mercury-agent 0.5.0 → 0.5.2

package/README.md

@@ -1,451 +1,452 @@
-<p align="center">
-  <img src="assets/logo-with-text.svg" alt="Mercury" height="120" />
-</p>
-
-<p align="center">
-  <em>There are many claws, but this one is mine.</em>
-</p>
-
-<p align="center">
-  <a href="https://github.com/Avishai-Tsabari/mercury"><img alt="GitHub" src="https://img.shields.io/badge/github-mercury-181717?style=flat-square&logo=github" /></a>
-  <a href="https://www.npmjs.com/package/mercury-agent"><img alt="npm" src="https://img.shields.io/npm/v/mercury-agent?style=flat-square&logo=npm" /></a>
-</p>
-
-Mercury is a personal AI assistant that lives where you chat. It connects to WhatsApp, Slack, Discord, and Telegram, runs agents inside containers for isolation, and uses [pi](https://github.com/badlogic/pi) as the runtime.
-
----
-
-## Prerequisites
-
-- **[Node.js](https://nodejs.org/)** >= 18 — Required for `npm install -g mercury-agent`
-- **[Bun](https://bun.sh)** >= 1.0 — JavaScript runtime used by Mercury
-- **[Docker](https://docs.docker.com/get-docker/)** — Required for running agent containers. On Linux, also install `docker-buildx` (`apt-get install docker-buildx`) — Docker Desktop includes it, but Docker Engine on Linux does not.
-- **Windows users:** Mercury runs best under [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install). Install WSL2 with `wsl --install`, then install Bun and Docker inside it.
-
-## Quick Start
-
-```bash
-npm install -g mercury-agent
-mkdir my-assistant && cd my-assistant
-mercury setup     # Interactive guided setup (recommended)
-# -- or for manual setup: --
-mercury init
-```
-
-Authenticate:
-
-```bash
-mercury auth login              # Interactive OAuth (Anthropic, GitHub Copilot, etc.)
-mercury auth login anthropic    # Or specify provider directly
-mercury auth status             # Check what's configured
-```
-
-Or set an API key in `.env`:
-
-```bash
-MERCURY_ANTHROPIC_API_KEY=sk-ant-...
-```
-
-Configure identity and adapters in `.env`:
-
-```bash
-MERCURY_BOT_USERNAME=Mercury
-MERCURY_TRIGGER_PATTERNS=@Mercury,Mercury
-
-# Enable adapters
-MERCURY_ENABLE_WHATSAPP=true
-MERCURY_ENABLE_DISCORD=true
-MERCURY_DISCORD_BOT_TOKEN=your-bot-token
-```
-
-Start:
-
-```bash
-mercury run
-# or install as a background service:
-mercury service install
-```
-
-### Set up spaces and conversations
-
-Mercury discovers conversations from incoming traffic. They start **unlinked** — you assign them to **spaces** (memory boundaries).
-
-```bash
-# Create spaces
-mercury spaces create main
-mercury spaces create work
-mercury spaces create family
-
-# Send a message from WhatsApp/Discord/Slack, then:
-mercury conversations              # See discovered conversations
-mercury conversations --unlinked   # See unlinked ones
-mercury link <id> main             # Link a conversation to a space
-```
-
-Multiple conversations can point at the same space — they share memory, session, and vault.
-
----
-
-## How It Works
-
-```
-┌──────────────────────────────────────────────────────────────┐
-│                        Host Process                          │
-│                                                              │
-│   ┌──────────┐  ┌─────────┐  ┌─────────┐  ┌───────────────┐  │
-│   │ WhatsApp │  │  Slack  │  │ Discord │  │   Scheduler   │  │
-│   │ Adapter  │  │ Adapter │  │ Adapter │  │ (cron tasks)  │  │
-│   └───┬──────┘  └────┬────┘  └───┬─────┘  └──────┬────────┘  │
-│       └──────────────┴───────────┴───────────────┘           │
-│                              │                               │
-│                     ┌────────▼────────┐                      │
-│                     │  Router/Queue   │                      │
-│                     └────────┬────────┘                      │
-│                              │                               │
-│                     ┌────────▼────────┐                      │
-│                     │    SQLite DB    │                      │
-│                     └────────┬────────┘                      │
-└──────────────────────────────┼───────────────────────────────┘
-                               │
-                     ┌─────────▼──────────┐
-                     │  Docker Container  │
-                     │  ┌──────────────┐  │
-                     │  │    pi CLI    │  │
-                     │  └──────────────┘  │
-                     │ /spaces/<space-id> │
-                     └────────────────────┘
-```
-
-Each space is a user-defined memory boundary with its own workspace and pi session. Incoming platform conversations are discovered automatically, then linked into spaces.
-
----
-
-## Features
-
-| Feature | Description | Docs |
-|---------|-------------|------|
-| **Multi-platform** | WhatsApp, Slack, Discord, Telegram | [docs/pipeline.md](docs/pipeline.md) |
-| **Memory** | Obsidian-compatible vault per space | [docs/memory.md](docs/memory.md) |
-| **Scheduled Tasks** | Cron-based recurring prompts | [docs/scheduler.md](docs/scheduler.md) |
-| **Permissions** | Role-based access control | [docs/permissions.md](docs/permissions.md) |
-| **Media** | Images, documents, voice notes | [docs/media/overview.md](docs/media/overview.md) |
-| **KB Distillation** | Extract lasting knowledge from chats | [docs/kb-distillation.md](docs/kb-distillation.md) |
-| **Extensions** | TypeScript plugins for CLIs, skills, jobs, hooks | [docs/extensions.md](docs/extensions.md) |
-| **DM Auto-Space** | Auto-create isolated spaces per customer DM | [docs/rate-limiting.md](docs/rate-limiting.md) |
-
----
-
-## Workspaces
-
-Each space gets an isolated workspace:
-
-```text
-.mercury/spaces/<space-id>/
-├── AGENTS.md              # Space instructions
-├── .mercury.session.jsonl # pi session
-├── inbox/                 # Media received from users
-└── outbox/                # Files produced by the agent
-```
-
-Memory/vault structure (for example `.obsidian/`, `knowledge/`, `daily/`) is created by installed extensions.
-
-Multiple platform conversations can point at the same space.
-
----
-
-## Agent Profiles
-
-Profiles are shareable templates that bundle agent instructions, extensions, and defaults. Use them to start from a preconfigured assistant type.
-
-**Built-in profiles:**
-
-| Profile | Description |
-|---------|-------------|
-| `general` | General-purpose assistant — helpful, concise, chat-friendly |
-| `coding` | Code-focused with sub-agent delegation and web search |
-| `research` | Web search and knowledge distillation focused |
-
-```bash
-# Create from built-in profile
-mercury setup --profile coding
-
-# Create from git repo
-mercury setup --profile https://github.com/user/mercury-stock-agent
-
-# Create from local directory
-mercury setup --profile ./my-profiles/ml-assistant
-
-# List available profiles
-mercury profiles list
-
-# Export current project as a profile
-mercury profiles export ./my-profile
-```
-
----
-
-## CLI
-
-### `mercury` (host CLI)
-
-```bash
-# setup + runtime
-mercury setup              # Interactive guided setup (recommended for new projects)
-mercury setup --profile <name>   # Create from a profile (general, coding, research, or path/URL)
-mercury init               # Manual init (creates .env, .mercury structure)
-mercury run
-mercury build              # only needed when developing the base image from source
-mercury status
-mercury doctor             # preflight check — validates Docker, Bun, credentials, adapters
-
-# profiles (agent templates)
-mercury profiles list      # List built-in profiles
-mercury profiles show <name>   # Show profile details
-mercury profiles export <dir>  # Export current project as a reusable profile
-
-# auth
-mercury auth login [provider]
-mercury auth logout [provider]
-mercury auth status
-mercury auth whatsapp
-
-# chat + routing
-mercury chat "hello"
-mercury chat --file photo.jpg "what's in this?"
-mercury chat --space work "check status"
-echo "summarize" | mercury chat
-mercury spaces list
-mercury spaces create <id>
-mercury conversations
-mercury conversations --unlinked
-mercury link <conversation-id> <space-id>
-
-# extensions
-mercury add ./path/to/extension
-mercury add npm:<package>
-mercury add git:<repo-url>
-mercury add user/repo       # GitHub shorthand (e.g. mercury add user/mercury-ext-ml)
-mercury add user/repo#subdir   # GitHub repo with subdirectory
-mercury remove <name>
-mercury extensions list
-mercury ext create <name>   # Scaffold a new extension
-mercury ext validate <name> # Validate extension structure and load
-mercury ext test <name>     # Dry-run load extension
-
-# service (recommended for background)
-mercury service install
-mercury service uninstall
-mercury service status
-mercury service logs [-f]
-```
-
-### `mrctl` (in-container API CLI)
-
-```bash
-mrctl whoami
-mrctl tasks list|create|pause|resume|run|delete
-mrctl roles list|grant|revoke
-mrctl permissions show|set
-mrctl config get|set
-mrctl spaces list|name|delete
-mrctl conversations list
-mrctl stop
-mrctl compact
-```
-
-For full command docs, run `mercury --help`, `mercury <command> --help`, or `mrctl help`.
-
----
-
-## Extensions
-
-Mercury supports TypeScript extensions that add CLIs, skills, background jobs, lifecycle hooks, config keys, and dashboard widgets.
-
-### Creating Extensions
-
-```bash
-mercury ext create my-extension   # Scaffold a new extension
-mercury ext validate my-extension # Check structure and load
-mercury ext test my-extension     # Dry-run load
-```
-
-```
-.mercury/extensions/
-├── napkin/
-│   ├── index.ts
-│   └── skill/SKILL.md
-└── my-extension/
-    └── index.ts
-```
-
-Each extension exports a setup function:
-
-```typescript
-export default function(mercury) {
-  mercury.cli({ name: "napkin", install: "bun add -g napkin-ai" });
-  mercury.permission({ defaultRoles: ["admin", "member"] });
-  mercury.env({ from: "MERCURY_NAPKIN_API_KEY" });
-  mercury.skill("./skill");
-  mercury.on("workspace_init", async ({ workspace, containerWorkspace }) => { ... });
-  mercury.on("before_container", async ({ workspace, containerWorkspace }) => {
-    return { env: { MY_VAR: containerWorkspace + "/data" } };
-  });
-}
-```
-
-Extensions with CLIs get auto-installed into a derived Docker image. Skills are symlinked for agent discovery. Permissions integrate with the existing RBAC system.
-
-See [docs/extensions.md](docs/extensions.md) for the extension system guide.
-
----
-
-## Configuration
-
-Optional project file **`mercury.yaml`** (or **`mercury.yml`**) supplies non-secret defaults; any set **`MERCURY_*`** variable overrides it. See [docs/configuration.md](docs/configuration.md) and `resources/templates/mercury.example.yaml`.
-
-### Environment Variables
-
-**Core:**
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `MERCURY_DATA_DIR` | `.mercury` | Data directory |
-| `MERCURY_MAX_CONCURRENCY` | `3` | Max concurrent runs |
-| `MERCURY_PORT` | `8787` | API port |
-| `MERCURY_BOT_USERNAME` | `mercury` | Bot display name |
-| `MERCURY_LOG_LEVEL` | `info` | Log level |
-
-**Security:**
-
-| Variable | Description |
-|----------|-------------|
-| `MERCURY_API_SECRET` | Shared secret for `/api/*` routes. When set, requires `Authorization: Bearer <secret>`. Auto-generated by `mercury setup`. |
-| `MERCURY_CHAT_API_KEY` | Optional API key for `/chat` endpoint. When set, requires Bearer token. When unset, `/chat` is open (for local use). |
-
-**Auth:**
-
-Credentials are resolved in this order:
-1. OAuth credentials from `mercury auth login` (saved to `.mercury/global/auth.json`)
-2. API keys from `.env` (e.g., `MERCURY_ANTHROPIC_API_KEY`)
-
-Supported OAuth providers: Anthropic, GitHub Copilot, Google Gemini CLI, Antigravity, OpenAI Codex.
-
-**Model:**
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `MERCURY_MODEL_PROVIDER` | `anthropic` | Provider |
-| `MERCURY_MODEL` | `claude-opus-4-6` | Model |
-| `MERCURY_ANTHROPIC_API_KEY` | — | API key |
-| `MERCURY_ANTHROPIC_OAUTH_TOKEN` | — | OAuth token (alternative) |
-
-**Adapters:**
-
-| Variable | Description |
-|----------|-------------|
-| `MERCURY_ENABLE_WHATSAPP` | Enable WhatsApp |
-| `MERCURY_WHATSAPP_AUTH_DIR` | Auth storage path |
-| `MERCURY_ENABLE_TELEGRAM` | Enable Telegram |
-| `MERCURY_TELEGRAM_BOT_TOKEN` | Telegram bot token |
-| `MERCURY_ENABLE_DISCORD` | Enable Discord |
-| `MERCURY_DISCORD_BOT_TOKEN` | Discord bot token |
-| `MERCURY_ENABLE_SLACK` | Enable Slack |
-| `MERCURY_SLACK_BOT_TOKEN` | Slack bot token |
-| `MERCURY_SLACK_SIGNING_SECRET` | Slack signing secret |
-
-**Container:**
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `MERCURY_AGENT_CONTAINER_IMAGE` | `ghcr.io/avishai-tsabari/mercury-agent:latest` | Container image |
-| `MERCURY_CONTAINER_TIMEOUT_MS` | `300000` | Container timeout (5 min) |
-| `MERCURY_CONTAINER_RUNTIME` | `runc` | `runc` (default) or `runsc` ([gVisor](https://gvisor.dev)) |
-| `MERCURY_CONTAINER_BWRAP_DOCKER_COMPAT` | `false` | Set `true` on Linux Docker Engine (see note below) |
-
-> **Linux Docker Engine:** Mercury uses [bubblewrap](https://github.com/containers/bubblewrap) for in-container sandboxing. On Linux Docker Engine (not Docker Desktop), bwrap cannot mount `/proc` without extra privileges. Either set `container_bwrap_docker_compat: true` in `mercury.yaml` (adds `--privileged` to `docker run`), or install [gVisor](https://gvisor.dev/docs/user_guide/install/) and set `MERCURY_CONTAINER_RUNTIME=runsc` to skip bwrap entirely.
-
-**KB Distillation:**
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `MERCURY_KB_DISTILL_INTERVAL_MS` | `0` (disabled) | Distillation interval |
-
-**Triggers:**
-
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `MERCURY_TRIGGER_MATCH` | `mention` | `mention`, `prefix`, `always` |
-| `MERCURY_TRIGGER_PATTERNS` | `@Mercury,Mercury` | Trigger patterns |
-| `MERCURY_ADMINS` | — | Pre-seeded admin user IDs |
-
-### DM Auto-Space
-
-Auto-create isolated spaces for each customer who DMs your bot. Each customer gets their own space with persistent context, configurable permissions, and rate limits.
-
-```yaml
-# mercury.yaml
-dm_auto_space:
-  enabled: true
-  admin_ids:                                    # platform IDs — auto-link to "main" space
-    - "24417056866472"                          # WhatsApp LID, Telegram user ID, etc.
-  default_system_prompt: "You are a helpful assistant."
-  default_member_permissions: "prompt,prefs.get"  # restrict customers to chat only
-
-runtime:
-  rate_limit_daily_member: 20                   # global daily cap for members (0 = unlimited)
-  rate_limit_daily_admin: 0                     # global daily cap for admins (0 = unlimited)
-```
-
-`admin_ids` values are platform-specific identifiers — check the dashboard Conversations page to see the format (e.g. WhatsApp LID digits, Telegram numeric user ID).
-
-Auto-created spaces are seeded with `trigger.match=always`, `context.mode=context`, and the configured member permissions. Per-space rate limits are manageable from the dashboard.
-
-### Per-space Config
-
-Conversations are discovered from incoming traffic. Unlinked conversations stay idle until you attach them to a space via `mercury link <conversation-id> <space-id>` or the dashboard.
-
-```bash
-mrctl config set trigger_match always
-mrctl config set trigger_patterns "@Bot,Bot"
-```
-
----
-
-## Docs
-
-- **Remaining work:** [TODOS](docs/TODOS.md) — Security, reliability, and ops gaps
-- **Platform setup:** [WhatsApp](docs/setup-whatsapp.md) · [Discord](docs/setup-discord.md) · [Slack](docs/setup-slack.md)
-- [Configuration](docs/configuration.md) (mercury.yaml + env) · [PRD: config load](docs/prd-config-load.md)
-- [Authentication](docs/auth/overview.md)
-- [Message pipeline](docs/pipeline.md)
-- [Memory system](docs/memory.md)
-- [Scheduled tasks](docs/scheduler.md)
-- [Permissions](docs/permissions.md)
-- [Media handling](docs/media/overview.md)
-- [KB distillation](docs/kb-distillation.md)
-- [Container lifecycle](docs/container-lifecycle.md)
-- [Graceful shutdown](docs/graceful-shutdown.md)
-- [Rate limiting](docs/rate-limiting.md)
-- [Extensions](docs/extensions.md)
-
----
-
-## Credits
-
-Mercury was originally created by [Michael Livshits](https://github.com/Michaelliv). Full credit for the foundational architecture, extension system, and platform adapters goes to him.
-
-Original repository: [github.com/Michaelliv/mercury](https://github.com/Michaelliv/mercury) (archived)
-
-This fork is maintained by [Avishai Tsabari](https://github.com/Avishai-Tsabari).
-
----
-
-## License
-
-MIT — see [LICENSE](LICENSE)
-
----
-
-<p align="center">
-  <em>There are many claws, but this one is mine.</em> 🪽
-</p>
+<p align="center">
+  <img src="assets/logo-with-text.svg" alt="Mercury" height="120" />
+</p>
+
+<p align="center">
+  <em>There are many claws, but this one is mine.</em>
+</p>
+
+<p align="center">
+  <a href="https://github.com/Avishai-Tsabari/mercury"><img alt="GitHub" src="https://img.shields.io/badge/github-mercury-181717?style=flat-square&logo=github" /></a>
+  <a href="https://www.npmjs.com/package/mercury-agent"><img alt="npm" src="https://img.shields.io/npm/v/mercury-agent?style=flat-square&logo=npm" /></a>
+</p>
+
+Mercury is a personal AI assistant that lives where you chat. It connects to WhatsApp, Slack, Discord, and Telegram, runs agents inside containers for isolation, and uses [pi](https://github.com/badlogic/pi) as the runtime.
+
+---
+
+## Prerequisites
+
+- **[Node.js](https://nodejs.org/)** >= 18 — Required for `npm install -g mercury-agent`
+- **[Bun](https://bun.sh)** >= 1.2 — JavaScript runtime used by Mercury
+- **[Docker](https://docs.docker.com/get-docker/)** — Required for running agent containers. On Linux, also install `docker-buildx` (`apt-get install docker-buildx`) — Docker Desktop includes it, but Docker Engine on Linux does not.
+- **Windows users:** Mercury runs best under [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install). Install WSL2 with `wsl --install`, then install Bun and Docker inside it.
+
+## Quick Start
+
+```bash
+npm install -g mercury-agent
+mkdir my-assistant && cd my-assistant
+mercury setup     # Interactive guided setup (recommended)
+# -- or for manual setup: --
+mercury init
+```
+
+Authenticate:
+
+```bash
+mercury auth login              # Interactive OAuth (Anthropic, GitHub Copilot, etc.)
+mercury auth login anthropic    # Or specify provider directly
+mercury auth status             # Check what's configured
+```
+
+Or set an API key in `.env`:
+
+```bash
+MERCURY_ANTHROPIC_API_KEY=sk-ant-...
+```
+
+Configure identity and adapters in `.env`:
+
+```bash
+MERCURY_BOT_USERNAME=Mercury
+MERCURY_TRIGGER_PATTERNS=@Mercury,Mercury
+
+# Enable adapters
+MERCURY_ENABLE_WHATSAPP=true
+MERCURY_ENABLE_DISCORD=true
+MERCURY_DISCORD_BOT_TOKEN=your-bot-token
+```
+
+Start:
+
+```bash
+mercury run
+# or install as a background service:
+mercury service install
+```
+
+> `mercury run` runs in the foreground (good for a first smoke test). For anything long-running, prefer `mercury service install` — it runs in the background and auto-restarts.
+
+### Set up spaces and conversations
+
+Mercury discovers conversations from incoming traffic. They start **unlinked** — you assign them to **spaces** (memory boundaries).
+
+```bash
+# Create spaces
+mercury spaces create main
+mercury spaces create work
+mercury spaces create family
+
+# Send a message from WhatsApp/Discord/Slack, then:
+mercury conversations              # See discovered conversations
+mercury conversations --unlinked   # See unlinked ones
+mercury link <id> main             # Link a conversation to a space
+```
+
+Multiple conversations can point at the same space — they share memory, session, and vault.
+
+---
+
+## How It Works
+
+```
+┌──────────────────────────────────────────────────────────────┐
+│                        Host Process                          │
+│                                                              │
+│   ┌──────────┐  ┌─────────┐  ┌─────────┐  ┌───────────────┐  │
+│   │ WhatsApp │  │  Slack  │  │ Discord │  │   Scheduler   │  │
+│   │ Adapter  │  │ Adapter │  │ Adapter │  │ (cron tasks)  │  │
+│   └───┬──────┘  └────┬────┘  └───┬─────┘  └──────┬────────┘  │
+│       └──────────────┴───────────┴───────────────┘           │
+│                              │                               │
+│                     ┌────────▼────────┐                      │
+│                     │  Router/Queue   │                      │
+│                     └────────┬────────┘                      │
+│                              │                               │
+│                     ┌────────▼────────┐                      │
+│                     │    SQLite DB    │                      │
+│                     └────────┬────────┘                      │
+└──────────────────────────────┼───────────────────────────────┘
+                               │
+                     ┌─────────▼──────────┐
+                     │  Docker Container  │
+                     │  ┌──────────────┐  │
+                     │  │    pi CLI    │  │
+                     │  └──────────────┘  │
+                     │ /spaces/<space-id> │
+                     └────────────────────┘
+```
+
+Each space is a user-defined memory boundary with its own workspace and pi session. Incoming platform conversations are discovered automatically, then linked into spaces.
+
+---
+
+## Features
+
+| Feature | Description | Docs |
+|---------|-------------|------|
+| **Multi-platform** | WhatsApp, Slack, Discord, Telegram | [docs/pipeline.md](docs/pipeline.md) |
+| **Memory** | Obsidian-compatible vault per space | [docs/memory.md](docs/memory.md) |
+| **Scheduled Tasks** | Cron-based recurring prompts | [docs/scheduler.md](docs/scheduler.md) |
+| **Permissions** | Role-based access control | [docs/permissions.md](docs/permissions.md) |
+| **Media** | Images, documents, voice notes | [docs/media/overview.md](docs/media/overview.md) |
+| **KB Distillation** | Extract lasting knowledge from chats | [docs/kb-distillation.md](docs/kb-distillation.md) |
+| **Extensions** | TypeScript plugins for CLIs, skills, jobs, hooks | [docs/extensions.md](docs/extensions.md) |
+| **DM Auto-Space** | Auto-create isolated spaces per customer DM | [docs/rate-limiting.md](docs/rate-limiting.md) |
+
+---
+
+## Workspaces
+
+Each space gets an isolated workspace:
+
+```text
+.mercury/spaces/<space-id>/
+├── AGENTS.md              # Space instructions
+├── .mercury.session.jsonl # pi session
+├── inbox/                 # Media received from users
+└── outbox/                # Files produced by the agent
+```
+
+Memory/vault structure (for example `.obsidian/`, `knowledge/`, `daily/`) is created by installed extensions.
+
+Multiple platform conversations can point at the same space.
+
+---
+
+## Agent Profiles
+
+Profiles are shareable templates that bundle agent instructions, extensions, and defaults. Use them to start from a preconfigured assistant type.
+
+**Built-in profiles:**
+
+| Profile | Description |
+|---------|-------------|
+| `general` | General-purpose assistant — helpful, concise, chat-friendly |
+| `coding` | Code-focused with sub-agent delegation and web search |
+| `research` | Web search and knowledge distillation focused |
+
+```bash
+# Create from built-in profile
+mercury setup --profile coding
+
+# Create from git repo
+mercury setup --profile https://github.com/user/mercury-stock-agent
+
+# Create from local directory
+mercury setup --profile ./my-profiles/ml-assistant
+
+# List available profiles
+mercury profiles list
+
+# Export current project as a profile
+mercury profiles export ./my-profile
+```
+
+---
+
+## CLI
+
+### `mercury` (host CLI)
+
+```bash
+# setup + runtime
+mercury setup              # Interactive guided setup (recommended for new projects)
+mercury setup --profile <name>   # Create from a profile (general, coding, research, or path/URL)
+mercury init               # Manual init (creates .env, .mercury structure)
+mercury run
+mercury build              # only needed when developing the base image from source
+mercury status
+mercury doctor             # preflight check — validates Docker, Bun, credentials, adapters
+
+# profiles (agent templates)
+mercury profiles list      # List built-in profiles
+mercury profiles show <name>   # Show profile details
+mercury profiles export <dir>  # Export current project as a reusable profile
+
+# auth
+mercury auth login [provider]
+mercury auth logout [provider]
+mercury auth status
+mercury auth whatsapp
+
+# chat + routing
+mercury chat "hello"
+mercury chat --file photo.jpg "what's in this?"
+mercury chat --space work "check status"
+echo "summarize" | mercury chat
+mercury spaces list
+mercury spaces create <id>
+mercury conversations
+mercury conversations --unlinked
+mercury link <conversation-id> <space-id>
+
+# extensions
+mercury add ./path/to/extension
+mercury add npm:<package>
+mercury add git:<repo-url>
+mercury add user/repo       # GitHub shorthand (e.g. mercury add user/mercury-ext-ml)
+mercury add user/repo#subdir   # GitHub repo with subdirectory
+mercury remove <name>
+mercury extensions list
+mercury ext create <name>   # Scaffold a new extension
+mercury ext validate <name> # Validate extension structure and load
+mercury ext test <name>     # Dry-run load extension
+
+# service (recommended for background)
+mercury service install
+mercury service uninstall
+mercury service status
+mercury service logs [-f]
+```
+
+### `mrctl` (in-container API CLI)
+
+```bash
+mrctl whoami
+mrctl tasks list|create|pause|resume|run|delete
+mrctl roles list|grant|revoke
+mrctl permissions show|set
+mrctl config get|set
+mrctl spaces list|name|delete
+mrctl conversations list
+mrctl stop
+mrctl compact
+```
+
+For full command docs, run `mercury --help`, `mercury <command> --help`, or `mrctl help`.
+
+---
+
+## Extensions
+
+Mercury supports TypeScript extensions that add CLIs, skills, background jobs, lifecycle hooks, config keys, and dashboard widgets.
+
+### Creating Extensions
+
+```bash
+mercury ext create my-extension   # Scaffold a new extension
+mercury ext validate my-extension # Check structure and load
+mercury ext test my-extension     # Dry-run load
+```
+
+```
+.mercury/extensions/
+├── napkin/
+│   ├── index.ts
+│   └── skill/SKILL.md
+└── my-extension/
+    └── index.ts
+```
+
+Each extension exports a setup function:
+
+```typescript
+export default function(mercury) {
+  mercury.cli({ name: "napkin", install: "bun add -g napkin-ai" });
+  mercury.permission({ defaultRoles: ["admin", "member"] });
+  mercury.env({ from: "MERCURY_NAPKIN_API_KEY" });
+  mercury.skill("./skill");
+  mercury.on("workspace_init", async ({ workspace, containerWorkspace }) => { ... });
+  mercury.on("before_container", async ({ workspace, containerWorkspace }) => {
+    return { env: { MY_VAR: containerWorkspace + "/data" } };
+  });
+}
+```
+
+Extensions with CLIs get auto-installed into a derived Docker image. Skills are symlinked for agent discovery. Permissions integrate with the existing RBAC system.
+
+See [docs/extensions.md](docs/extensions.md) for the extension system guide.
+
+---
+
+## Configuration
+
+Optional project file **`mercury.yaml`** (or **`mercury.yml`**) supplies non-secret defaults; any set **`MERCURY_*`** variable overrides it. See [docs/configuration.md](docs/configuration.md) and `resources/templates/mercury.example.yaml`.
+
+### Environment Variables
+
+**Core:**
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `MERCURY_DATA_DIR` | `.mercury` | Data directory |
+| `MERCURY_MAX_CONCURRENCY` | `2` | Max concurrent runs |
+| `MERCURY_PORT` | `8787` | API port |
+| `MERCURY_BOT_USERNAME` | `mercury` | Bot display name |
+| `MERCURY_LOG_LEVEL` | `info` | Log level |
+
+**Security:**
+
+| Variable | Description |
+|----------|-------------|
+| `MERCURY_API_SECRET` | Shared secret for `/api/*` routes. When set, requires `Authorization: Bearer <secret>`. Auto-generated by `mercury setup`. |
+| `MERCURY_CHAT_API_KEY` | Optional API key for `/chat` endpoint. When set, requires Bearer token. When unset, `/chat` is open (for local use). |
+
+**Auth:**
+
+Credentials are resolved in this order:
+1. OAuth credentials from `mercury auth login` (saved to `.mercury/global/auth.json`)
+2. API keys from `.env` (e.g., `MERCURY_ANTHROPIC_API_KEY`)
+
+Supported OAuth providers: Anthropic, GitHub Copilot, Google Gemini CLI, Antigravity, OpenAI Codex.
+
+**Model:**
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `MERCURY_MODEL_PROVIDER` | `anthropic` | Provider |
+| `MERCURY_MODEL` | `claude-opus-4-8` | Model |
+| `MERCURY_ANTHROPIC_API_KEY` | — | API key |
+| `MERCURY_ANTHROPIC_OAUTH_TOKEN` | — | OAuth token (alternative) |
+
+**Adapters:**
+
+| Variable | Description |
+|----------|-------------|
+| `MERCURY_ENABLE_WHATSAPP` | Enable WhatsApp |
+| `MERCURY_WHATSAPP_AUTH_DIR` | Auth storage path |
+| `MERCURY_ENABLE_TELEGRAM` | Enable Telegram |
+| `MERCURY_TELEGRAM_BOT_TOKEN` | Telegram bot token |
+| `MERCURY_ENABLE_DISCORD` | Enable Discord |
+| `MERCURY_DISCORD_BOT_TOKEN` | Discord bot token |
+| `MERCURY_ENABLE_SLACK` | Enable Slack |
+| `MERCURY_SLACK_BOT_TOKEN` | Slack bot token |
+| `MERCURY_SLACK_SIGNING_SECRET` | Slack signing secret |
+
+**Container:**
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `MERCURY_AGENT_IMAGE` | `ghcr.io/avishai-tsabari/mercury-agent:latest` | Container image |
+| `MERCURY_CONTAINER_TIMEOUT_MS` | `300000` | Container timeout (5 min) |
+| `MERCURY_CONTAINER_RUNTIME` | `runc` | `runc` (default) or `runsc` ([gVisor](https://gvisor.dev)) |
+| `MERCURY_CONTAINER_BWRAP_DOCKER_COMPAT` | `false` | Set `true` on Linux Docker Engine (see note below) |
+
+> **Linux Docker Engine:** Mercury uses [bubblewrap](https://github.com/containers/bubblewrap) for in-container sandboxing. On Linux Docker Engine (not Docker Desktop), bwrap cannot mount `/proc` without extra privileges. Either set `container_bwrap_docker_compat: true` in `mercury.yaml` (adds `--privileged` to `docker run`), or install [gVisor](https://gvisor.dev/docs/user_guide/install/) and set `MERCURY_CONTAINER_RUNTIME=runsc` to skip bwrap entirely.
+
+**KB Distillation:**
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `MERCURY_KB_DISTILL_INTERVAL_MS` | `0` (disabled) | Distillation interval |
+
+**Triggers:**
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `MERCURY_TRIGGER_MATCH` | `mention` | `mention`, `prefix`, `always` |
+| `MERCURY_TRIGGER_PATTERNS` | `@Mercury,Mercury` | Trigger patterns |
+| `MERCURY_ADMINS` | — | Pre-seeded admin user IDs |
+
+### DM Auto-Space
+
+Auto-create isolated spaces for each customer who DMs your bot. Each customer gets their own space with persistent context, configurable permissions, and rate limits.
+
+```yaml
+# mercury.yaml
+dm_auto_space:
+  enabled: true
+  admin_ids:                                    # platform IDs — auto-link to "main" space
+    - "24417056866472"                          # WhatsApp LID, Telegram user ID, etc.
+  default_system_prompt: "You are a helpful assistant."
+  default_member_permissions: "prompt,prefs.get"  # restrict customers to chat only
+
+runtime:
+  rate_limit_daily_member: 20                   # global daily cap for members (0 = unlimited)
+  rate_limit_daily_admin: 0                     # global daily cap for admins (0 = unlimited)
+```
+
+`admin_ids` values are platform-specific identifiers — check the dashboard Conversations page to see the format (e.g. WhatsApp LID digits, Telegram numeric user ID).
+
+Auto-created spaces are seeded with `trigger.match=always`, `context.mode=context`, and the configured member permissions. Per-space rate limits are manageable from the dashboard.
+
+### Per-space Config
+
+Conversations are discovered from incoming traffic. Unlinked conversations stay idle until you attach them to a space via `mercury link <conversation-id> <space-id>` or the dashboard.
+
+```bash
+mrctl config set trigger_match always
+mrctl config set trigger_patterns "@Bot,Bot"
+```
+
+---
+
+## Docs
+
+- **Platform setup:** [WhatsApp](docs/setup-whatsapp.md) · [Discord](docs/setup-discord.md) · [Slack](docs/setup-slack.md)
+- [Configuration](docs/configuration.md) (mercury.yaml + env) · [PRD: config load](docs/prd-config-load.md)
+- [Authentication](docs/auth/overview.md)
+- [Message pipeline](docs/pipeline.md)
+- [Memory system](docs/memory.md)
+- [Scheduled tasks](docs/scheduler.md)
+- [Permissions](docs/permissions.md)
+- [Media handling](docs/media/overview.md)
+- [KB distillation](docs/kb-distillation.md)
+- [Container lifecycle](docs/container-lifecycle.md)
+- [Graceful shutdown](docs/graceful-shutdown.md)
+- [Rate limiting](docs/rate-limiting.md)
+- [Extensions](docs/extensions.md)
+
+---
+
+## Credits
+
+Mercury was originally created by [Michael Livshits](https://github.com/Michaelliv). Full credit for the foundational architecture, extension system, and platform adapters goes to him.
+
+Original repository: [github.com/Michaelliv/mercury](https://github.com/Michaelliv/mercury) (archived)
+
+This fork is maintained by [Avishai Tsabari](https://github.com/Avishai-Tsabari).
+
+---
+
+## License
+
+MIT — see [LICENSE](LICENSE)
+
+---
+
+<p align="center">
+  <em>There are many claws, but this one is mine.</em> 🪽
+</p>