Single source of truth for Sidekick, Kay, Codex sidekick, delegation, and verification terms.
| Term | Meaning |
|---|---|
| Sidekick | The Alo Labs plugin that gives Claude Code, Codex, and Cursor a shared delegation layer for supported coding sidekicks. |
| host AI | The Claude Code, Codex, or Cursor session that plans, delegates, reviews, verifies, and communicates with the user. |
| sidekick | A supported child runtime that performs bounded implementation work after activation. Current sidekicks are Kay and Codex. |
| Kay | The Kay runtime installed and repaired through Sidekick. Kay tasks run through kay exec. |
| Codex sidekick | The local OpenAI Codex CLI used as a child runtime through codex exec, pinned to gpt-5.4-mini with extra-high reasoning. |
| delegate | To hand a bounded coding task from the host AI to the active sidekick. |
| active-sidekick | The shared session selector at ~/.sidekick/sessions/<session>/active-sidekick. It contains kay or codex. |
| marker | A project-local file showing that a sidekick is active in the current host session. |
| Host verification | The host-owned review pass that checks requirements, diffs, tests, integration behavior, assumptions, and failure classes before reporting completion. |
| generated host bundle | A rendered skill surface under agents/claude/, agents/codex/, or agents/cursor/, produced from canonical files under skills/. |
| registry | sidekicks/registry.json, the shared metadata for runtime names, marker paths, commands, and install details. |
| release gate | The test sequence that proves public docs, generated surfaces, manifests, hooks, and live sidekick paths are aligned. |
skills/.