MiniClaw

MiniClaw is a local-first automation runtime that turns Discord messages, optional Weixin direct text/voice/image entry, cron schedules, read-only providers, and Claude/Codex agents into one observable personal operations loop. The website is a curated portal; the implementation contract stays in the repo docs.

System Design

flowchart LR
  Discord[Discord] --> Intake[IM Intake]
  Weixin[Weixin Direct] --> Intake
  Intake --> Router[Smart Router]
  Router --> Chat[Chat Runtime]
  Router --> Task[Task Runtime]
  Cron[Cron Scheduler] --> ActiveWindow[Active Window Guard]
  ActiveWindow --> Providers[Pre Providers]
  Providers --> Task
  Task --> Agents[Claude / Codex]
  Chat --> Store[(SQLite)]
  Task --> Store
  Agents --> Delivery[Discord / IM Delivery]
  Store --> Quality[Trace / Docs / Quality Gates]

Design Surface

• Discord-native control plane: chat, task intake, slash commands, cron reports, and failure recovery land in Discord by default; Weixin direct is an opt-in personal text, voice, and image entry point that can enter chat or, after y/n confirmation, task mode independently.
• Runtime boundary: MiniClaw owns routing, context, progress, trace events, and delivery; Claude/Codex own agent execution.
• Operator visibility: task traces, cron run history, read-only doctor reports, and incident workflows are first-class slash-command surfaces.
• Provider-first reports: content, email, stock, watchlist, pulse, and market-intel providers produce structured context before the LLM summarizes anything, after scheduled cron passes the global active-window guard.
• Local-first state: user config, secrets, provider sessions, Weixin account state, cron state, and SQLite data live outside the public repo.
• Docs-driven governance: English repo docs are the canonical implementation record; Chinese docs mirror them with source-hash parity.
• Quality as architecture: docs drift, website drift, bilingual parity, changelog drift, coverage, secrets, and cron E2E are executable gates.

Runtime Loop

sequenceDiagram
  participant U as User / Cron
  participant D as Discord
  participant R as Router
  participant T as Runtime
  participant P as Provider
  participant A as Agent
  participant S as SQLite

  U->>D: message, slash command, or schedule
  D->>R: normalized intake event
  R->>T: chat, task, or cron route
  T->>P: collect trusted context when active window allows
  T->>A: execute with bounded runtime config
  A->>S: persist trace, usage, and state
  T->>D: progress, result, or recovery action

Operating Model

• Architecture maps the system boundaries and data movement.
• Runtime explains intake, routing, task execution, memory, cron, and recovery.
• Providers describes the readonly data collection layer and provider families.
• Getting Started keeps the first local run short and points deeper setup back to repo docs.
• Quality Gates shows how MiniClaw prevents docs, website, tests, and release checks from drifting.