The Cadence CLI checks in, scores the week, runs the weekly review, and plans the next cycle. Use it yourself, or hand it to Claude Code, Codex, or any agent that can run a command — it installs its own skill.
$ curl -fsSL https://cadenceweek.com/install-cli | bash
brew install rizwanreza/tap/cadence
$ cadence status Today is Thursday, Oct 1 2026 (America/Chicago) Cycle: Spring build — week 4 of 12 (2026-09-07 to 2026-11-29) Check-ins: 1 / 4 done ✓ Lift 3x/week ✗ 160g protein 112 / 160 g ✗ Deep work block 1 / 2 sessions ✗ Write 500 words Last week's commitment: Pack protein before any trip. Up next • 1 of 4 goals checked in today. cadence today
Claude Code, Codex, Cursor — any agent that can run a shell command can run Cadence. cadence skill install teaches it the method: log the work, check the score, ask the review questions, and save the answers where you'll see them.
The 12 Week Year runs on three clocks: the day, the week, the cycle. Say it the way you'd say it to a person — the skill knows which command each one needs.
Seconds a day, without opening a tab.
One honest look back, one change forward.
Review the cycle, then plan the next one.
No agent required. The same numbers as the dashboard, one command away — and every command takes --json when you'd rather script it.
$ cadence score Weekly execution: 84% (21 / 25 points) Pace: 84%; tier: Strong Cycle 1, 2026-09-21 to 2026-09-27; snapshot 2026-09-27 Goal Points Done Pace Lift 3x/week 3 / 3 3 / 3 100% 160g protein 4 / 7 4 / 7 57.1% Deep work block 10 / 10 10 / 10 100% Write 500 words 4 / 5 4 / 5 80%
$ cadence history --from 2026-09-21 \ --to 2026-09-27 --goal protein Entries 2026-09-21 to 2026-09-27 Date Goal Value 2026-09-21 160g protein 160 g 2026-09-22 160g protein 165 g 2026-09-23 160g protein 160 g 2026-09-27 160g protein 170 g
Coaching for the week of 2026-09-28
Assessment: 76% through Thursday, after weeks of 88%, 91% and 84%. Lift and deep work are on track; protein is the drag.
Guidance: Log protein at each meal today and put the writing block before lunch.
Risk: Protein missed Thursday through Saturday last week. Plan food before the trip, not at the gate.
Leverage: Writing before lunch has landed 4 of 4 times. Keep it there.
source: llm
You'll need a Cadence account with a cycle to track. The CLI signs in with a personal token, not your password.
Downloads the right build for your machine and checks it against the release checksums.
$ curl -fsSL https://cadenceweek.com/install-cli | bash
Or with Homebrew:
$ brew install rizwanreza/tap/cadence
Open Settings → CLI Access and generate a token. Copy it; you'll paste it once.
Paste the token when asked, then run cadence status to see your week.
$ cadence login
Installs the Cadence skill for your coding agents. Then just ask: “Log today's workout.”
$ cadence skill install
Something off? cadence doctor checks the install, your token, and the connection, and tells you what to fix.
An agent acting on your goals should be easy to trust and easy to stop. The token works only with the Cadence API, lives only where you put it, and you can take it back in one click.
Read the source on GitHub →Your token is saved in a local config file only you can read (permissions 0600). Your password never touches the terminal.
Revoke or regenerate the token from Settings → CLI Access. The old one stops working immediately — for you and for any agent using it.
The API caps how fast any one token can call it, so a looping script or a runaway agent can't hammer your account.
The CLI and the agent skill are MIT-licensed. Read exactly what runs on your machine and what it sends.
Start a cycle in Cadence, then check in from the terminal — or let your agent keep the score.