Skip to navigation
Install

One-command setup

talotrace setup signs you in and prepares your coding agent in one step.

talotrace setup is the first command to run. It signs you in with tool access, finds the coding agents you use, writes the TaloTrace skills for each and adds one MCP entry that is pinned to your CLI version.

npx -y @talotrace/connect setup

It needs Node 22.14 or newer. npx -y @talotrace/connect <command> runs any talotrace command without installing; npm install --global @talotrace/connect installs the program as talotrace, which the other pages use. Running it again is the way to update: it changes only what is out of date.

What it does

  1. Resolves which TaloTrace environment you follow, and prints it.
  2. Checks this computer and the connection. If the CLI is too old, it stops before it writes anything.
  3. Signs you in. On a terminal it asks whether your agent may start runs and read evidence. With --yes, --json or --no-interactive it never signs in: it reports LOGIN_REQUIRED and the next step, talotrace login --tools, and installs the files anyway.
  4. Detects Claude Code, Codex and Cursor from the environment, the folder and the machine. With none found it prepares Claude Code.
  5. Writes the skills talotrace-web, talotrace-mobile and talotrace-verify, and the MCP entry talotrace-<profile>.
  6. Reads everything back and prints one row per agent and file, then what to restart.

Then restart your agent and ask: “Verify this change with TaloTrace”.

Where each agent gets its files

AgentSkillsMCP entry
Claude Code.claude/skills/talotrace-*/SKILL.md.mcp.json
Codex.agents/skills/talotrace-*/SKILL.md and a short managed section in AGENTS.mdadded with codex mcp add
Cursorthe Claude or Codex skills folder, whichever was written.cursor/mcp.json

If the TaloTrace plugin is already installed in Claude Code, setup reports its version and writes no skill files.

Options

OptionWhat it does
--agent claude|codex|cursorSet up only this agent. Repeat it for more. The default is to detect.
--scope project|userWrite into the project folder (the default) or into your user settings.
--profile dev|stg|latestChoose the TaloTrace environment. See Configuration.
--yesNever ask a question.
--dry-runPrint the plan and write nothing.
--forceReplace a file you edited. The old one is kept as <file>.bak.
--no-loginSkip the sign-in step.
--checkReport the state of every file and change nothing. It exits 1 when anything is out of date or edited.
--removeDelete only what setup wrote. A file you edited is left alone unless you add --force.
--jsonPrint one JSON result.

A file is ok, stale, modified, unmarked, absent or corrupt. Setup refuses to overwrite a modified, unmarked or corrupt file without --force.

Exit codes follow every other command: 0 when all is ok, 1 when something was refused, 2 for a wrong command line. See exit codes.

Without setup

Install by hand: Claude Code or Cursor, Codex and others.