fengming 0.3.10 → 0.3.11

package/docs/help/troubleshooting.md

@@ -1,449 +0,0 @@
----
-summary: "Symptom first troubleshooting hub for FengMing"
-read_when:
-  - FengMing is not working and you need the fastest path to a fix
-  - You want a triage flow before diving into deep runbooks
-title: "General troubleshooting"
----
-
-If you only have 2 minutes, use this page as a triage front door.
-
-## First 60 seconds
-
-Run this exact ladder in order:
-
-```bash
-fengming status
-fengming status --all
-fengming gateway probe
-fengming gateway status
-fengming doctor
-fengming channels status --probe
-fengming logs --follow
-```
-
-Good output in one line:
-
-- `fengming status` → shows configured channels and no obvious auth errors.
-- `fengming status --all` → full report is present and shareable.
-- `fengming gateway probe` → expected gateway target is reachable (`Reachable: yes`). `Capability: ...` tells you what auth level the probe could prove, and `Read probe: limited - missing scope: operator.read` is degraded diagnostics, not a connect failure.
-- `fengming gateway status` → `Runtime: running`, `Connectivity probe: ok`, and a plausible `Capability: ...` line. Use `--require-rpc` if you need read-scope RPC proof too.
-- `fengming doctor` → no blocking config/service errors.
-- `fengming channels status --probe` → reachable gateway returns live per-account
-  transport state plus probe/audit results such as `works` or `audit ok`; if the
-  gateway is unreachable, the command falls back to config-only summaries.
-- `fengming logs --follow` → steady activity, no repeating fatal errors.
-
-## Assistant feels limited or missing tools
-
-If the assistant cannot inspect files, run commands, use browser automation, or
-see expected tools, check the effective tool profile first:
-
-```bash
-fengming status
-fengming status --all
-fengming doctor
-```
-
-Common causes:
-
-- `tools.profile: "messaging"` is intentionally narrow for chat-only agents.
-- `tools.profile: "coding"` is the usual profile for repository, file, shell,
-  and runtime workflows.
-- `tools.profile: "full"` exposes the broadest tool set and should be limited
-  to trusted operator-controlled agents.
-- Per-agent `agents.list[].tools` overrides can narrow or expand the root
-  profile for one agent.
-
-Change the root or per-agent tool profile, then restart or reload the Gateway
-and run `fengming status --all` again. See [Tools](/tools) for the profile
-model and allow/deny overrides.
-
-## Anthropic long context 429
-
-If you see:
-`HTTP 429: rate_limit_error: Extra usage is required for long context requests`,
-go to [/gateway/troubleshooting#anthropic-429-extra-usage-required-for-long-context](/gateway/troubleshooting#anthropic-429-extra-usage-required-for-long-context).
-
-## Local OpenAI-compatible backend works directly but fails in FengMing
-
-If your local or self-hosted `/v1` backend answers small direct
-`/v1/chat/completions` probes but fails on `fengming infer model run` or normal
-agent turns:
-
-1. If the error mentions `messages[].content` expecting a string, set
-   `models.providers.<provider>.models[].compat.requiresStringContent: true`.
-2. If the backend still fails only on FengMing agent turns, set
-   `models.providers.<provider>.models[].compat.supportsTools: false` and retry.
-3. If tiny direct calls still work but larger FengMing prompts crash the
-   backend, treat the remaining issue as an upstream model/server limitation and
-   continue in the deep runbook:
-   [/gateway/troubleshooting#local-openai-compatible-backend-passes-direct-probes-but-agent-runs-fail](/gateway/troubleshooting#local-openai-compatible-backend-passes-direct-probes-but-agent-runs-fail)
-
-## Plugin install fails with missing fengming extensions
-
-If install fails with `package.json missing fengming.extensions`, the plugin package
-is using an old shape that FengMing no longer accepts.
-
-Fix in the plugin package:
-
-1. Add `fengming.extensions` to `package.json`.
-2. Point entries at built runtime files (usually `./dist/index.js`).
-3. Republish the plugin and run `fengming plugins install <package>` again.
-
-Example:
-
-```json
-{
-  "name": "@fengming/my-plugin",
-  "version": "1.2.3",
-  "fengming": {
-    "extensions": ["./dist/index.js"]
-  }
-}
-```
-
-Reference: [Plugin architecture](/plugins/architecture)
-
-## Plugin present but blocked by suspicious ownership
-
-If `fengming doctor`, setup, or startup warnings show:
-
-```text
-blocked plugin candidate: suspicious ownership (... uid=1000, expected uid=0 or root)
-plugin present but blocked
-```
-
-the plugin files are owned by a different Unix user than the process loading
-them. Do not remove the plugin config. Fix the file ownership or run FengMing as
-the same user that owns the state directory.
-
-Docker installs normally run as `node` (uid `1000`). For the default Docker
-setup, repair the host bind mounts:
-
-```bash
-sudo chown -R 1000:1000 /path/to/fengming-config /path/to/fengming-workspace
-fengming doctor --fix
-```
-
-If you intentionally run FengMing as root, repair the managed plugin root to
-root ownership instead:
-
-```bash
-sudo chown -R root:root /path/to/fengming-config/npm
-fengming doctor --fix
-```
-
-Deeper docs:
-
-- [Plugin path ownership](/tools/plugin#blocked-plugin-path-ownership)
-- [Docker permissions](/install/docker#permissions-and-eacces)
-
-## Decision tree
-
-```mermaid
-flowchart TD
-  A[FengMing is not working] --> B{What breaks first}
-  B --> C[No replies]
-  B --> D[Dashboard or Control UI will not connect]
-  B --> E[Gateway will not start or service not running]
-  B --> F[Channel connects but messages do not flow]
-  B --> G[Cron or heartbeat did not fire or did not deliver]
-  B --> H[Node is paired but camera canvas screen exec fails]
-  B --> I[Browser tool fails]
-
-  C --> C1[/No replies section/]
-  D --> D1[/Control UI section/]
-  E --> E1[/Gateway section/]
-  F --> F1[/Channel flow section/]
-  G --> G1[/Automation section/]
-  H --> H1[/Node tools section/]
-  I --> I1[/Browser section/]
-```
-
-<AccordionGroup>
-  <Accordion title="No replies">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming channels status --probe
-    fengming pairing list --channel <channel> [--account <id>]
-    fengming logs --follow
-    ```
-
-    Good output looks like:
-
-    - `Runtime: running`
-    - `Connectivity probe: ok`
-    - `Capability: read-only`, `write-capable`, or `admin-capable`
-    - Your channel shows transport connected and, where supported, `works` or `audit ok` in `channels status --probe`
-    - Sender appears approved (or DM policy is open/allowlist)
-
-    Common log signatures:
-
-    - `drop guild message (mention required` → mention gating blocked the message in Discord.
-    - `pairing request` → sender is unapproved and waiting for DM pairing approval.
-    - `blocked` / `allowlist` in channel logs → sender, room, or group is filtered.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#no-replies](/gateway/troubleshooting#no-replies)
-    - [/channels/troubleshooting](/channels/troubleshooting)
-    - [/channels/pairing](/channels/pairing)
-
-  </Accordion>
-
-  <Accordion title="Dashboard or Control UI will not connect">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming logs --follow
-    fengming doctor
-    fengming channels status --probe
-    ```
-
-    Good output looks like:
-
-    - `Dashboard: http://...` is shown in `fengming gateway status`
-    - `Connectivity probe: ok`
-    - `Capability: read-only`, `write-capable`, or `admin-capable`
-    - No auth loop in logs
-
-    Common log signatures:
-
-    - `device identity required` → HTTP/non-secure context cannot complete device auth.
-    - `origin not allowed` → browser `Origin` is not allowed for the Control UI
-      gateway target.
-    - `AUTH_TOKEN_MISMATCH` with retry hints (`canRetryWithDeviceToken=true`) → one trusted device-token retry may occur automatically.
-    - That cached-token retry reuses the cached scope set stored with the paired
-      device token. Explicit `deviceToken` / explicit `scopes` callers keep
-      their requested scope set instead.
-    - On the async Tailscale Serve Control UI path, failed attempts for the same
-      `{scope, ip}` are serialized before the limiter records the failure, so a
-      second concurrent bad retry can already show `retry later`.
-    - `too many failed authentication attempts (retry later)` from a localhost
-      browser origin → repeated failures from that same `Origin` are temporarily
-      locked out; another localhost origin uses a separate bucket.
-    - repeated `unauthorized` after that retry → wrong token/password, auth mode mismatch, or stale paired device token.
-    - `gateway connect failed:` → UI is targeting the wrong URL/port or unreachable gateway.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#dashboard-control-ui-connectivity](/gateway/troubleshooting#dashboard-control-ui-connectivity)
-    - [/web/control-ui](/web/control-ui)
-    - [/gateway/authentication](/gateway/authentication)
-
-  </Accordion>
-
-  <Accordion title="Gateway will not start or service installed but not running">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming logs --follow
-    fengming doctor
-    fengming channels status --probe
-    ```
-
-    Good output looks like:
-
-    - `Service: ... (loaded)`
-    - `Runtime: running`
-    - `Connectivity probe: ok`
-    - `Capability: read-only`, `write-capable`, or `admin-capable`
-
-    Common log signatures:
-
-    - `Gateway start blocked: set gateway.mode=local` or `existing config is missing gateway.mode` → gateway mode is remote, or the config file is missing the local-mode stamp and should be repaired.
-    - `refusing to bind gateway ... without auth` → non-loopback bind without a valid gateway auth path (token/password, or trusted-proxy where configured).
-    - `another gateway instance is already listening` or `EADDRINUSE` → port already taken.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#gateway-service-not-running](/gateway/troubleshooting#gateway-service-not-running)
-    - [/gateway/background-process](/gateway/background-process)
-    - [/gateway/configuration](/gateway/configuration)
-
-  </Accordion>
-
-  <Accordion title="Channel connects but messages do not flow">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming logs --follow
-    fengming doctor
-    fengming channels status --probe
-    ```
-
-    Good output looks like:
-
-    - Channel transport is connected.
-    - Pairing/allowlist checks pass.
-    - Mentions are detected where required.
-
-    Common log signatures:
-
-    - `mention required` → group mention gating blocked processing.
-    - `pairing` / `pending` → DM sender is not approved yet.
-    - `not_in_channel`, `missing_scope`, `Forbidden`, `401/403` → channel permission token issue.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#channel-connected-messages-not-flowing](/gateway/troubleshooting#channel-connected-messages-not-flowing)
-    - [/channels/troubleshooting](/channels/troubleshooting)
-
-  </Accordion>
-
-  <Accordion title="Cron or heartbeat did not fire or did not deliver">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming cron status
-    fengming cron list
-    fengming cron runs --id <jobId> --limit 20
-    fengming logs --follow
-    ```
-
-    Good output looks like:
-
-    - `cron.status` shows enabled with a next wake.
-    - `cron runs` shows recent `ok` entries.
-    - Heartbeat is enabled and not outside active hours.
-
-    Common log signatures:
-
-    - `cron: scheduler disabled; jobs will not run automatically` → cron is disabled.
-    - `heartbeat skipped` with `reason=quiet-hours` → outside configured active hours.
-    - `heartbeat skipped` with `reason=empty-heartbeat-file` → `HEARTBEAT.md` exists but only contains blank/header-only scaffolding.
-    - `heartbeat skipped` with `reason=no-tasks-due` → `HEARTBEAT.md` task mode is active but none of the task intervals are due yet.
-    - `heartbeat skipped` with `reason=alerts-disabled` → all heartbeat visibility is disabled (`showOk`, `showAlerts`, and `useIndicator` are all off).
-    - `requests-in-flight` → main lane busy; heartbeat wake was deferred.
-    - `unknown accountId` → heartbeat delivery target account does not exist.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#cron-and-heartbeat-delivery](/gateway/troubleshooting#cron-and-heartbeat-delivery)
-    - [/automation/cron-jobs#troubleshooting](/automation/cron-jobs#troubleshooting)
-    - [/gateway/heartbeat](/gateway/heartbeat)
-
-  </Accordion>
-
-  <Accordion title="Node is paired but tool fails camera canvas screen exec">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming nodes status
-    fengming nodes describe --node <idOrNameOrIp>
-    fengming logs --follow
-    ```
-
-    Good output looks like:
-
-    - Node is listed as connected and paired for role `node`.
-    - Capability exists for the command you are invoking.
-    - Permission state is granted for the tool.
-
-    Common log signatures:
-
-    - `NODE_BACKGROUND_UNAVAILABLE` → bring node app to foreground.
-    - `*_PERMISSION_REQUIRED` → OS permission was denied/missing.
-    - `SYSTEM_RUN_DENIED: approval required` → exec approval is pending.
-    - `SYSTEM_RUN_DENIED: allowlist miss` → command not on exec allowlist.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#node-paired-tool-fails](/gateway/troubleshooting#node-paired-tool-fails)
-    - [/nodes/troubleshooting](/nodes/troubleshooting)
-    - [/tools/exec-approvals](/tools/exec-approvals)
-
-  </Accordion>
-
-  <Accordion title="Exec suddenly asks for approval">
-    ```bash
-    fengming config get tools.exec.host
-    fengming config get tools.exec.security
-    fengming config get tools.exec.ask
-    fengming gateway restart
-    ```
-
-    What changed:
-
-    - If `tools.exec.host` is unset, the default is `auto`.
-    - `host=auto` resolves to `sandbox` when a sandbox runtime is active, `gateway` otherwise.
-    - `host=auto` is routing only; the no-prompt "YOLO" behavior comes from `security=full` plus `ask=off` on gateway/node.
-    - On `gateway` and `node`, unset `tools.exec.security` defaults to `full`.
-    - Unset `tools.exec.ask` defaults to `off`.
-    - Result: if you are seeing approvals, some host-local or per-session policy tightened exec away from the current defaults.
-
-    Restore current default no-approval behavior:
-
-    ```bash
-    fengming config set tools.exec.host gateway
-    fengming config set tools.exec.security full
-    fengming config set tools.exec.ask off
-    fengming gateway restart
-    ```
-
-    Safer alternatives:
-
-    - Set only `tools.exec.host=gateway` if you just want stable host routing.
-    - Use `security=allowlist` with `ask=on-miss` if you want host exec but still want review on allowlist misses.
-    - Enable sandbox mode if you want `host=auto` to resolve back to `sandbox`.
-
-    Common log signatures:
-
-    - `Approval required.` → command is waiting on `/approve ...`.
-    - `SYSTEM_RUN_DENIED: approval required` → node-host exec approval is pending.
-    - `exec host=sandbox requires a sandbox runtime for this session` → implicit/explicit sandbox selection but sandbox mode is off.
-
-    Deep pages:
-
-    - [/tools/exec](/tools/exec)
-    - [/tools/exec-approvals](/tools/exec-approvals)
-    - [/gateway/security#what-the-audit-checks-high-level](/gateway/security#what-the-audit-checks-high-level)
-
-  </Accordion>
-
-  <Accordion title="Browser tool fails">
-    ```bash
-    fengming status
-    fengming gateway status
-    fengming browser status
-    fengming logs --follow
-    fengming doctor
-    ```
-
-    Good output looks like:
-
-    - Browser status shows `running: true` and a chosen browser/profile.
-    - `fengming` starts, or `user` can see local Chrome tabs.
-
-    Common log signatures:
-
-    - `unknown command "browser"` or `unknown command 'browser'` → `plugins.allow` is set and does not include `browser`.
-    - `Failed to start Chrome CDP on port` → local browser launch failed.
-    - `browser.executablePath not found` → configured binary path is wrong.
-    - `browser.cdpUrl must be http(s) or ws(s)` → the configured CDP URL uses an unsupported scheme.
-    - `browser.cdpUrl has invalid port` → the configured CDP URL has a bad or out-of-range port.
-    - `No Chrome tabs found for profile="user"` → the Chrome MCP attach profile has no open local Chrome tabs.
-    - `Remote CDP for profile "<name>" is not reachable` → the configured remote CDP endpoint is not reachable from this host.
-    - `Browser attachOnly is enabled ... not reachable` or `Browser attachOnly is enabled and CDP websocket ... is not reachable` → attach-only profile has no live CDP target.
-    - stale viewport / dark-mode / locale / offline overrides on attach-only or remote CDP profiles → run `fengming browser stop --browser-profile <name>` to close the active control session and release emulation state without restarting the gateway.
-
-    Deep pages:
-
-    - [/gateway/troubleshooting#browser-tool-fails](/gateway/troubleshooting#browser-tool-fails)
-    - [/tools/browser#missing-browser-command-or-tool](/tools/browser#missing-browser-command-or-tool)
-    - [/tools/browser-linux-troubleshooting](/tools/browser-linux-troubleshooting)
-    - [/tools/browser-wsl2-windows-remote-cdp-troubleshooting](/tools/browser-wsl2-windows-remote-cdp-troubleshooting)
-
-  </Accordion>
-
-</AccordionGroup>
-
-## Related
-
-- [FAQ](/help/faq) — frequently asked questions
-- [Gateway Troubleshooting](/gateway/troubleshooting) — gateway-specific issues
-- [Doctor](/gateway/doctor) — automated health checks and repairs
-- [Channel Troubleshooting](/channels/troubleshooting) — channel connectivity issues
-- [Automation Troubleshooting](/automation/cron-jobs#troubleshooting) — cron and heartbeat issues

package/docs/index.md

@@ -1,196 +0,0 @@
----
-summary: "FengMing is a multi-channel gateway for AI agents that runs on any OS."
-read_when:
-  - Introducing FengMing to newcomers
-title: "FengMing"
----
-
-# FengMing 🦞
-
-<p align="center">
-    <img
-        src="/assets/fengming-logo-text-dark.png"
-        alt="FengMing"
-        width="500"
-        class="dark:hidden"
-    />
-    <img
-        src="/assets/fengming-logo-text.png"
-        alt="FengMing"
-        width="500"
-        class="hidden dark:block"
-    />
-</p>
-
-> _"EXFOLIATE! EXFOLIATE!"_ — A space lobster, probably
-
-<p align="center">
-  <strong>Any OS gateway for AI agents across Discord, Google Chat, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, Zalo, and more.</strong><br />
-  Send a message, get an agent response from your pocket. Run one Gateway across built-in channels, bundled channel plugins, WebChat, and mobile nodes.
-</p>
-
-<Columns>
-  <Card title="Get Started" href="/start/getting-started" icon="rocket">
-    Install FengMing and bring up the Gateway in minutes.
-  </Card>
-  <Card title="Run Onboarding" href="/start/wizard" icon="sparkles">
-    Guided setup with `fengming onboard` and pairing flows.
-  </Card>
-  <Card title="Open the Control UI" href="/web/control-ui" icon="layout-dashboard">
-    Launch the browser dashboard for chat, config, and sessions.
-  </Card>
-</Columns>
-
-## What is FengMing?
-
-FengMing is a **self-hosted gateway** that connects your favorite chat apps and channel surfaces — built-in channels plus bundled or external channel plugins such as Discord, Google Chat, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, Zalo, and more — to AI coding agents. You run a single Gateway process on your own machine (or a server), and it becomes the bridge between your messaging apps and an always-available AI assistant.
-
-**Who is it for?** Developers and power users who want a personal AI assistant they can message from anywhere — without giving up control of their data or relying on a hosted service.
-
-**What makes it different?**
-
-- **Self-hosted**: runs on your hardware, your rules
-- **Multi-channel**: one Gateway serves built-in channels plus bundled or external channel plugins simultaneously
-- **Agent-native**: built for coding agents with tool use, sessions, memory, and multi-agent routing
-- **Open source**: MIT licensed, community-driven
-
-**What do you need?** Node 24 (recommended), or Node 22 LTS (`22.19+`) for compatibility, an API key from your chosen provider, and 5 minutes. For best quality and security, use the strongest latest-generation model available.
-
-## How it works
-
-```mermaid
-flowchart LR
-  A["Chat apps + plugins"] --> B["Gateway"]
-  B --> C["FengMing agent"]
-  B --> D["CLI"]
-  B --> E["Web Control UI"]
-  B --> F["macOS app"]
-  B --> G["iOS and Android nodes"]
-```
-
-The Gateway is the single source of truth for sessions, routing, and channel connections.
-
-## Key capabilities
-
-<Columns>
-  <Card title="Multi-channel gateway" icon="network" href="/channels">
-    Discord, iMessage, Signal, Slack, Telegram, WhatsApp, WebChat, and more with a single Gateway process.
-  </Card>
-  <Card title="Plugin channels" icon="plug" href="/tools/plugin">
-    Bundled plugins add Matrix, Nostr, Twitch, Zalo, and more in normal current releases.
-  </Card>
-  <Card title="Multi-agent routing" icon="route" href="/concepts/multi-agent">
-    Isolated sessions per agent, workspace, or sender.
-  </Card>
-  <Card title="Media support" icon="image" href="/nodes/images">
-    Send and receive images, audio, and documents.
-  </Card>
-  <Card title="Web Control UI" icon="monitor" href="/web/control-ui">
-    Browser dashboard for chat, config, sessions, and nodes.
-  </Card>
-  <Card title="Mobile nodes" icon="smartphone" href="/nodes">
-    Pair iOS and Android nodes for Canvas, camera, and voice-enabled workflows.
-  </Card>
-</Columns>
-
-## Quick start
-
-<Steps>
-  <Step title="Install FengMing">
-    ```bash
-    npm install -g fengming@latest
-    ```
-  </Step>
-  <Step title="Onboard and install the service">
-    ```bash
-    fengming onboard --install-daemon
-    ```
-  </Step>
-  <Step title="Chat">
-    Open the Control UI in your browser and send a message:
-
-    ```bash
-    fengming dashboard
-    ```
-
-    Or connect a channel ([Telegram](/channels/telegram) is fastest) and chat from your phone.
-
-  </Step>
-</Steps>
-
-Need the full install and dev setup? See [Getting Started](/start/getting-started).
-
-## Dashboard
-
-Open the browser Control UI after the Gateway starts.
-
-- Local default: [http://127.0.0.1:18789/](http://127.0.0.1:18789/)
-- Remote access: [Web surfaces](/web) and [Tailscale](/gateway/tailscale)
-
-<p align="center">
-  <img src="/whatsapp-fengming.jpg" alt="FengMing" width="420" />
-</p>
-
-## Configuration (optional)
-
-Config lives at `~/.fengming/fengming.json`.
-
-- If you **do nothing**, FengMing uses the bundled FengMing agent runtime with per-sender sessions.
-- If you want to lock it down, start with `channels.whatsapp.allowFrom` and (for groups) mention rules.
-
-Example:
-
-```json5
-{
-  channels: {
-    whatsapp: {
-      allowFrom: ["+15555550123"],
-      groups: { "*": { requireMention: true } },
-    },
-  },
-  messages: { groupChat: { mentionPatterns: ["@fengming"] } },
-}
-```
-
-## Start here
-
-<Columns>
-  <Card title="Docs hubs" href="/start/hubs" icon="book-open">
-    All docs and guides, organized by use case.
-  </Card>
-  <Card title="Configuration" href="/gateway/configuration" icon="settings">
-    Core Gateway settings, tokens, and provider config.
-  </Card>
-  <Card title="Remote access" href="/gateway/remote" icon="globe">
-    SSH and tailnet access patterns.
-  </Card>
-  <Card title="Channels" href="/channels/telegram" icon="message-square">
-    Channel-specific setup for Feishu, Microsoft Teams, WhatsApp, Telegram, Discord, and more.
-  </Card>
-  <Card title="Nodes" href="/nodes" icon="smartphone">
-    iOS and Android nodes with pairing, Canvas, camera, and device actions.
-  </Card>
-  <Card title="Help" href="/help" icon="life-buoy">
-    Common fixes and troubleshooting entry point.
-  </Card>
-</Columns>
-
-## Learn more
-
-<Columns>
-  <Card title="Full feature list" href="/concepts/features" icon="list">
-    Complete channel, routing, and media capabilities.
-  </Card>
-  <Card title="Multi-agent routing" href="/concepts/multi-agent" icon="route">
-    Workspace isolation and per-agent sessions.
-  </Card>
-  <Card title="Security" href="/gateway/security" icon="shield">
-    Tokens, allowlists, and safety controls.
-  </Card>
-  <Card title="Troubleshooting" href="/gateway/troubleshooting" icon="wrench">
-    Gateway diagnostics and common errors.
-  </Card>
-  <Card title="About and credits" href="/reference/credits" icon="info">
-    Project origins, contributors, and license.
-  </Card>
-</Columns>