Connect your AI

An agent connects to your pod with its own identity and key. What it writes goes through the pod's governance: by default its creates and edits apply directly and can be undone, while deletions, schema and structural changes, and admin actions become proposals you approve. You can see and revoke each agent separately.

The user CLI, @synap-core/cli, does the wiring for you.

The short pathCopy Anchor Link

npx @synap-core/cli init

init finds or creates your pod, approves this computer, and connects the agents it detects on it (Claude Code, Codex, Cursor). See the Cloud quickstart.

Connect one agentCopy Anchor Link

synap connect claude-code
synap connect --list                          # everything that can be connected
synap connect cursor --workspace <id>         # focus on one workspace (default: pod-wide)
synap connect codex --project <id>            # focus on one project

connect creates the agent's identity on your pod, gives it a key, and writes the client's configuration. For clients that read skill folders, it also installs the Synap skills.

You choose how the agent's changes land: Normal (recommended: creates and edits apply directly with Undo; deletions and structural changes ask you), Creates only or Ask first. synap init asks on the page where you approve the computer; synap connect claude-code asks in the terminal. You can change it later on the agent's page in the pod admin console. See Validation policy.

Clients you configure in a web UICopy Anchor Link

For ChatGPT, claude.ai and other clients configured in a browser:

synap mcp url --client chatgpt     # a dedicated key plus the URL and ready-to-paste snippets
synap mcp ui-setup cursor          # the exact form fields to fill in for a client
synap mcp connect-claude           # the claude.ai steps: paste a URL, approve in the browser

Your own agentCopy Anchor Link

For an agent you wrote yourself:

synap agents add --name researcher

prints an MCP URL and a key for a new agent identity named researcher. --role admin|editor|viewer sets its workspace role (default editor).

Check the connectionCopy Anchor Link

synap mcp verify    # is /mcp reachable, and is the key valid
synap doctor        # does each configured key work, and why or why not
synap whoami        # who the key acts as, and its scopes
synap agents list   # your agents on this pod

What an agent can and cannot doCopy Anchor Link

• It works through MCP or the Hub REST API, with the scopes and grant of its key. See API keys to limit what it may change.
• Its writes follow its write mode. Under the default, creates and edits apply directly with Undo; deletions and structural changes become proposals. Deletes, admin actions, scope changes, new kinds and roles, and new spaces, cells, playbooks and automations are always proposals, whatever rule you set.
• It can never approve a proposal, its own or anyone else's.
• It cannot create keys for other agents, widen its own approval rules, or give itself vault access.

In this sectionCopy Anchor Link