Settings

Settings is where Coldtea keeps app preferences, agent setup, team setup, and feature-specific configuration.

Use it when something should change for more than one prompt. Do not hide important one-off context in settings; put that in the task or composer prompt.

Appearance

Appearance controls the Coldtea shell theme and editor theme behavior. The app theme changes Coldtea's own surfaces. Imported editor themes affect the editor surface, not the whole app.

If the editor and shell look different, that is usually intentional.

Agents controls local CLI discovery and launch behavior. Use it to check which agents Coldtea can start, adjust default arguments, reorder quick-launch shortcuts, and edit agent-specific prompt or behavior settings where available.

Agent auth still belongs to the agent. If Claude Code, Codex, Gemini CLI, or another CLI needs first-run login, complete that setup the same way you would in a normal terminal.

Cloud runs

Cloud runs is for remote task-agent configuration where your build and team setup support it. It can include GitHub access checks, model or credential settings, and repository-scoped secrets.

Treat this section as sensitive. Repo secrets and API keys should be added only when the remote run actually needs them.

Features

Features contains smaller behavior switches, including:

A global hotkey for bringing Coldtea to the front.
Whether resumed brews open in a new tab by default.
Terminal activity cursor settings.

If a shortcut does not register, another app may already own it. Pick a different combination instead of fighting the OS.

TeaHouse, integrations, and QA

TeaHouse settings cover the team workspace: membership, task boards, and connected team context.

Integrations is where provider connections such as GitHub are managed. Linear task import appears through the task and TeaHouse setup flows when available.

QA settings are for Matcha and test-user setup where that feature is enabled. Use them only after the team has decided what environment and accounts Matcha should touch.

Scripts and updates

Scripts contains worktree setup, run, and teardown commands for the selected project. Shared scripts live in .coldtea/config.json; local overrides belong in .coldtea/config.local.json.

Updates shows the app update state for builds that include the updater.

Before changing settings

Ask one question: should this affect future work, or just this run?

If it is future behavior, settings is the right place. If it is instruction for the current agent, keep it in the task, plan, or prompt so the reviewer can see it.

Next: configure agents, GitHub, or worktree scripts.