Skip to main content
tuple connect launches an AI coding agent with context for Tuple. Use tuple connect prompt to give that context to an agent that’s already running.Connecting or reading a guide supplies instructions. For a one-time question, the agent reads the relevant context, answers, and finishes. Ask explicitly when you want ongoing participation.

​
Prerequisites

The Tuple desktop app must be running and signed in. Follow the CLI setup and authorization steps. The agent you choose must be installed separately and available on your PATH.

​
Choose a call and an agent

An active call supplies live context. An ended call supplies historical context. --call selects either by ID. An unknown call ID returns an error.If you run tuple connect in a terminal without a default agent or --harness, a one-step picker asks which agent to use. Tuple saves only that choice as the default, then continues the original command with its purpose and --call selection. Canceling the picker leaves the configuration unchanged and does not contact the app or launch an agent.Passing --harness skips first-run setup. Outside a terminal, specify --harness or run tuple connect configure in a terminal first.Run tuple connect --help for the installed command’s options. Use the migration guide when updating an existing integration.

​
Give an existing agent context

This command writes instructions to stdout without launching an agent. Load the output into your agent’s context. For a runner that accepts a prompt on stdin:
Agents can read the embedded guide directly:
Choose connection for call connectivity or quality problems, and troubleshooting for tool failures or missing call content. The MCP server exposes the same guidance as resources.

​
Configure launches

Use this explicit configuration flow to choose a default agent and edit advanced launch settings in ~/.tuple/cli.toml. It exits after configuration without launching the agent. Built-in agents include Claude Code, Codex, Cursor, Copilot, opencode, Pi, Droid, and Prime Agent.Command-based agents can save model, reasoning, and additional argument settings when supported. URL-based agents ignore these settings, so the configuration flow skips those questions for them.You can define a custom executable using an argument template:
Then launch it with tuple connect --harness my-agent. See custom harness settings for URL templates and additional arguments.

​
Ask an agent to follow along

For ongoing help, give the agent an explicit task and stopping condition, such as “Follow this call and summarize decisions when it ends.” The agent needs an environment that can continue working between messages.An attached agent owns one reader and its delivery checkpoint. It can use a continuous reader:
Or request one batch at a time:
The first read includes catch-up. If the first batch is empty, use --cursor 0 to wait on the next read. After the records reach the model, repeat with --cursor <record-id> using the highest delivered positive ID. Keep the same call selector and exclusions. A failed delivery keeps the previous checkpoint so the next read can recover the records. See Capture readers for framing, timeouts, and wake phrases.With MCP, use next_capture only when the server advertises it. Its response and checkpoint rules are documented in live Capture delivery.A Tuple-managed agent receives context from the app. Use the app-provided tools and managed-agent guide for that session. The app owns its ongoing delivery; an attached agent remains attached when it reads a guide.