Launches the Cursor CLI agent as a live companion on your Tuple call when Capture starts.

When call-capture-started fires, this trigger opens your preferred terminal and runs tuple connect --harness cursor. Connect resolves the call state, gives Cursor a context prompt, and points it at the live transcript — so Cursor catches up on everything said so far, then watches the call as it happens and acts as a sharp third pair.

What it does

tuple connect brings Cursor into the call and tells it how to follow the version-matched Capture stream. Guided by connect's prompt, Cursor:

• Logs the call live — a one-line · play-by-play on each batch of new transcript, so you can follow along at a glance.
• Chimes in when it matters — a real interjection for a bug it can see, an ambiguous decision or action item, a correction, or a direct question.
• Answers when addressed — say "Cursor, ..." (or type into the terminal) and it responds, then keeps listening.
• Summarizes — a checkpoint when recording stops, and a final summary (decisions, action items, open threads) when the call ends.

Because the trigger just hands off to tuple connect, there's nothing call-format-specific in it: how Cursor reads the call lives in connect's prompt, in the CLI. Nothing is hard-coded about the model either — Cursor uses whatever you have configured.

Choosing your terminal

By default the trigger opens your system's default handler for .command files. To force a specific terminal, set PREFERRED_TERM at the top of call-capture-started (or in the environment):

PREFERRED_TERM="iterm"   # ghostty | iterm | alacritty | terminal

The terminal runs launch-sidekick-cursor.command, whose #!/bin/zsh -li shebang sources your shell profile, so tuple and cursor-agent resolve from the same PATH you get in a normal terminal.

Prerequisites

• macOS
• Cursor CLI installed so cursor-agent works in a new terminal
• The tuple CLI on your interactive shell PATH (with connect and capture support)
  • Install it from the Tuple app: its Capture settings have an Install button that links tuple onto your PATH.
• Tuple Capture enabled for the call

Installation

Drop this directory into your Tuple triggers folder:

~/.tuple/triggers/sidekick-cursor/

The trigger fires the next time call Capture starts.

How it works

call-capture-started supplies the call and recording IDs through environment variables, not positional arguments. This trigger:

1. Creates a working directory per start, ${TMPDIR:-/tmp}/tuple-sidekick-cursor/<timestamp>-<pid>.
2. Shell-quotes both IDs into trigger-context.sh and writes an executable launch-sidekick-cursor.command wrapper.
3. Opens it in your preferred terminal via open (LaunchServices). No AppleScript and no direct binary launch, so it triggers no macOS accessibility prompt and no stray windows.
4. The wrapper starts a login-interactive zsh, sources the trigger context, and runs tuple connect --harness cursor. Connect selects the live current session; the exact trigger IDs remain available to the launched agent and its Tuple commands.

There is no dedup: each Capture start gets its own directory, so stopping and restarting Capture spawns a fresh companion while older ones keep running.

For local testing without opening a terminal, set SIDEKICK_CURSOR_DRY_RUN=1; it writes the launcher and exits.