Onboarding & CLI¶
Traigent provides guided CLI surfaces for getting a Python project from install to a safe first run.
Commands¶
traigent onboard
traigent auth device-login
traigent first-prompt --agent codex
traigent quickstart
traigent onboard detects common Python project markers, supported coding
agents, current authentication state, MCP availability, and then prints or runs
the next setup steps.
In a terminal, onboarding can offer to:
- add
traigent[integrations]to the project - start device login unless
--no-loginis set - install Traigent agent skills —
--profile beginner(default) vianpx skills add Traigent/traigent-first-run, or--profile advancedvianpx skills add Traigent/traigent-skills - register MCP for detected agents when
traigent mcp --helpsucceeds - run the packaged mock quickstart
- print the first prompt for the detected coding agent
In non-interactive mode, onboarding prints a plan and JSON block instead of
starting login by default. Use --login to run device login after the plan.
Device Login¶
traigent auth device-login
traigent auth device-login --write-env
traigent auth device-login --backend-url https://portal.traigent.ai
The command starts an RFC 8628-style browser device-code flow against the
resolved API base, which defaults to the cloud portal at
https://portal.traigent.ai. It prints a verification URL and one-time code,
then polls until the backend returns a project-scoped API key or the request
expires.
By default, credentials are stored in the secure local credential store. With
--write-env, the command also writes project credentials to a local .env
file in the current directory.
First Prompt¶
traigent first-prompt --agent claude
traigent first-prompt --agent cursor
traigent first-prompt --agent codex
The first prompt is a paste block for coding agents. It tells the agent to read the Traigent agent guide, inspect the project, run dry-run/mock mode first, avoid real provider spend without approval, and finish with evidence and changed files.
Quickstart¶
traigent quickstart
quickstart runs the bundled mock-mode demo. It does not require provider API
keys and does not make LLM provider calls. LiteLLM may still try an import-time
model-cost-map fetch and fall back to bundled pricing data when offline; the
guarantee is no provider spend, not zero outbound packets.
Copy-Paste Example¶
python3 -m pip install "traigent[integrations]"
traigent auth device-login --write-env
traigent quickstart
traigent first-prompt --agent codex
Honesty note: traigent onboard is a guided setup helper, not an installer that
silently changes every project. Interactive dependency, skill, MCP, and .env
steps ask for consent; non-interactive mode prints a plan for a caller to run.