Cross-provider subagent delegation fails (Codex → GOAT MiniMax)

未關閉
#1,096 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
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-openai 0.1.5
  • Subagent model: MiniMaxAI/MiniMax-M3

Steps to reproduce

  1. Connect ChatGPT/Codex and Command Code GOAT.
  2. Create a custom subagent with MiniMax M3 as its pinned model.
  3. Select GPT-6.1 Sol from the ChatGPT/Codex section as the main model.
  4. Ask Sol to delegate the task: "Reply exactly SUBAGENT_OK."
  5. The subagent immediately fails.
  6. 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
  1. Connect an existing ChatGPT/Codex subscription and a Command Code GOAT account using /connect.
  2. Create a custom subagent named sub-agent with model: MiniMaxAI/MiniMax-M3 and reasoningEffort: medium.
  3. Select GPT-6.1 Sol from the ChatGPT/Codex section as the main model.
  4. Ask the Director: "Delegate to sub-agent. Do not use tools. Reply exactly SUBAGENT_OK."
  5. Observe that the subagent fails immediately with a generic run error.
  6. Switch the main model to MiniMax M3 through Command Code GOAT.
  7. 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 小時
30 天內合併 PR
6

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CommandCodeAI/command-code 的其他 Issue

查看 CommandCodeAI/command-code 的全部 Issue

相似的 Issue

更多 AI Infra & Agents Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。