Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: T3_CODE_ORCHESTRATION_INSTRUCTIONS has no carve-out for user- or repo-mandated CLI review workflows (unlike T3_CODE_BROWSER_TOOL_INSTRUCTIONS)

Aperta Adatta ai principianti
  • Qualcosa non va?
#19,908 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
ai-infra-agents, typescript
Ambito
ai, backend

Direzione di ricerca

La modifica riguarda T3_CODE_ORCHESTRATION_INSTRUCTIONS in packages/provider-core/src/server/orchestrationInstructions.ts, intorno alle righe 9–11, dove si trovano le righe incondizionate di delegate_task. Leggi l'eccezione per il browser alle righe 49–54 dello stesso file e rispecchia la sua formulazione. È completato quando il testo di orchestrazione prevede un'eccezione per il caso in cui l'utente o un workflow del repository documentato indichi un runner CLI o uno script specifico per una revisione o un controllo.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

packages/provider-core, apps/server

Steps to reproduce
  1. In a repository whose AGENTS.md (or user prompt) mandates a repository-owned CLI review runner (for example, a read-only shell command that prepares an isolated review packet and runs a cross-provider reviewer CLI with --strict-mcp-config and structured verdict parsing), start a Codex turn in T3 Code with the t3-code MCP server attached.
  2. Ask the agent to run the repository's required code review workflow.
  3. Observe how strict instruction-hierarchy models (such as Codex) resolve the conflict between the repository workflow / user prompt and t3_code_orchestration (T3_CODE_ORCHESTRATION_INSTRUCTIONS) injected in turn/start.additionalContext.
Expected behavior

When the user or a documented repository workflow/skill explicitly names a dedicated CLI runner or script for a review or check, the agent should follow that workflow rather than refusing it on the ground that T3_CODE_ORCHESTRATION_INSTRUCTIONS requires delegate_task.

T3_CODE_BROWSER_TOOL_INSTRUCTIONS in the same file (packages/provider-core/src/server/orchestrationInstructions.ts L49–54) already includes this exact carve-out for browser tools:

Use another browser system when:
- the T3 preview tools are absent, or `preview_open` returns an explicit unsupported/unavailable error;
- the user asks for another browser, or invokes a skill or documented repository workflow that names one; follow that workflow and report any prerequisite it is missing;
Actual behavior

T3_CODE_ORCHESTRATION_INSTRUCTIONS (packages/provider-core/src/server/orchestrationInstructions.ts L9–11) currently states unconditionally:

  • Also use delegate_task for cross-provider or explicitly T3-owned child tasks.
  • For every T3 delegated review round, call delegate_task again.

For Codex turns (apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.ts L766–775 → buildCodexAdditionalContext in apps/server/src/provider/CodexDeveloperInstructions.ts L146–164), t3_code_orchestration is injected as { kind: "application", value: T3_CODE_ORCHESTRATION_INSTRUCTIONS }, which Codex renders as a developer-level <t3_code_orchestration> message. Because developer instructions outrank AGENTS.md and user messages in Codex's instruction hierarchy, Codex sessions refuse to run a repository's shell-based review runner even when both AGENTS.md and the user explicitly tell them to use the repository runner instead of delegate_task.

Suggested fix: in T3_CODE_ORCHESTRATION_INSTRUCTIONS (packages/provider-core/src/server/orchestrationInstructions.ts), add a short exception parallel to T3_CODE_BROWSER_TOOL_INSTRUCTIONS—for example, noting that when the user or a documented repository workflow/skill explicitly names a specific CLI runner or script for a review or check, the agent should follow that workflow instead of delegate_task.

Impact

Blocks core workflow

Version or commit

0.0.46-nightly.20261014.3132; still present on main @ 42da166d13

Environment

macOS, Apple Silicon. T3 Code Desktop Nightly 0.0.46-nightly.20261014.3132. Provider: Codex (gpt-5.4 / gpt-6.1-sol).

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
6h 23m
PR unite (30g)
203

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.