Help Center

How Can We Help You?

Everything you need to find the right Sidekick docs for your task — from first install to per-session delegation, debugging, release prep, and runtime differences across Claude and Codex.

Sidekick ships Kay and Codex. Claude Code and Codex hosts can activate either sidekick for the current session. Use /sidekick:kay-delegate for Kay, /sidekick:codex-delegate for Codex, and the matching stop command before switching. If you're not sure which path to read first, start with Compatibility.
Start Here Audience Glossary Compatibility Install Delegate Debug Decisions Reference Concepts
Documentation

Choose a task or topic

Start with the page that matches what you want to do. Pick the page that matches your role or your task, then drill into the detailed topic pages if you need more context.

Task map

Start Here

The question-first entry point. Use this if you do not yet know which Sidekick doc to read first.

  • Find the right doc by role or task
  • Jump to install, delegate, debug, release, extend, or migrate
  • Use the glossary and compatibility matrix when terms drift
  • Follow the reader model instead of the folder tree
Open start page →
Start here

Getting Started

New to Sidekick? Install the plugin, choose Kay or Codex for your sidekick path, run the current-session readiness check, and delegate your first coding task.

  • Installing Sidekick via /plugin install
  • Runtime prerequisites and readiness checks
  • Your first delegation task
  • Reading the task-first docs map
  • Understanding AGENTS.md bootstrap
Read guide →
Fundamentals

Core Concepts

Understand how Sidekick works across Claude Code and Codex — host-owned verification, sidekick activation, enforced hooks, progress surfaces, and the shared active-sidekick selector.

  • Kay and Codex sidekick modes
  • active-sidekick mutual exclusion
  • Host verification and recovery
  • Runtime readiness checks
  • Progress summaries and audit indexes
Read concepts →
Workflow

Delegation Workflow

The end-to-end flow for delegating a task through Kay or Codex — from activation and runtime routing to host verification and retry.

  • Activating one sidekick per session
  • Routing Kay exec and Codex exec
  • Monitoring bounded progress summaries
  • Running host verification
  • Relaunching the active sidekick for fixes
View workflow →
Reference

Command Reference

Every activation command, stop command, hook, runtime command, test command, and canonical term — all in one place.

  • Activation and stop commands
  • Kay and Codex runtime flags
  • Session marker paths
  • Strict and release tests
  • Failure taxonomy
Open reference →
Help

Troubleshooting

Common issues with current-session readiness, provider configuration, hook enforcement, verification failures, and session recovery.

  • Readiness failures and fixes
  • Provider and model config
  • Verification failure recovery
  • Wrong sidekick active
  • Reinstall and reset paths
Troubleshoot issues →

New to delegating? Start with Getting Started, then Core Concepts to understand active-sidekick, runtime routing, and host verification before your first task.