control-kody

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.

Install
npx skills add 'https://github.com/kentcdodds/kody/tree/main/.agents/skills/control-kody'
Download bundle ↓
main · 8beb6cdScanned 2026-09-15

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗
View on GitHub
← Back to SKILL.md

Email inbox

Per-user stored mail (notify-self, reply) and email destinations.

How to get there

/account/email/account/email/:messageId. Destinations sit on the inbox list at /account/email#email-destinations.

Drive it

node tools/control-kody.ts request GET /account/email.json
node tools/control-kody.ts request GET /account/email-destinations.json
node tools/control-kody.ts request POST /account/email.json --json '{"action":"delete","message_id":"<id>"}'

APIs

  • GET /account/email.json
  • POST /account/email.json { "action": "classify", "message_id", "classification" }
  • POST /account/email.json { "action": "delete", "message_id" }
  • GET|POST /account/email-destinations.json (add / resend / setDefault / remove), then confirm extras at /verify-email-destination

Delete confirms in the UI with a second click, then returns the inbox list and updated usage.stored_messages count.

Gotchas

  • Preview seed starts empty. Inbound mail is not something a Cloud Agent can mint without the email store APIs.
  • The account email is always listable and cannot be removed here; extras must verify before emailSend can use them. Cap is 5 extras. Mail comes from {username}@platform.