ReferenceCommandsGet started
turno init
Set turno up in one step: find agents, profiles, folders and MCP servers, show the diff, write it (one undo)
Usage: turno init [--dry-run] [--yes] [--profile <name[:agent]>]... [--skip <name>]...
[--default <profile>] [--no-mcp] [--start | --no-start]
Sets turno up in one step. It looks for installed agents, turno profiles, agent folders made by
hand (~/.claude-<name>, ~/.codex-<name>, ...), MCP servers in every agent config, and the
folders each Claude Code account was used in. Then it proposes profiles, folder rules, a default
and mcp.toml, prints the whole change, and writes it as one journal: turno undo <stamp> reverts
all of it. It never moves your own files without showing it first.
In a terminal it asks before adopting each folder, which profiles to create when there are none,
and the default; without one, --yes is required and flags give the answers.
--dry-run print the plan and the diff, write nothing
-y, --yes write without asking (adopts every folder found but those in --skip)
--profile <p[:a]> create this profile (agent claude, codex, copilot or cursor)
--skip <name> leave a found folder alone
--default <p> profile for folders without a rule
--no-mcp do not create mcp.toml
--start also start the gateway and point every profile at it (with --yes)
--no-start leave the gateway and the agent configs alone
When there are MCP servers, init in a terminal also offers to start the gateway as a login
service and point every profile at it (turno mcp daemon start, turno mcp sync), in the same
journal. With --yes it does that only with --start.
Examples:
$ turno init
$ turno init --dry-run
$ turno init --yes --profile work --profile school:codex
$ turno init --yes --no-mcp