pllan 2026.3.47 → 2026.3.49

package/docs/nb/automation/cron-jobs.md

@@ -9,7 +9,7 @@ title: "Cron Jobs"
 
 # Cron jobs (Gateway scheduler)
 
-> **Cron vs Heartbeat?** See [Cron vs Heartbeat](/automation/cron-vs-heartbeat) for guidance on when to use each.
+> **Cron vs Heartbeat?** See [Cron vs Heartbeat](/nb/automation/cron-vs-heartbeat) for guidance on when to use each.
 
 Cron is the Gateway’s built-in scheduler. It persists jobs, wakes the agent at
 the right time, and can optionally deliver output back to a chat.
@@ -17,7 +17,7 @@ the right time, and can optionally deliver output back to a chat.
 If you want _“run this every morning”_ or _“poke the agent in 20 minutes”_,
 cron is the mechanism.
 
-Troubleshooting: [/automation/troubleshooting](/automation/troubleshooting)
+Troubleshooting: [/automation/troubleshooting](/nb/automation/troubleshooting)
 
 ## TL;DR
 
@@ -67,7 +67,7 @@ pllan cron add \
 
 ## Tool-call equivalents (Gateway cron tool)
 
-For the canonical JSON shapes and examples, see [JSON schema for tool calls](/automation/cron-jobs#json-schema-for-tool-calls).
+For the canonical JSON shapes and examples, see [JSON schema for tool calls](/nb/automation/cron-jobs#json-schema-for-tool-calls).
 
 ## Where cron jobs are stored
 
@@ -153,7 +153,7 @@ They must use `payload.kind = "systemEvent"`.
 - `wakeMode: "next-heartbeat"`: event waits for the next scheduled heartbeat.
 
 This is the best fit when you want the normal heartbeat prompt + main-session context.
-See [Heartbeat](/gateway/heartbeat).
+See [Heartbeat](/nb/gateway/heartbeat).
 
 #### Isolated jobs (dedicated cron sessions)
 
@@ -437,7 +437,7 @@ When a job fails, Pllan classifies errors as **transient** (retryable) or **perm
 - On any error: apply exponential backoff (30s → 1m → 5m → 15m → 60m) before the next scheduled run.
 - Job stays enabled; backoff resets after the next successful run.
 
-Configure `cron.retry` to override these defaults (see [Configuration](/automation/cron-jobs#configuration)).
+Configure `cron.retry` to override these defaults (see [Configuration](/nb/automation/cron-jobs#configuration)).
 
 ## Configuration
 
@@ -696,7 +696,7 @@ pllan system event --mode now --text "Next heartbeat: check battery."
 
 - `cron.list`, `cron.status`, `cron.add`, `cron.update`, `cron.remove`
 - `cron.run` (force or due), `cron.runs`
-  For immediate system events without a job, use [`pllan system event`](/cli/system).
+  For immediate system events without a job, use [`pllan system event`](/nb/cli/system).
 
 ## Troubleshooting
 
@@ -711,7 +711,7 @@ pllan system event --mode now --text "Next heartbeat: check battery."
 - Pllan applies exponential retry backoff for recurring jobs after consecutive errors:
   30s, 1m, 5m, 15m, then 60m between retries.
 - Backoff resets automatically after the next successful run.
-- One-shot (`at`) jobs retry transient errors (rate limit, overloaded, network, server_error) up to 3 times with backoff; permanent errors disable immediately. See [Retry policy](/automation/cron-jobs#retry-policy).
+- One-shot (`at`) jobs retry transient errors (rate limit, overloaded, network, server_error) up to 3 times with backoff; permanent errors disable immediately. See [Retry policy](/nb/automation/cron-jobs#retry-policy).
 
 ### Telegram delivers to the wrong place
 

package/docs/nb/automation/cron-vs-heartbeat.md

@@ -70,7 +70,7 @@ The agent reads this on each heartbeat and handles all items in one turn.
 }
 ```
 
-See [Heartbeat](/gateway/heartbeat) for full configuration.
+See [Heartbeat](/nb/gateway/heartbeat) for full configuration.
 
 ## Cron: Precise Scheduling
 
@@ -128,7 +128,7 @@ pllan cron add \
   --delete-after-run
 ```
 
-See [Cron jobs](/automation/cron-jobs) for full CLI reference.
+See [Cron jobs](/nb/automation/cron-jobs) for full CLI reference.
 
 ## Decision Flowchart
 
@@ -213,7 +213,7 @@ For ad-hoc workflows, call pllan directly.
 - The tool is an **optional plugin**; enable it additively via `tools.alsoAllow: ["pllan"]` (recommended).
 - pllan expects the `pllan` CLI to be available on `PATH`.
 
-See [pllan](/tools/pllan) for full usage and examples.
+See [pllan](/nb/tools/pllan) for full usage and examples.
 
 ## Main Session vs Isolated Session
 
@@ -281,6 +281,6 @@ pllan cron add \
 
 ## Related
 
-- [Heartbeat](/gateway/heartbeat) - full heartbeat configuration
-- [Cron jobs](/automation/cron-jobs) - full cron CLI and API reference
-- [System](/cli/system) - system events + heartbeat controls
+- [Heartbeat](/nb/gateway/heartbeat) - full heartbeat configuration
+- [Cron jobs](/nb/automation/cron-jobs) - full cron CLI and API reference
+- [System](/nb/cli/system) - system events + heartbeat controls

package/docs/nb/automation/gmail-pubsub.md

@@ -14,7 +14,7 @@ Goal: Gmail watch -> Pub/Sub push -> `gog gmail watch serve` -> Pllan webhook.
 
 - `gcloud` installed and logged in ([install guide](https://docs.cloud.google.com/sdk/docs/install-sdk)).
 - `gog` (gogcli) installed and authorized for the Gmail account ([gogcli.sh](https://gogcli.sh/)).
-- Pllan hooks enabled (see [Webhooks](/automation/webhook)).
+- Pllan hooks enabled (see [Webhooks](/nb/automation/webhook)).
 - `tailscale` logged in ([tailscale.com](https://tailscale.com/)). Supported setup uses Tailscale Funnel for the public HTTPS endpoint.
   Other tunnel services can work, but are DIY/unsupported and require manual wiring.
   Right now, Tailscale is what we support.
@@ -88,7 +88,7 @@ Notes:
   To disable (dangerous), set `hooks.gmail.allowUnsafeExternalContent: true`.
 
 To customize payload handling further, add `hooks.mappings` or a JS/TS transform module
-under `~/.pllan/hooks/transforms` (see [Webhooks](/automation/webhook)).
+under `~/.pllan/hooks/transforms` (see [Webhooks](/nb/automation/webhook)).
 
 ## Wizard (recommended)
 

package/docs/nb/automation/hooks.md

@@ -15,9 +15,9 @@ Hooks provide an extensible event-driven system for automating actions in respon
 Hooks are small scripts that run when something happens. There are two kinds:
 
 - **Hooks** (this page): run inside the Gateway when agent events fire, like `/new`, `/reset`, `/stop`, or lifecycle events.
-- **Webhooks**: external HTTP webhooks that let other systems trigger work in Pllan. See [Webhook Hooks](/automation/webhook) or use `pllan webhooks` for Gmail helper commands.
+- **Webhooks**: external HTTP webhooks that let other systems trigger work in Pllan. See [Webhook Hooks](/nb/automation/webhook) or use `pllan webhooks` for Gmail helper commands.
 
-Hooks can also be bundled inside plugins; see [Plugin hooks](/plugins/architecture#provider-runtime-hooks).
+Hooks can also be bundled inside plugins; see [Plugin hooks](/nb/plugins/architecture#provider-runtime-hooks).
 
 Common uses:
 
@@ -362,7 +362,7 @@ export default handler;
 
 These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before Pllan persists them.
 
-- **`tool_result_persist`**: transform tool results before they are written to the session transcript. Must be synchronous; return the updated tool result payload or `undefined` to keep it as-is. See [Agent Loop](/concepts/agent-loop).
+- **`tool_result_persist`**: transform tool results before they are written to the session transcript. Must be synchronous; return the updated tool result payload or `undefined` to keep it as-is. See [Agent Loop](/nb/concepts/agent-loop).
 
 ### Plugin Hook Events
 
@@ -1043,7 +1043,7 @@ node -e "import('./path/to/handler.ts').then(console.log)"
 
 ## See Also
 
-- [CLI Reference: hooks](/cli/hooks)
+- [CLI Reference: hooks](/nb/cli/hooks)
 - [Bundled Hooks README](https://github.com/pllan/pllan/tree/main/src/hooks/bundled)
-- [Webhook Hooks](/automation/webhook)
-- [Configuration](/gateway/configuration-reference#hooks)
+- [Webhook Hooks](/nb/automation/webhook)
+- [Configuration](/nb/gateway/configuration-reference#hooks)

package/docs/nb/automation/troubleshooting.md

@@ -116,7 +116,7 @@ Common signatures:
 
 Related:
 
-- [/automation/cron-jobs](/automation/cron-jobs)
-- [/gateway/heartbeat](/gateway/heartbeat)
-- [/automation/cron-vs-heartbeat](/automation/cron-vs-heartbeat)
-- [/concepts/timezone](/concepts/timezone)
+- [/automation/cron-jobs](/nb/automation/cron-jobs)
+- [/gateway/heartbeat](/nb/gateway/heartbeat)
+- [/automation/cron-vs-heartbeat](/nb/automation/cron-vs-heartbeat)
+- [/concepts/timezone](/nb/concepts/timezone)

package/docs/nb/automation/webhook.md

@@ -155,7 +155,7 @@ Mapping options (summary):
 - `allowUnsafeExternalContent: true` disables the external content safety wrapper for that hook
   (dangerous; only for trusted internal sources).
 - `pllan webhooks gmail setup` writes `hooks.gmail` config for `pllan webhooks gmail run`.
-  See [Gmail Pub/Sub](/automation/gmail-pubsub) for the full Gmail watch flow.
+  See [Gmail Pub/Sub](/nb/automation/gmail-pubsub) for the full Gmail watch flow.
 
 ## Responses
 

package/docs/nb/brave-search.md

@@ -90,4 +90,4 @@ await web_search({
 - The Search plan includes the LLM Context endpoint and AI inference rights. Storing results to train or tune models requires a plan with explicit storage rights. See the Brave [Terms of Service](https://api-dashboard.search.brave.com/terms-of-service).
 - Results are cached for 15 minutes by default (configurable via `cacheTtlMinutes`).
 
-See [Web tools](/tools/web) for the full web_search configuration.
+See [Web tools](/nb/tools/web) for the full web_search configuration.

package/docs/nb/channels/bluebubbles.md

@@ -155,7 +155,7 @@ DMs:
 - Approve via:
   - `pllan pairing list bluebubbles`
   - `pllan pairing approve bluebubbles <CODE>`
-- Pairing is the default token exchange. Details: [Pairing](/channels/pairing)
+- Pairing is the default token exchange. Details: [Pairing](/nb/channels/pairing)
 
 Groups:
 
@@ -264,7 +264,7 @@ Use full IDs for durable automations and storage:
 - Templates: `{{MessageSidFull}}`, `{{ReplyToIdFull}}`
 - Context: `MessageSidFull` / `ReplyToIdFull` in inbound payloads
 
-See [Configuration](/gateway/configuration) for template variables.
+See [Configuration](/nb/gateway/configuration) for template variables.
 
 ## Block streaming
 
@@ -288,7 +288,7 @@ Control whether responses are sent as a single message or streamed in blocks:
 
 ## Configuration reference
 
-Full configuration: [Configuration](/gateway/configuration)
+Full configuration: [Configuration](/nb/gateway/configuration)
 
 Provider options:
 
@@ -331,7 +331,7 @@ Prefer `chat_guid` for stable routing:
 
 - Webhook requests are authenticated by comparing `guid`/`password` query params or headers against `channels.bluebubbles.password`. Requests from `localhost` are also accepted.
 - Keep the API password and webhook endpoint secret (treat them like credentials).
-- Localhost trust means a same-host reverse proxy can unintentionally bypass the password. If you proxy the gateway, require auth at the proxy and configure `gateway.trustedProxies`. See [Gateway security](/gateway/security#reverse-proxy-configuration).
+- Localhost trust means a same-host reverse proxy can unintentionally bypass the password. If you proxy the gateway, require auth at the proxy and configure `gateway.trustedProxies`. See [Gateway security](/nb/gateway/security#reverse-proxy-configuration).
 - Enable HTTPS + firewall rules on the BlueBubbles server if exposing it outside your LAN.
 
 ## Troubleshooting
@@ -344,4 +344,4 @@ Prefer `chat_guid` for stable routing:
 - Pllan auto-hides known-broken actions based on the BlueBubbles server's macOS version. If edit still appears on macOS 26 (Tahoe), disable it manually with `channels.bluebubbles.actions.edit=false`.
 - For status/health info: `pllan status --all` or `pllan status --deep`.
 
-For general channel workflow reference, see [Channels](/channels) and the [Plugins](/tools/plugin) guide.
+For general channel workflow reference, see [Channels](/nb/channels) and the [Plugins](/nb/tools/plugin) guide.

package/docs/nb/channels/broadcast-groups.md

@@ -437,6 +437,6 @@ Planned features:
 
 ## See Also
 
-- [Multi-Agent Configuration](/tools/multi-agent-sandbox-tools)
-- [Routing Configuration](/channels/channel-routing)
-- [Session Management](/concepts/session)
+- [Multi-Agent Configuration](/nb/tools/multi-agent-sandbox-tools)
+- [Routing Configuration](/nb/channels/channel-routing)
+- [Session Management](/nb/concepts/session)

package/docs/nb/channels/channel-routing.md

@@ -88,7 +88,7 @@ Config:
 }
 ```
 
-See: [Broadcast Groups](/channels/broadcast-groups).
+See: [Broadcast Groups](/nb/channels/broadcast-groups).
 
 ## Config overview
 

package/docs/nb/channels/discord.md

@@ -10,13 +10,13 @@ title: "Discord"
 Status: ready for DMs and guild channels via the official Discord gateway.
 
 <CardGroup cols={3}>
-  <Card title="Pairing" icon="link" href="/channels/pairing">
+  <Card title="Pairing" icon="link" href="/nb/channels/pairing">
     Discord DMs default to pairing mode.
   </Card>
-  <Card title="Slash commands" icon="terminal" href="/tools/slash-commands">
+  <Card title="Slash commands" icon="terminal" href="/nb/tools/slash-commands">
     Native command behavior and command catalog.
   </Card>
-  <Card title="Channel troubleshooting" icon="wrench" href="/channels/troubleshooting">
+  <Card title="Channel troubleshooting" icon="wrench" href="/nb/channels/troubleshooting">
     Cross-channel diagnostics and repair flow.
   </Card>
 </CardGroup>
@@ -139,7 +139,7 @@ pllan gateway
 DISCORD_BOT_TOKEN=...
 ```
 
-        Plaintext `token` values are supported. SecretRef values are also supported for `channels.discord.token` across env/file/exec providers. See [Secrets Management](/gateway/secrets).
+        Plaintext `token` values are supported. SecretRef values are also supported for `channels.discord.token` across env/file/exec providers. See [Secrets Management](/nb/gateway/secrets).
 
       </Tab>
     </Tabs>
@@ -551,7 +551,7 @@ Use `bindings[].match.roles` to route Discord guild members to different agents
 - Native command auth uses the same Discord allowlists/policies as normal message handling.
 - Commands may still be visible in Discord UI for users who are not authorized; execution still enforces Pllan auth and returns "not authorized".
 
-See [Slash commands](/tools/slash-commands) for command catalog and behavior.
+See [Slash commands](/nb/tools/slash-commands) for command catalog and behavior.
 
 Default slash command settings:
 
@@ -688,7 +688,7 @@ Default slash command settings:
     - `spawnAcpSessions` must be true to auto-create/bind threads for ACP (`/acp spawn ... --thread ...` or `sessions_spawn({ runtime: "acp", thread: true })`).
     - If thread bindings are disabled for an account, `/focus` and related thread binding operations are unavailable.
 
-    See [Sub-agents](/tools/subagents), [ACP Agents](/tools/acp-agents), and [Configuration Reference](/gateway/configuration-reference).
+    See [Sub-agents](/nb/tools/subagents), [ACP Agents](/nb/tools/acp-agents), and [Configuration Reference](/nb/gateway/configuration-reference).
 
   </Accordion>
 
@@ -753,7 +753,7 @@ Default slash command settings:
     - In a bound channel or thread, `/new` and `/reset` reset the same ACP session in place.
     - Temporary thread bindings still work and can override target resolution while active.
 
-    See [ACP Agents](/tools/acp-agents) for binding behavior details.
+    See [ACP Agents](/nb/tools/acp-agents) for binding behavior details.
 
   </Accordion>
 
@@ -958,7 +958,7 @@ Default slash command settings:
 
     If approvals fail with unknown approval IDs, verify approver list and feature enablement.
 
-    Related docs: [Exec approvals](/tools/exec-approvals)
+    Related docs: [Exec approvals](/nb/tools/exec-approvals)
 
   </Accordion>
 </AccordionGroup>
@@ -1195,7 +1195,7 @@ pllan logs --follow
 
 Primary reference:
 
-- [Configuration reference - Discord](/gateway/configuration-reference#discord)
+- [Configuration reference - Discord](/nb/gateway/configuration-reference#discord)
 
 High-signal Discord fields:
 
@@ -1222,8 +1222,8 @@ High-signal Discord fields:
 
 ## Related
 
-- [Pairing](/channels/pairing)
-- [Channel routing](/channels/channel-routing)
-- [Multi-agent routing](/concepts/multi-agent)
-- [Troubleshooting](/channels/troubleshooting)
-- [Slash commands](/tools/slash-commands)
+- [Pairing](/nb/channels/pairing)
+- [Channel routing](/nb/channels/channel-routing)
+- [Multi-agent routing](/nb/concepts/multi-agent)
+- [Troubleshooting](/nb/channels/troubleshooting)
+- [Slash commands](/nb/tools/slash-commands)

package/docs/nb/channels/feishu.md

@@ -660,7 +660,7 @@ See [Get group/user IDs](#get-groupuser-ids) for lookup tips.
 
 ## Configuration reference
 
-Full configuration: [Gateway configuration](/gateway/configuration)
+Full configuration: [Gateway configuration](/nb/gateway/configuration)
 
 Key options:
 

package/docs/nb/channels/googlechat.md

@@ -204,7 +204,7 @@ Notes:
 - `typingIndicator` supports `none`, `message` (default), and `reaction` (reaction requires user OAuth).
 - Attachments are downloaded through the Chat API and stored in the media pipeline (size capped by `mediaMaxMb`).
 
-Secrets reference details: [Secrets Management](/gateway/secrets).
+Secrets reference details: [Secrets Management](/nb/gateway/secrets).
 
 ## Troubleshooting
 
@@ -256,6 +256,6 @@ pllan channels status
 
 Related docs:
 
-- [Gateway configuration](/gateway/configuration)
-- [Security](/gateway/security)
-- [Reactions](/tools/reactions)
+- [Gateway configuration](/nb/gateway/configuration)
+- [Security](/nb/gateway/security)
+- [Reactions](/nb/tools/reactions)

package/docs/nb/channels/groups.md

@@ -36,7 +36,7 @@ requireMention? yes -> mentioned? no -> store for context only
 otherwise -> reply
 ```
 
-![Group message flow](/images/groups-flow.svg)
+![Group message flow](/nb/images/groups-flow.svg)
 
 If you want...
 
@@ -65,7 +65,7 @@ This gives you one agent “brain” (shared workspace + memory), but two execut
 - **DMs**: full tools (host)
 - **Groups**: sandbox + restricted tools (Docker)
 
-> If you need truly separate workspaces/personas (“personal” and “public” must never mix), use a second agent + bindings. See [Multi-Agent Routing](/concepts/multi-agent).
+> If you need truly separate workspaces/personas (“personal” and “public” must never mix), use a second agent + bindings. See [Multi-Agent Routing](/nb/concepts/multi-agent).
 
 Example (DMs on host, groups sandboxed + messaging-only tools):
 
@@ -116,9 +116,9 @@ Want “groups can only see folder X” instead of “no host access”? Keep `w
 
 Related:
 
-- Configuration keys and defaults: [Gateway configuration](/gateway/configuration-reference#agents-defaults-sandbox)
-- Debugging why a tool is blocked: [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated)
-- Bind mounts details: [Sandboxing](/gateway/sandboxing#custom-bind-mounts)
+- Configuration keys and defaults: [Gateway configuration](/nb/gateway/configuration-reference#agents-defaults-sandbox)
+- Debugging why a tool is blocked: [Sandbox vs Tool Policy vs Elevated](/nb/gateway/sandbox-vs-tool-policy-vs-elevated)
+- Bind mounts details: [Sandboxing](/nb/gateway/sandboxing#custom-bind-mounts)
 
 ## Display labels
 
@@ -376,4 +376,4 @@ The agent system prompt includes a group intro on the first turn of a new group
 
 ## WhatsApp specifics
 
-See [Group messages](/channels/group-messages) for WhatsApp-only behavior (history injection, mention handling details).
+See [Group messages](/nb/channels/group-messages) for WhatsApp-only behavior (history injection, mention handling details).

package/docs/nb/channels/imessage.md

@@ -9,7 +9,7 @@ title: "iMessage"
 # iMessage (legacy: imsg)
 
 <Warning>
-For new iMessage deployments, use <a href="/channels/bluebubbles">BlueBubbles</a>.
+For new iMessage deployments, use <a href="/nb/channels/bluebubbles">BlueBubbles</a>.
 
 The `imsg` integration is legacy and may be removed in a future release.
 </Warning>
@@ -17,13 +17,13 @@ The `imsg` integration is legacy and may be removed in a future release.
 Status: legacy external CLI integration. Gateway spawns `imsg rpc` and communicates over JSON-RPC on stdio (no separate daemon/port).
 
 <CardGroup cols={3}>
-  <Card title="BlueBubbles (recommended)" icon="message-circle" href="/channels/bluebubbles">
+  <Card title="BlueBubbles (recommended)" icon="message-circle" href="/nb/channels/bluebubbles">
     Preferred iMessage path for new setups.
   </Card>
-  <Card title="Pairing" icon="link" href="/channels/pairing">
+  <Card title="Pairing" icon="link" href="/nb/channels/pairing">
     iMessage DMs default to pairing mode.
   </Card>
-  <Card title="Configuration reference" icon="settings" href="/gateway/configuration-reference#imessage">
+  <Card title="Configuration reference" icon="settings" href="/nb/gateway/configuration-reference#imessage">
     Full iMessage field reference.
   </Card>
 </CardGroup>
@@ -361,7 +361,7 @@ imsg send <handle> "test"
 
 ## Configuration reference pointers
 
-- [Configuration reference - iMessage](/gateway/configuration-reference#imessage)
-- [Gateway configuration](/gateway/configuration)
-- [Pairing](/channels/pairing)
-- [BlueBubbles](/channels/bluebubbles)
+- [Configuration reference - iMessage](/nb/gateway/configuration-reference#imessage)
+- [Gateway configuration](/nb/gateway/configuration)
+- [Pairing](/nb/channels/pairing)
+- [BlueBubbles](/nb/channels/bluebubbles)

package/docs/nb/channels/index.md

@@ -13,35 +13,35 @@ Tekst stottes overalt; medie- og reaksjonsstotte varierer per kanal.
 
 ## Stottede kanaler
 
-- [BlueBubbles](/channels/bluebubbles) — **Anbefalt for iMessage**; bruker BlueBubbles macOS-server REST API med full funksjonstotte (redigering, angre sending, effekter, reaksjoner, gruppeadministrasjon — redigering er for oyeblikket odelatt pa macOS 26 Tahoe).
-- [Discord](/channels/discord) — Discord Bot API + Gateway; stotter servere, kanaler og DM-er.
-- [Feishu](/channels/feishu) — Feishu/Lark-bot via WebSocket (utvidelse, installeres separat).
-- [Google Chat](/channels/googlechat) — Google Chat API-app via HTTP-webhook.
-- [iMessage (eldre)](/channels/imessage) — Eldre macOS-integrasjon via imsg CLI (avviklet, bruk BlueBubbles for nye oppsett).
-- [IRC](/channels/irc) — Klassiske IRC-servere; kanaler + DM-er med sammenkobling/tilgangsliste-kontroller.
-- [LINE](/channels/line) — LINE Messaging API-bot (utvidelse, installeres separat).
-- [Matrix](/channels/matrix) — Matrix-protokoll (utvidelse, installeres separat).
-- [Mattermost](/channels/mattermost) — Bot API + WebSocket; kanaler, grupper, DM-er (utvidelse, installeres separat).
-- [Microsoft Teams](/channels/msteams) — Bot Framework; bedriftsstotte (utvidelse, installeres separat).
-- [Nextcloud Talk](/channels/nextcloud-talk) — Selvhostet chat via Nextcloud Talk (utvidelse, installeres separat).
-- [Nostr](/channels/nostr) — Desentraliserte DM-er via NIP-04 (utvidelse, installeres separat).
-- [Signal](/channels/signal) — signal-cli; personvernfokusert.
-- [Synology Chat](/channels/synology-chat) — Synology NAS Chat via utgaende+inngaende webhooks (utvidelse, installeres separat).
-- [Slack](/channels/slack) — Bolt SDK; arbeidsomrade-apper.
-- [Telegram](/channels/telegram) — Bot API via grammy; stotter grupper.
-- [Tlon](/channels/tlon) — Urbit-basert meldingstjeneste (utvidelse, installeres separat).
-- [Twitch](/channels/twitch) — Twitch-chat via IRC-tilkobling (utvidelse, installeres separat).
-- [WebChat](/web/webchat) — Gateway WebChat-grensesnitt over WebSocket.
-- [WhatsApp](/channels/whatsapp) — Mest populaer; bruker Baileys og krever QR-sammenkobling.
-- [Zalo](/channels/zalo) — Zalo Bot API; Vietnams populaere meldingstjeneste (utvidelse, installeres separat).
-- [Zalo Personlig](/channels/zalouser) — Zalo personlig konto via QR-innlogging (utvidelse, installeres separat).
+- [BlueBubbles](/nb/channels/bluebubbles) — **Anbefalt for iMessage**; bruker BlueBubbles macOS-server REST API med full funksjonstotte (redigering, angre sending, effekter, reaksjoner, gruppeadministrasjon — redigering er for oyeblikket odelatt pa macOS 26 Tahoe).
+- [Discord](/nb/channels/discord) — Discord Bot API + Gateway; stotter servere, kanaler og DM-er.
+- [Feishu](/nb/channels/feishu) — Feishu/Lark-bot via WebSocket (utvidelse, installeres separat).
+- [Google Chat](/nb/channels/googlechat) — Google Chat API-app via HTTP-webhook.
+- [iMessage (eldre)](/nb/channels/imessage) — Eldre macOS-integrasjon via imsg CLI (avviklet, bruk BlueBubbles for nye oppsett).
+- [IRC](/nb/channels/irc) — Klassiske IRC-servere; kanaler + DM-er med sammenkobling/tilgangsliste-kontroller.
+- [LINE](/nb/channels/line) — LINE Messaging API-bot (utvidelse, installeres separat).
+- [Matrix](/nb/channels/matrix) — Matrix-protokoll (utvidelse, installeres separat).
+- [Mattermost](/nb/channels/mattermost) — Bot API + WebSocket; kanaler, grupper, DM-er (utvidelse, installeres separat).
+- [Microsoft Teams](/nb/channels/msteams) — Bot Framework; bedriftsstotte (utvidelse, installeres separat).
+- [Nextcloud Talk](/nb/channels/nextcloud-talk) — Selvhostet chat via Nextcloud Talk (utvidelse, installeres separat).
+- [Nostr](/nb/channels/nostr) — Desentraliserte DM-er via NIP-04 (utvidelse, installeres separat).
+- [Signal](/nb/channels/signal) — signal-cli; personvernfokusert.
+- [Synology Chat](/nb/channels/synology-chat) — Synology NAS Chat via utgaende+inngaende webhooks (utvidelse, installeres separat).
+- [Slack](/nb/channels/slack) — Bolt SDK; arbeidsomrade-apper.
+- [Telegram](/nb/channels/telegram) — Bot API via grammy; stotter grupper.
+- [Tlon](/nb/channels/tlon) — Urbit-basert meldingstjeneste (utvidelse, installeres separat).
+- [Twitch](/nb/channels/twitch) — Twitch-chat via IRC-tilkobling (utvidelse, installeres separat).
+- [WebChat](/nb/web/webchat) — Gateway WebChat-grensesnitt over WebSocket.
+- [WhatsApp](/nb/channels/whatsapp) — Mest populaer; bruker Baileys og krever QR-sammenkobling.
+- [Zalo](/nb/channels/zalo) — Zalo Bot API; Vietnams populaere meldingstjeneste (utvidelse, installeres separat).
+- [Zalo Personlig](/nb/channels/zalouser) — Zalo personlig konto via QR-innlogging (utvidelse, installeres separat).
 
 ## Merknader
 
 - Kanaler kan kjore samtidig; konfigurer flere, og Pllan vil rute per chat.
 - Raskeste oppsett er vanligvis **Telegram** (enkelt bot-token). WhatsApp krever QR-sammenkobling og
   lagrer mer tilstand pa disk.
-- Gruppeoppforsel varierer per kanal; se [Grupper](/channels/groups).
-- DM-sammenkobling og tilgangslister handheves for sikkerhet; se [Sikkerhet](/gateway/security).
-- Feilsoking: [Kanalfeilsoking](/channels/troubleshooting).
-- Modellleverandorer er dokumentert separat; se [Modellleverandorer](/providers/models).
+- Gruppeoppforsel varierer per kanal; se [Grupper](/nb/channels/groups).
+- DM-sammenkobling og tilgangslister handheves for sikkerhet; se [Sikkerhet](/nb/gateway/security).
+- Feilsoking: [Kanalfeilsoking](/nb/channels/troubleshooting).
+- Modellleverandorer er dokumentert separat; se [Modellleverandorer](/nb/providers/models).

package/docs/nb/channels/irc.md

@@ -183,7 +183,7 @@ Notes:
 - Legacy unprefixed keys are still accepted and matched as `id:` only.
 - The first matching sender policy wins; `"*"` is the wildcard fallback.
 
-For more on group access vs mention-gating (and how they interact), see: [/channels/groups](/channels/groups).
+For more on group access vs mention-gating (and how they interact), see: [/channels/groups](/nb/channels/groups).
 
 ## NickServ
 

package/docs/nb/channels/matrix.md

@@ -27,7 +27,7 @@ Install from a local checkout:
 pllan plugins install ./extensions/matrix
 ```
 
-See [Plugins](/tools/plugin) for plugin behavior and install rules.
+See [Plugins](/nb/tools/plugin) for plugin behavior and install rules.
 
 ## Setup
 
@@ -233,7 +233,7 @@ Bootstrap cross-signing and verification state:
 pllan matrix verify bootstrap
 ```
 
-Multi-account support: use `channels.matrix.accounts` with per-account credentials and optional `name`. See [Configuration reference](/gateway/configuration-reference#multi-account-all-channels) for the shared pattern.
+Multi-account support: use `channels.matrix.accounts` with per-account credentials and optional `name`. See [Configuration reference](/nb/gateway/configuration-reference#multi-account-all-channels) for the shared pattern.
 
 Verbose bootstrap diagnostics:
 
@@ -370,7 +370,7 @@ Upgrading from the previous public Matrix plugin:
 - If the Matrix access token changes later for the same account, homeserver, and user, Pllan now prefers reusing the most complete existing token-hash storage root instead of starting from an empty Matrix state directory.
 - On the next gateway start, backed-up room keys are restored automatically into the new crypto store.
 - If the old plugin had local-only room keys that were never backed up, Pllan will warn clearly. Those keys cannot be exported automatically from the previous rust crypto store, so some old encrypted history may remain unavailable until recovered manually.
-- See [Matrix migration](/install/migrating-matrix) for the full upgrade flow, limits, recovery commands, and common migration messages.
+- See [Matrix migration](/nb/install/migrating-matrix) for the full upgrade flow, limits, recovery commands, and common migration messages.
 
 Encrypted runtime state is organized under per-account, per-user token-hash roots in
 `~/.pllan/matrix/accounts/<account>/<homeserver>__<user>/<token-hash>/`.
@@ -542,7 +542,7 @@ Current behavior:
 }
 ```
 
-See [Groups](/channels/groups) for mention-gating and allowlist behavior.
+See [Groups](/nb/channels/groups) for mention-gating and allowlist behavior.
 
 Pairing example for Matrix DMs:
 
@@ -553,7 +553,7 @@ pllan pairing approve matrix <CODE>
 
 If an unapproved Matrix user keeps messaging you before approval, Pllan reuses the same pending pairing code and may send a reminder reply again after a short cooldown instead of minting a new code.
 
-See [Pairing](/channels/pairing) for the shared DM pairing flow and storage layout.
+See [Pairing](/nb/channels/pairing) for the shared DM pairing flow and storage layout.
 
 ## Multi-account example
 

package/docs/nb/channels/mattermost.md

@@ -31,7 +31,7 @@ pllan plugins install ./extensions/mattermost
 If you choose Mattermost during setup and a git checkout is detected,
 Pllan will offer the local install path automatically.
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## Quick setup
 

package/docs/nb/channels/msteams.md

@@ -36,7 +36,7 @@ pllan plugins install ./extensions/msteams
 If you choose Teams during setup and a git checkout is detected,
 Pllan will offer the local install path automatically.
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## Quick setup (beginner)
 
@@ -480,7 +480,7 @@ Key settings (see `/gateway/configuration` for shared channel patterns):
 
 ## Routing & Sessions
 
-- Session keys follow the standard agent format (see [/concepts/session](/concepts/session)):
+- Session keys follow the standard agent format (see [/concepts/session](/nb/concepts/session)):
   - Direct messages share the main session (`agent:<agentId>:<mainKey>`).
   - Channel/group messages use conversation id:
     - `agent:<agentId>:msteams:channel:<conversationId>`

package/docs/nb/channels/nextcloud-talk.md

@@ -28,7 +28,7 @@ pllan plugins install ./extensions/nextcloud-talk
 If you choose Nextcloud Talk during setup and a git checkout is detected,
 Pllan will offer the local install path automatically.
 
-Details: [Plugins](/tools/plugin)
+Details: [Plugins](/nb/tools/plugin)
 
 ## Quick setup (beginner)
 
@@ -108,7 +108,7 @@ Minimal config:
 
 ## Configuration reference (Nextcloud Talk)
 
-Full configuration: [Configuration](/gateway/configuration)
+Full configuration: [Configuration](/nb/gateway/configuration)
 
 Provider options: