blomios/IdeA
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(tickets): clôture du cycle cross-project — #260/#265 passent closed après QA verte et AppImage, création+clôture du diagnostic #266 (Codex 5.6 headless/custom CLI vs TUI, sans code prod), index/counter

Browse Source
This commit is contained in:
Blomios
2026-09-07 17:07:56 +02:00
parent 5d7ab903fe
commit 5f73220219
8 changed files with 89 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
.ideai/tickets/266/issue.md Normal file
View File

@ -0,0 +1,17 @@
---
id: "e8885e22-960d-4b89-b5c3-2e35ddf7c632"
number: 266
title: "Diagnostiquer Codex 5.6 en headless/custom CLI vs TUI native"
status: "closed"
priority: "high"
sprint: null
links: []
agentRefs: [{"agentId":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d","role":"assigned"}]
attachments: []
createdBy: {"kind":"agent","agent_id":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d"}
updatedBy: {"kind":"agent","agent_id":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d"}
createdAt: 1788793171188
updatedAt: 1788793585703
version: 3
---
Investigation demandée: le profil AI Codex 5.6 fonctionne en TUI native, mais échoue dans la custom CLI et via idea_ask_agent. Suspect: la version headless/structured Codex ne supporte pas ce profil ou ne passe pas les mêmes paramètres/auth que la TUI. Objectif: identifier la cause racine, comparer spawn TUI vs structured/headless, commandes/config générées, modèle transmis, auth/env, adapter Codex, et proposer le correctif.