Manage Channels

How it works

The /manage-channels skill is the configuration tool for NanoClaw v2’s entity model. After you install channel skills (/add-telegram, /add-slack, etc.), this skill wires them to agent groups and manages how messages from each channel are isolated.

NanoClaw v2 separates channels (where messages come from), agent groups (the workspace, memory, and tools), and users (privilege). Wiring a channel to an agent group is the step that connects them. This skill handles all of that.

What it does

The skill assesses your current state by reading data/v2.db and shows:

• Wired channels — channels with both DB entities and a messaging_group_agents row
• Configured but unwired — channels with credentials and code but no wiring
• Not configured — channels you haven’t installed yet

Then it lets you:

• Wire a new channel to an agent group, asking the isolation question
• Add another group/chat on an already-configured platform (e.g. a second Telegram group)
• Change wiring to move a channel from one agent group to another
• Show configuration as a readable summary

Isolation modes

When wiring a channel, the skill asks how it should be isolated. Three options:

• Same conversation (agent-shared) — all messages from this channel land in one shared session. Recommended for webhook + chat combos (GitHub + Slack on the same agent).
• Same agent, separate conversations (shared) — shared workspace and memory, independent threads. Recommended for the same user across multiple platforms.
• Separate agent (new folder) — full isolation, distinct workspace and memory. Recommended when different people are involved.

The skill picks a recommendation based on the channel’s default-isolation and asks if you want to override.

Tips

• Run /init-first-agent first if you have no agent groups yet. That skill does end-to-end verification by sending you a welcome DM. /manage-channels then handles every channel after that.
• Privilege is user-level in v2, not channel-level. There’s no “main channel” concept — any user can be granted owner or admin (global or per-agent-group).
• Telegram has a built-in pair-code flow. Other channels need you to send the bot a message first so the inbound interceptor creates the messaging group; then this skill can find it.
• Moving a channel to a new agent group is non-destructive. Old sessions stay with the old agent group; new messages route to the new one. The old agent_destinations row stays unless you delete it manually.
• For the deep dive on isolation, see docs/isolation-model.md in the repo.