Drive and verify the Kody app with a Feature Map and one CLI. Use when changing UI, account routes, preview deploys, or proving a Cloud Agent change with a real origin, session, and /health SHA.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Do not invent a throwaway curl script, scrape PR comments by hand, or rediscover
account routes from routes.ts. Use the CLI and the Feature Map.
node tools/control-kody.ts doctor
node tools/control-kody.ts dev
node tools/control-kody.ts login
node tools/control-kody.ts request GET /account/waiting.json
node tools/control-kody.ts map waiting
node tools/control-kody.ts health --sha <merge-sha>
node tools/control-kody.ts preview -- --request 'GET /account/waiting.json' --check /account/waiting
node tools/control-kody.ts package-create --origin <preview> --package-name <leaf-or-@scope/leaf> [--head-ahead]
--kody-id is an alias for --package-name.
npm run control-kody -- <command> is the same entry.
references/features/README.md is the
human-readable index. tools/control-kody/feature-catalog.ts is the
machine-readable source. map --check (and its node test) fail when a listed
path leaves routes.ts or a required HTML route has no entry.
Load one feature file for the surface you are changing.
jane@example.com / ilikecode (non-admin)me@kentcdodds.com / ilikecode (non-admin, empty until you create
data through JSON APIs, or package-create for a saved package)/admin 403 and /mcp 401 are expected for those seedsCI green is not enough for a user-visible account change. Prefer:
doctor then dev or previewrequest / --check as the seed user with data for this changehealth --origin https://kody.codes --sha <merge> (full SHA,
unique short SHA, or a later descendant HEAD that contains the merge)See docs/contributing/control-kody.md and preview-manual-test.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a user says "add a ty diagnostic", "write this new ty diagnostic", "change a ty error message", "review ty diagnostics", or asks to add, update, or review ty checks, diagnostic messages, subdiagnostics, or concise output behavior.
The English summary is being prepared. Showing the original description.
Use when adding A2UI rendering to any AG-UI-supported framework or custom AG-UI application, scaffolding an AG-UI app that should render A2UI, adapting an AG-UI integration to emit A2UI surfaces, or wiring the AG-UI A2UI middleware/toolkit with a compatible renderer.
The English summary is being prepared. Showing the original description.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
The English summary is being prepared. Showing the original description.
Evaluate an open source project's AGENTS.md and produce a corpus entry for the /agents-md directory. Use when adding a project to the directory, refreshing an existing entry, or running a batch of candidate repositories.
The English summary is being prepared. Showing the original description.
Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.
The English summary is being prepared. Showing the original description.
Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation.
The English summary is being prepared. Showing the original description.