mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Decouple orchestrator startup from CLAUDE_API_KEY #424

New Issue
Closed
opened 2026-02-17 23:00:13 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-17 23:00:13 +00:00
Owner
Copy Link

Problem

Orchestrator startup currently hard-fails when CLAUDE_API_KEY is not configured, even when running Codex/OpenCode-first deployments. This causes avoidable readiness failures and blocks local smoke verification.

Goal

Make provider/runtime key requirements explicit and configurable so orchestrator does not assume Claude-only operation.

Scope

  • Remove hard startup dependency on CLAUDE_API_KEY unless selected provider requires it
  • Add config validation by active provider/runtime
  • Provide clear startup diagnostics for missing key per selected provider
  • Update docs/env examples for multi-agent runtimes (Codex/Claude/OpenCode)

Acceptance Criteria

  • Orchestrator can start without CLAUDE_API_KEY when Claude provider is not selected
  • Readiness remains healthy for Codex/OpenCode configurations
  • Misconfigured provider reports actionable error message
  • CI includes a coverage path for non-Claude startup

Context

Raised during post-merge smoke validation on 2026-02-17.

## Problem Orchestrator startup currently hard-fails when `CLAUDE_API_KEY` is not configured, even when running Codex/OpenCode-first deployments. This causes avoidable readiness failures and blocks local smoke verification. ## Goal Make provider/runtime key requirements explicit and configurable so orchestrator does not assume Claude-only operation. ## Scope - Remove hard startup dependency on `CLAUDE_API_KEY` unless selected provider requires it - Add config validation by active provider/runtime - Provide clear startup diagnostics for missing key per selected provider - Update docs/env examples for multi-agent runtimes (Codex/Claude/OpenCode) ## Acceptance Criteria - Orchestrator can start without `CLAUDE_API_KEY` when Claude provider is not selected - Readiness remains healthy for Codex/OpenCode configurations - Misconfigured provider reports actionable error message - CI includes a coverage path for non-Claude startup ## Context Raised during post-merge smoke validation on 2026-02-17.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#424
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?