Agent and model providersGrid Console is agent-agnostic. It owns the board, the stages, the card contracts and the code index; a provider plugin runs the sessions. The alpha bundles Claude, built on Claude Code.Two hooks, two jobsHOOKWHAT IT DOESagent.providerRuns a session for a card and supplies the per-stage commands the pipeline calls. Claude Code today; Codex CLI and Gemini CLI later.llm.providerAdds models to the pickers. Grid Console never calls a model itself.
This split is why the pipeline commands in Cards and stages read claude /prepare rather than something built in: they are contributed by the Claude provider plugin. Swap the provider and the arrows keep their meaning while the commands change.Claude, bundledASPECTDETAILWhat it needsClaude Code installed and signed in on your machine.How it signs inThrough Claude Code’s own sign-in. Grid Console never stores or sees it.Commands it contributesclaude /prepare claude /build claude /self-reviewWhat Grid reads backTranscript rows, tool calls, files touched, tokens and cost.
Adding a providerDeclare the hooks in the manifest, implement the session contract (start, stream rows, report files touched, exit with a status the pipeline understands), and map each transition to a command. Report tokens and cost per request or Insights stays empty for your sessions. API keys, where a provider needs them, live with that provider, not with us.RoadmapTodayClaude (Claude Code), bundled.BetaChatGPT/Codex CLI, community provider plugins.After 1.0Gemini CLI, local models through Ollama, private endpoints on Fleet.
ALPHA"Works with Claude Code" is a statement of compatibility, nothing more. Grid Console is not affiliated with any provider, never handles a provider login, and routes no model calls of its own.