The Launch it with Set exactly one of
tuple CLI stores production preferences in ~/.tuple/cli.toml. Use tuple connect configure to choose a default agent and edit launch settings interactively, or edit the file directly.Tuple creates the containing directory with permissions 0700 and writes the file with 0600. A missing file is valid. On a terminal, tuple connect asks you to choose a default agent before its first launch. Invalid TOML returns an error with the file path. Saving through Tuple preserves the supported keys described here; keep a backup if you store additional keys in the file.Environment paths
The selected Tuple environment determines the file. Keep the executable, app socket, and configuration environment aligned.
Launch settings
default_harness selects an agent when --harness is omitted. Each [harness.<key>] table stores settings for a built-in agent or defines a custom agent.Built-in keys include claude, codex, cursor, copilot, opencode, pi, droid, and prime-agent.--model and --reasoning on tuple connect override saved values for one launch. Support depends on the chosen agent. Tuple warns on stderr when it cannot apply an option.Command-based agents can use saved model, reasoning, and extra_args settings. URL templates ignore these settings, so tuple connect configure skips their launch-setting questions.Harness entries
For a built-in agent, set launch options withoutcommand or url. To define a custom agent, choose one template type. A custom entry using a built-in key overrides that built-in agent.An executable template replaces {PROMPT} with the generated prompt. If the placeholder is absent, Tuple appends the prompt as a final argument.tuple connect --harness review.A URL template opens through the platform’s URL handler. Tuple URL-encodes the prompt before substituting {PROMPT}:command and url for a custom agent.