Todas as versões
v0.0.8527 de agosto de 2026PATCH

Codi runs the team — and nothing merges without you

Every finished task now goes through Codi's review before it counts as done, every outcome lands visibly in your chat, and no agent can merge into your working branch — approving the merge is your click, always. Also in 0.0.85: shared workspaces with members and presence, session-based activity, one Codi turn per batch of answers, and a spent model no longer takes its whole engine offline.

NOVO6
  • The review lane: a worker finishing a task hands it to Codi for review — with the worker's findings in front of it — and Codi approves, requests changes, or escalates to you. 'Done' is the review's verdict, never the worker's own claim.
  • Merge consent: agents approve the WORK, you approve the MERGE. When reviewed work carries a branch, you get one message in chat and one Inbox card — nothing touches your branch until you approve the task from the Board or task header.
  • Shared workspaces with members and presence: see who's in the workspace and who's online.
  • Activity is session-based: every ask is a session with a truthful status, and each expands into its full trail — runs, tool calls, tasks, costs, errors.
  • Answer a batch of Codi's questions and you get ONE follow-up turn, not one per answer — Codi waits for you to stop clicking before it starts.
  • Inbox cards carry Codi's summary and its specific question, with the raw findings one click away on the task's Findings tab — you decide from a briefing, not a wall of comments.
MELHORADO6
  • A model hitting its weekly limit no longer takes the whole engine offline — 'Fable is spent' now leaves Opus and Sonnet working instead of showing 'rate limited, try again in 32 hours'.
  • Work you trigger shows on YOUR ask: answering orientation questions no longer leaves the thread reading 'done' while Codi is still working.
  • Codi owns task budgets: a task running out escalates to Codi, which raises the budget itself within bounds — you only hear about it when it actually needs you.
  • Blocked handoffs are loud in every direction: the engineer is told at handoff time (with the exact command to fix it), your channel names the branch where the work is safe, and Codi is woken to deal with it.
  • Orientation got faster and Codi speaks in the thread while it works.
  • Deliveries land on the branch the work was branched from — no more finished work quietly merging to main while you work on dev.
CORRIGIDO5
  • Codi finished one task and never moved to the next: a completion event arriving while Codi's previous run was winding down could be silently swallowed. Event wakes now queue behind a live run instead of vanishing, so dependent tasks always start.
  • Tasks could jump straight to done without review, stranding their dependent tasks in backlog. A completed worker run now always hands off to review.
  • A repeated handoff of the same task was a silent no-op that read as success — the commit sat on its branch forever. Every handoff now answers with what actually happened.
  • Sub-agent questions appeared only in the Inbox; they are now announced in the chat as well, exactly once.
  • Stale engine verdicts ('Claude is rate limited') could persist after the limit cleared; availability is now evidence-based, self-healing, and the banner names the evidence and its age.
NOTAS DE VERSÃO

Why this release

0.0.85 is about trust in delegation. You hand Codi a feature; Codi splits it into tasks, supervises the engineers, reviews what they build, and comes back to you only when a decision is genuinely yours. For that to work, two things must be true: nothing finishes silently, and nothing irreversible happens without you. This release makes both structural.

Done means reviewed

A worker can no longer declare its own task done. Finishing hands the task to Codi for review, with the worker's findings rendered straight into Codi's context. Codi approves, sends it back with concrete feedback (and the engineer is re-woken to act on it), or — when it genuinely can't decide — escalates to your Inbox with a summary and a specific question, findings one click behind the task link. Every one of those outcomes is posted visibly in the channel. Comments are a durable record now, never a delivery channel.

Your branch is yours

The sharpest lesson this month: reviewed-and-approved work merged straight into the branch a founder was actively working on. Correct code, wrong authority. Now agents approve the work and the merge waits for you — one message in chat, one Inbox card, and your approve on the Board or task header is the only thing that lands a branch. Validity still fails fast: broken tests and empty handoffs are refused at handoff time, to the engineer, before anything reaches you.

Nothing finishes silently

The bug class we hunted all month is 'the app knows and the surface doesn't say it'. A completion event arriving during the last seconds of another run used to be swallowed — that was 'Codi finished one task and never moved on'. A repeat handoff used to be a silent no-op that read as success. A sub-agent's question used to appear only in the Inbox. All fixed, all pinned by tests against the real failure traces.

Working together

Workspaces now have members and presence — see who's in and who's online, in a chat that behaves like the tool you already know: threads, sessions, and an activity view where every ask is a session you can open into its full trail (runs, tool calls, tasks, costs) — or delete.

Get the update

The app auto-updates on next launch. To force a check, Settings → Updates → Check for updates, or download from the releases page.

Acompanhe

Boa parte disto entregou-se a si própria.

A AskCodi mantém a AskCodi, por isso estas notas descrevem trabalho que também tivemos de rever.