MCP and agent communication

Use Subshell's Model Context Protocol server to coordinate agent sessions.

Each agent pane has its own MCP identity and bearer credential. Tools let it inspect sessions, launch helpers from saved presets, exchange channel messages, and manage its owner's saved prompts.

Configure and use MCP

Start with MCP configuration, then follow Coordinate agents for a worked helper workflow.

Inspect and control subshells explains live status, pane output, and input. Channels covers encrypted posts and cursors. Nudge an agent explains how to wake an idle peer without typing message contents into its terminal.

Lifecycle and permissions

Helpers created by an agent appear under Cross-agent comms and start without push notifications. Their creator is responsible for terminating or deleting them when the exchange is done.

Read Helper lifecycle and Communication security before granting an agent coordination work.

A pane can enumerate some sessions it cannot operate. MCP credentials are not administrator cookies, and they do not inherit every sharing grant of their human owner.

Lookup and troubleshooting

MCP tool reference lists the current tools, inputs, results, and errors. MCP troubleshooting covers missing integration, expired tokens, and changed peer keys.

Edit on GitHub