Let your agent set it up
One command gives your coding agent the Checkpoint skill. Ask it to add detection, block AI agents, or govern your coding agents, and it does the work, handing you only the steps that need your sign-in or approval.
Give your agent the skill
npx skills add https://kya.vouched.idIt asks which agents to add it to (Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, Windsurf, or any other agent that reads Agent Skills) and whether it's for this repository or every project. Keep the https://: without it, npx skills looks for a git repository.
No Node.js, or an agent without skills support? Paste this at the start of its session instead:
Read https://kya.vouched.id/skills/checkpoint/SKILL.md and follow it.Ask for what you need
If you installed the skill, start a new session so the agent loads it. Then ask:
Set up Checkpoint in this repoYour agent installs the CLI and hands you kya-os setup, which signs you in, links the project, and adds Detect for your stack: the pixel by default, or the server SDK to see every request.
Run what it hands you
Signing in, minting a key, and changing your coding agent's settings happen in your name, so your agent prints those commands for you. Run them in your own terminal, from the app's directory. For setup:
kya-os setup
kya-os detect install --surface sdkkya-os setup signs you in, in your browser or with a code from --device, then shows its plan and asks before changing anything. The second command is optional: it adds server-side detection and mints the app's key. The CLI mints the key itself, so it never passes through your agent: into a gitignored env file for Next.js and Express, and into the project's user secrets, outside the repository, for ASP.NET Core. For Java it mints none: create a key in the dashboard (Credentials) and store it where the CLI says.
If your terminal can't find kya-os, it was open before the install. Run export PATH="$HOME/.kya-os/bin:$PATH" first.
Check that it works
kya-os whoamiIt shows who's signed in and which project this repository is linked to. Then load a page of your app, locally or deployed, and open the project's Activity feed in the dashboard. The visit appears within a minute. For Govern, use any tool in Claude Code: the call appears in the same feed.
Requirements
- A Checkpoint account. Sign up if you don't have one.
- A coding agent that can run shell commands in your repository.
- macOS or Linux, or Windows with WSL. The
kya-osCLI doesn't run natively on Windows yet. - Node.js 22.20 or newer, for
npx skills. The CLI itself doesn't need it.
What changes, and how to undo it
- The skill, in
.claude/skills/checkpoint/or.agents/skills/checkpoint/, withskills-lock.json. Remove it withnpx skills remove checkpoint. - The CLI,
~/.kya-os/bin/kya-os, checked against the registry's hash before it's installed. Uninstall removes it. - Your sign-in, in your OS keychain.
kya-os logoutrevokes it on Checkpoint and deletes it here. - The project link,
.kya-os/project.json. Commit it: it holds no secret. Delete it to unlink. - Detect: one block marked
Checkpoint Detectin existing files, and any new file the plan lists. Remove them to undo. - The app's key, in a gitignored
.env.localor.env, or your stack's secret store. Revoke it in the dashboard, then delete it. - The Claude Code hook, in
.claude/settings.local.json.kya-os govern uninstallremoves it.
Install options
npx skills add https://kya.vouched.id takes these flags:
# Claude Code, every project, no prompts
npx skills add https://kya.vouched.id \
-g -a claude-code -y
# list, update, remove
npx skills list
npx skills update
npx skills remove checkpointA project install writes skills-lock.json, which records where the skill came from so npx skills update can refresh it. Commit it with the skill: it holds no secrets, and your teammates' agents get the skill too. npx skills reports anonymous install counts; run it with DISABLE_TELEMETRY=1 to turn that off.
Without Node.js
Save the one file where your agent looks for skills, or use the prompt from step 1:
mkdir -p .claude/skills/checkpoint
curl -fsSL https://kya.vouched.id/skills/checkpoint/SKILL.md \
-o .claude/skills/checkpoint/SKILL.mdThe skill
One markdown file, served at /skills/checkpoint/SKILL.md. It tells your agent how to check what's set up, which surface fits which stack, what to hand you, and what each error means. npx skills checks the file against the sha256 in /.well-known/agent-skills/index.json before installing it; the prompt reads the live file instead.
Frequently asked questions
Why doesn't my agent sign in or handle keys?
Signing in approves a session in your name, and a key authenticates your app's traffic. Both are yours, so the skill has your agent print those commands instead of running them. On Next.js, Express and ASP.NET Core the CLI mints the key itself, into a gitignored env file or the project's user secrets, so it never passes through your agent's context or your shell history. For Java, create a key in the dashboard (Credentials) and store it where the CLI says.
Do I need Node.js?
Only for npx skills, which needs Node.js 22.20 or newer. The kya-os CLI your agent installs is a single binary, and the prompt needs nothing installed.
Do I need the skill at all?
No. The Quickstart is the same flow by hand. The skill's value is that your agent picks the right surface for your stack, makes the by-hand edits the CLI prints for Express, ASP.NET, and Java, and knows the fix for each error.