Quick start

After setup, with reckon on your PATH:

1. Create an orgCopy Anchor Link

reckon org add acme --envs prod,uat,dev

This creates ~/.reckon/orgs/acme/ with its own secrets, config and workspace folders. Your first org also becomes the default context.

2. Connect toolsCopy Anchor Link

Connect at least one tool. Jenkins runs a server per environment; CubeAPM holds every environment in one server with a label each:

reckon connect jenkins-prod --org acme --provider jenkins --for-env prod
reckon connect cubeapm --org acme --provider cubeapm --label prod=PROD --label uat=UAT

Each command prints the credentials file it created. Fill it in with your editor, or run the CLI's own login for that connection:

$EDITOR ~/.reckon/orgs/acme/secrets/jenkins-prod.env
reckon login cubeapm

Orgs & connections explains the file format and the three connection shapes. Each integration page lists its settings.

3. Check themCopy Anchor Link

reckon use acme/prod
reckon status            # local readiness, no network
reckon verify            # one live read per connection

4. Open the agentCopy Anchor Link

reckon open              # the default context, acme/prod
reckon open acme/uat     # or name it
reckon open acme/prod --runtime codex
reckon open acme/prod -- --continue    # arguments after -- go to the agent

reckon open starts Claude Code (or Codex when Claude Code is not installed) in ~/.reckon/orgs/acme/workspace, pinned to that environment and without any tool credentials. A production environment gets a warning banner. The agent's first step is reckon preflight, and its first message states the context: "Working on acme, environment prod." See Agents for what the agent can and cannot do.

5. Ask for workCopy Anchor Link

Describe the work in plain language. Give a time window when it matters:

Checkout latency spiked from 14:30 to 14:50 UTC today. Find the cause.

Which deploy-api builds failed this week, and why?

Weekly search review for sc-domain:acme.com: what moved, and which queries are close to page one?

The agent reaches each tool with reckon run <tool> -- <arguments> and saves work that matters in a session, so the evidence survives the conversation.

6. Review saved workCopy Anchor Link

reckon history                   # this org's sessions in this environment
reckon resume <session-id>       # evidence, notes and gaps
reckon report <session-id>       # writes the briefing and prints its path

Sessions live in ~/.reckon/orgs/acme/workspace/sessions/. An investigation can be promoted to an RCA under incidents/. See Saved work.