Guides for you and your agent
Connect walkthroughs and Kody workflows, verified against the real consoles. Every guide is also plain markdown — append .md to any URL and hand it to your agent.
Connect a provider
- Connect DiscordVerified August 2026Verified walkthrough for connecting Discord to Kody: the OAuth user-token lane for identity and server membership, the bot-token lane required for reading or posting in servers, 7-day rotating tokens, prefilled connect links, and users/@me smoke tests for both lanes.
- Connect GitHubVerified August 2026Verified walkthrough for connecting GitHub to Kody: the built-in OAuth integration, fine-grained personal access tokens, bring-your-own OAuth Apps, scope choices, prefilled connect links, and copy-paste smoke tests.
- Connect Google (Gmail, Calendar, Drive)Verified August 2026Verified walkthrough for connecting Google to Kody: the built-in Google integration for Calendar and allowed scopes, bring-your-own OAuth for inbox reading or Drive-wide access, Google Auth Platform console steps, the Testing-status 7-day refresh-token trap, and a Calendar smoke test.
- Connect NotionVerified August 2026Verified walkthrough for connecting Notion to Kody: the personal internal connection token lane (fastest), the public connection OAuth lane, the page-picker access model (Notion has no OAuth scopes), prefilled connect links, and a users/me smoke test for both lanes.
- Connect SlackVerified August 2026Verified walkthrough for connecting Slack to Kody via the built-in Slack OAuth integration, plus when to bring your own Slack app, reconnect links, and an auth.test smoke test.
- Connect SpotifyVerified August 2026Verified walkthrough for connecting Spotify to Kody: dashboard app creation, the Development Mode Premium requirement and endpoint limits in force since February 2026, the PKCE public-client connect link, listening and playback scopes, and a profile smoke test.
Work with Kody
- What is Kody?Pre-account capability tour for people and agents deciding whether Kody fits: what Kody is, what you cannot get elsewhere, the building blocks, real usage examples, and notes for running a discovery interview. Nothing here requires an account or an MCP connection.
- How Kody worksThe factory loop as a conversation: ask what your favorite bot shipped, save the answer as an export you can invoke from any agent, then a daily email that stays quiet until something actually ships.
- Google OAuth interactive guideInteractive transcript of a coding agent walking a naive user through Lane B Google OAuth for Gmail inbox reading: official guides first, one console step at a time, prefilled /connect/oauth, refuse secrets in chat, then a Gmail profile smoke test.
- Quick example — fork, invoke, ownAgent playbook for onboarding Step 2: wait for a one-click install/fork of a zero-auth example package, invoke the user's installed copy, show the result, explain ownership, and offer optional triggers without recommending one.
- Email and memories — welcome email, reply, memoriesOptional agent playbook: send a welcome email, point the person at their own inbox to reply, look the reply up when they say it is sent, save what matters as memories, then offer a one-click integration. Onboarding Step 2 uses the quick-example fork→invoke flow instead; load this when someone wants the email loop. Includes the no-polling rule and troubleshooting for missing mail and unbound tools.
- Package authoring guideSTART HERE when creating or materially changing a Kody package: package shape, README.md Intent section, secret-using package approval checklist, and scope-update guidance without adding new primitives.
- Durable package lifecycle guideChoose between invoking existing behavior, temporary execute exploration, forking a close trusted community package, direct job schedules, and creating a durable repo-backed package; test package-owned job wrappers safely.
- Integration bootstrap guideSTART HERE when a third-party integration must work before saving a dependent package or package app: inspect integration/secret state, stop for setup, run an authenticated smoke test, then use connect nextSteps or community_search (prefer trusted) before building from scratch.
- Secret-backed integration recipeDefault non-OAuth recipe for secret-backed integrations: research auth, collect secrets through /account/secrets/new, run a smoke test, build the downstream package, then surface package secret approval links (prefer bulk) before calling the work complete.
- Integration-backed package app happy pathAfter integration/secret verification and a cheap smoke test, proceed directly to a package app rooted in package.json and package-owned code; avoid unnecessary repo spelunking.
- OAuth guide (standard path)START HERE for third-party OAuth: hosted /connect/oauth, the exact redirect URI (https://kody.codes/connect/oauth), required query params, PKCE vs confidential, post-connect nextSteps with trusted community helpers suggestions, and how it differs from MCP OAuth.
- Account secret setup guideHosted /account/secrets/new URL shape, query params, approval policy for API keys and PATs, and post-hoc package approval URLs including bulk approve.
- Account package invocation token setup guideHosted /account/package-invocation-tokens/new setup URL shape, owner-scoped /@:username/api/package-invocations invocation route shape, query params, and bearer-token safety policy for external package invocation clients.
- Package service pattern guideBuild a package-native long-lived service using kody.services, package app realtime fanout, service-owned storage, background lifecycle helpers, and scheduled wake-ups.
- Package subscription guideUse package.json#kody.subscriptions for package-owned event handlers; discover subscribers with package_subscriptions_list; smoke-test handlers with package_subscription_dispatch; follow metadata-first email, run.error.recorded activity notifiers, consent-gated admin-only platform.feedback.submitted notification guidance, and admin-only status.incident.opened / status.incident.resolved operator telemetry.
- Kody platform friction guideUse for meaningful Kody friction, bugs, poor experiences, or suggestions: show the exact proposal and account-identity notification disclosure before asking for explicit approval, and write one actionable issue per submission (repro steps, expected vs actual, impact).
- OpenAPI integrations guideOpenAPI discover → summarize → scaffold workflow and durable curated openapi_binding_save bindings callable as kody.openapi["name"].slug(...); auth still comes from a saved integration or secrets.