Cross-provider subagent delegation fails (Codex → GOAT MiniMax)
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 18/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- nodejs
- 領域
- ai, authentication
調査の方向性
The payload names createHarnessSession and runSubAgent, plus provider resolution and auth routing, as the places where the Director's provider is reused for the child. Start by reading those functions to see how a subagent's pinned model is matched to a provider, and reproduce with a custom subagent pinned to a model from another provider. Done means the child returns SUBAGENT_OK across providers, the original provider error surfaces on failure, and regression tests cover both same-provider and cross-provider delegation.
索引モデルが issue の本文から書いたものです。
説明
Summary
Problem
I'm trying to use two different model providers within Command Code:
- Director: GPT-6.1 Sol using my existing ChatGPT/Codex subscription.
- Subagent: MiniMax M3 using my existing Command Code GOAT subscription.
Both models work independently, but the Director cannot delegate tasks to the MiniMax subagent.
I'd like to request an official fix for cross-provider subagent delegation.
Environment
- Command Code CLI: 1.88.2
- Node.js: v24.21.0
- Operating system: Ubuntu VPS
- OpenAI provider:
@byokkit/cmd-provider-openai0.1.5 - Subagent model:
MiniMaxAI/MiniMax-M3
Steps to reproduce
- Connect ChatGPT/Codex and Command Code GOAT.
- Create a custom subagent with MiniMax M3 as its pinned model.
- Select GPT-6.1 Sol from the ChatGPT/Codex section as the main model.
- Ask Sol to delegate the task: "Reply exactly SUBAGENT_OK."
- The subagent immediately fails.
- Switch the main model to MiniMax M3 through Command Code and repeat. Delegation succeeds.
Actual result
The subagent fails before generating output or using tools.
The underlying error is:
HTTP 400 — Provider not available. Use Command Code provider.
Trace ID: 70c44b34dc2c73ba64de17906f21efaf
Command Code only displays: sub-agent stopped early: the run errored.
Investigation findings
Codex inspected the installed Command Code implementation.
It found that the subagent correctly selects MiniMax M3 but appears to reuse the Director's provider authentication and model transport.
This would explain why MiniMax → MiniMax works, while Sol/Codex → MiniMax/GOAT fails.
The custom-agent configuration also has no documented way to override the provider separately for the child.
These findings have not yet been confirmed by the Command Code maintainers.
Requested fix
Could you please investigate and fix this in an official Command Code release?
Ideally, each subagent should:
- Use the provider and authentication associated with its own selected model.
- Support delegation between ChatGPT/Codex and Command Code GOAT subscriptions.
- Return clear error messages when execution fails.
- Continue supporting existing single-provider configurations.
If this feature is intentionally unsupported, please consider adding it.
I would also appreciate confirmation of whether an official workaround already exists or a fix is planned.
Thank you!
Expected Behavior
The GPT-6.1 Sol Director, authenticated through my existing ChatGPT/Codex subscription, should be able to delegate tasks to a MiniMax M3 subagent using my Command Code GOAT subscription.
Each agent should use its own model provider and authentication. The MiniMax subagent should execute the task and return its result to the Director without requiring manual provider switching or an additional subscription.
Actual Behavior
Both models work independently, but cross-provider delegation fails before the subagent executes its first turn.
The underlying error is:
HTTP 400 — Provider not available. Use Command Code provider.
Command Code only displays:
sub-agent stopped early: the run errored
The child produces zero tokens and performs zero tool calls.
Investigation of the installed CLI indicates that the subagent selects the correct MiniMax model but inherits the Director's OpenAI/Codex provider authentication and transport.
MiniMax-to-MiniMax delegation works correctly.
Trace ID: 70c44b34dc2c73ba64de17906f21efaf
Steps to reproduce the issue
- Connect an existing ChatGPT/Codex subscription and a Command Code GOAT account using
/connect. - Create a custom subagent named
sub-agentwithmodel: MiniMaxAI/MiniMax-M3andreasoningEffort: medium. - Select GPT-6.1 Sol from the ChatGPT/Codex section as the main model.
- Ask the Director: "Delegate to sub-agent. Do not use tools. Reply exactly SUBAGENT_OK."
- Observe that the subagent fails immediately with a generic run error.
- Switch the main model to MiniMax M3 through Command Code GOAT.
- Repeat the same delegation. The subagent succeeds and returns SUBAGENT_OK.
Command Code Version
1.88.2
Operating System
Linux
Terminal/IDE
Remote SSH terminal (Ubuntu VPS)
Shell
bash
Session file (optional)
No response
Fix prompt (optional)
Fix cross-provider subagent delegation in Command Code.
The Director uses GPT-6.1 Sol through the OpenAI/Codex subscription, while the subagent uses MiniMax M3 through Command Code GOAT.
The current implementation appears to reuse the Director's provider authentication and model transport when launching a subagent, even when the child has a different pinned model.
Please investigate createHarnessSession, runSubAgent, provider resolution, and authentication routing.
Expected fix:
- Resolve each subagent's provider and authentication independently.
- Preserve the Director's existing provider and subscription.
- Support direct Codex → GOAT delegation without a custom bridge.
- Surface the original provider error when a subagent fails.
- Preserve compatibility with existing single-provider delegation.
Add regression tests for both same-provider and cross-provider delegation.
Please implement this in an official release if technically supported, or clarify the intended limitation.
Additional context
No response
- 主要言語
- 言語のデータがありません
- スター
- 4.2k
- フォーク
- 377
- 平均マージ
- 1日 3時間
- マージ済み PR(30日)
- 6
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
CommandCodeAI/command-code のほかの issue
-
Provider /v1/messages rejects role:"system" inside messages[] — Claude Code ≥ 2.1.154 incompatibleオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
CommandCodeAI/command-code#1085 ·
メンテナーはふだん 1 日以内に返信
-
Feature request: auto-reconnect remote control (/rc) after restart対応中かも @aliarain が 20 日前に担当しました。 オープンp2
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
CommandCodeAI/command-code#992 · コメント 1 件 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
CommandCodeAI/command-code#933 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
CommandCodeAI/command-code#855 ·
メンテナーはふだん 1 日以内に返信
-
grep tool passes empty file type to ripgrep対応中かも @ahmadbilaldev が 19 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
CommandCodeAI/command-code#655 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
CommandCodeAI/command-code の issue をすべて見る
似ている issue
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
developmentwithyash/yaan#60 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
area/billing area/config comp/tui-gateway P2 provider/openrouter type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
NousResearch/hermes-agent#153086 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 2 日以内に返信
-
ai-generated structs tech-debt
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信