Commands
Every slash command you can send from a bound Telegram or WhatsApp chat — create, bind, pair, stop, and more.
Commands are the control plane for driving sessions from chat. Both platforms accept the same set. Any message that doesn't start with / is passed through to the bound agent as a normal turn.
| Command | What it does |
|---|---|
/help | List commands available in this chat |
/new | Create a new session and bind this chat to it |
/bind | Pick a session to bind from the recent list |
/pair | Redeem a 6-digit code generated from the app |
/status | Show the session bound to this chat |
/stop | Abort the agent's current turn |
/unbind | Disconnect this chat from its session |
/help
/helpReturns the list of available commands, adapted to the current platform (Telegram supports a picker UI for /bind, WhatsApp falls back to a numbered list).
Responds even when the chat has no session bound — useful as a first smoke test after pairing.
/new [name]
/new triage production incidentCreates a new session in the current workspace with the given name (optional — defaults to a generated slug) and binds this chat to it. Subsequent messages drive the new session.
- Session appears in the workspace sidebar in real time.
- Uses the workspace's default permission mode, thinking level, model, and LLM connection.
- Only one session can be bound to a chat at a time —
/newimplicitly replaces any existing binding.
/bind
Without arguments, lists up to 10 recent non-archived sessions:
/bindTelegram shows inline buttons; WhatsApp shows a numbered list like:
1. production incident (2h ago)
2. refactor sessions module (yesterday)
…Reply with the number to bind:
/bind 1Or bind directly by session ID:
/bind abcd1234-5678-...Useful when you want to pick up an existing thread instead of starting fresh.
/pair <code>
/pair 451829Redeems a 6-digit code generated from the app:
- In the Fabric Agents app, open the session you want to share → session menu (⋯) → Pair over Telegram or Pair over WhatsApp.
- A 6-digit code is displayed, valid for ~5 minutes.
- The person you want to share with messages the bot / your WhatsApp with
/pair <that-code>. - Their chat is now bound to the session.
Rate limits: each sender gets a small number of /pair attempts per minute. Each code is single-use.
Use /pair when you want a specific contact driving a specific session — e.g. giving a collaborator push-control over a deployment session.
/status
/statusShows the session this chat is bound to, or reports "no session bound" if none.
First diagnostic when something feels wrong — confirms whether the message router sees a live binding before you go digging in logs.
/stop
/stopAborts the agent's current run on the bound session. Equivalent to hitting the stop button in the desktop UI.
Does nothing if the agent isn't currently processing — responds with "Nothing to stop".
/unbind
/unbindDrops the session binding for this chat. The session itself is untouched (it stays in the workspace) — only the link to this chat goes away. After /unbind, sending a plain message prompts you to /new, /bind, or /pair to bind again.
Useful when the chat should stop driving the session but you don't want to lose the session itself.
Command matching rules
- Case-insensitive (
/Newworks the same as/new). - Leading whitespace is tolerated; trailing text after the command name is treated as the argument (for
/newand/pair). - Any message that doesn't begin with
/is a normal user turn on the bound session. - If the chat has no session bound and you send a non-command message, the bot responds with a hint to use
/new,/bind, or/pair.
Related
- Messaging overview — response modes, bindings, architecture
- Telegram setup
- WhatsApp setup
Connect WhatsApp to Fabric Agents — scan a QR code with your phone, then drive sessions by messaging yourself or routing a contact via /pair.
Weave
Lean Fabric plugin with multi-agent orchestration. Eight specialised agents — Loom, Tapestry, Pattern, Thread, Spindle, Weft, Warp, Shuttle — with a Plan → Review → Execute workflow.