4 Commits

Include renames

Author	SHA1	Message	Date
yilsem	81ee2ca646	feat(codex-link): main model delegates every task to subagents by default ... User decision (15 Oct 2026): repeating or scheduled work goes to AITURK; all other work, coding included, goes to one subagent (easy) or a subagent team or dynamic workflow (hard). The main model talks, dispatches and verifies.	2026-10-15 02:26:45 +03:00
yilsem	557e619499	feat(codex-link): AITURK work routing setting and beta.40 ... - Default routing rule (user decision, 15 Oct 2026): repeating/scheduled work goes to the AITURK IDE bot as a cron job; coding stays in Codex (itself or its subagents); 'Codex' or 'sen yap' keeps everything in Codex. - Settings > Codex Bağlama: choice (recommended / send large work / never / custom text) with a text box and restore-default; written to bridge.json aiturk_hat. - Bridge re-reads aiturk_hat when bridge.json changes: no restart. IDE apply keeps aiturk_hat instead of wiping it. - Bridge version 20, IDE 1.0.0-beta.40. Jev untouched.	2026-10-15 02:18:18 +03:00
yilsemandClaude Opus 5.5	48103b9ad3	feat(codex-bridge): the AITURK work line is part of Codex Baglama ... The instruction is added for Codex Desktop whenever this computer has an AITURK command that can send work (aiturk is); no separate switch, no bridge.json entry. The bridge fills in the chat id; the command runs in Codex's own folder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-11 03:31:49 +03:00
yilsemandClaude Opus 5.5	1445e204da	feat(codex-bridge): handoff instruction for Codex Desktop only (off by default) ... User decision: the "larger work goes to AITURK" instruction lives only in what Codex IDE sees; the CLI must not know it exists. The bridge adds it in flight by the originator header (measured: Codex Desktop, codex-tui, codex_exec) and only when a send command is configured. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-11 01:05:00 +03:00