Check which AI providers Octopus can use before running a workflow. Get a compact table of availability, authentication, selected models, and billing categories, followed by prioritized fixes for detected problems.
Starter: one-screen provider health summary — availability, auth method, version drift, and cost posture for every seatable provider
Review the instructions the agent will receive before you install.
Produce a one-screen health summary of every provider Octopus can seat, so the user knows what a workflow will actually dispatch to before spending money.
The user asks "what providers do I have?", a workflow banner showed (unavailable - skipping), or a session is starting on a new machine.
${CLAUDE_PLUGIN_ROOT}/scripts/helpers/check-providers.sh and ${CLAUDE_PLUGIN_ROOT}/scripts/helpers/check-versions.sh.CLAUDE_SDK_API_KEY is set (Agent SDK, Opus 5 by default, 1M context). Flag Claude Code older than v2.1.280 for Opus 5.5, older than v2.1.219 for Opus 5, and Codex CLI older than v0.144.0 for GPT-5.6.grok login, opencode auth login, key export).A single table, one row per provider, columns: Provider, Status, Auth, Model, Cost. Below it, at most three ranked fix-it lines. No prose beyond that.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Interpret the saved results of a completed AI council review. Count verdicts, check whether enough participants responded and whether models are independent, surface substantive dissent, and explain what action the outcome supports.
Turn a technical choice into a structured debate between different AI model families. Assign explicit positions, launch the discussion, and summarize agreement, disagreement, and a recommendation supported by the strongest argument that survives the debate.
Clarify a feature’s requirements with multiple AI providers, combining technical constraints with user and business needs. Produce a scoped definition covering priorities, edge cases, exclusions, and a requirements checklist before implementation begins.
Review code or documents with available AI providers before delivery. Combine findings into a scored validation report that checks prior requirements and decisions, separates critical issues from warnings, and recommends next steps.
Develop complex features or business documents by gathering approaches from available AI providers. Combine their perspectives with prior project decisions and quality checks to produce a proposed plan, then proceed with implementation after user confirmation.
Research technical or business questions through multiple available AI providers, each assigned a different perspective. Combine usable results into a report covering findings, disagreements, evidence gaps, priorities, and recommended next steps.