π CodeBuddy Code v2.179.1 Release β
π¦ Version Info β
| Component | Version |
|---|---|
| CodeBuddy Code CLI | v2.179.1 |
| Agent SDK JS | v0.3.297 |
| Agent SDK Python | v0.3.296 |
β¨ New Features β
Complete channel history, with long messages collapsed β
Channel history is no longer truncated, so models reviewing it get the full text, can tell message kinds apart, and see repeated updates from the same task merged. Long messages in the timeline are collapsed by default and expand to the full text.
Programmatic reads are easier too: history can be filtered by kind and pinned state, and returns full bodies with paging cursors. When a page contains nothing of interest you can keep scanning backwards instead of mistaking it for "no history".
Channel task board supports coordinating roles, dependencies, and review β
The task board can create tasks with coordinating roles and dependencies. The host and coordinators can submit accept or rework decisions with evidence, and downstream tasks advance or reopen based on the result. Coordinating roles, dependencies, and review states are all shown on the board, so models no longer have to guess dependencies from context.
When dispatching tasks you can also declare a shared batch, letting specialists, critics, and arbiters work through the same batch in order instead of each landing on a different task.
Channel messages can be edited, recalled, and pinned, and members can be muted β
Channel messages support editing, recall, and pinning, and the profile panel collects the pinned decisions and conclusions. Members can be muted individually: muted members stay in history but are not woken automatically, and when it is a muted member's turn the system skips them immediately and passes the baton on.
π§ Improvements β
- Failures from channel tools are directly actionable: failures from the task board, channel messages, and orchestration tools now carry machine-readable error codes, so callers can branch on the code, do not have to parse prose, and never mistake an error for a success.
- The task board shows remote merge request status: GitHub / CNB / GitLab merge requests referenced by completed tasks are probed read-only and their status is shown on the task. When the network or permissions are unavailable, the task is marked as pending verification and the local board is untouched.
- Tasks keep moving while the channel is quiet: with no new messages, the system still advances the task clock, handles review timeouts, and drains pending outbound messages, so a long silent channel no longer gets stuck.
- High-volume output no longer slows the session: when the lossless subscription falls behind, it drops only rebuildable content such as text deltas, while complete messages, tool events, and usage are still delivered, so a slow consumer no longer blocks the stream.
- Remote connections handle stale background services automatically: when an old background service with a confirmed identity but stale configuration is found, it is replaced and reconnected within the same connection; manual retry in the Web UI also prepares a fresh connection, so there is no need to click repeatedly.
- The Plan subagent is only available in plan mode: sessions in other modes no longer expose the built-in Plan subagent to the model, avoiding misuse.
π Bug Fixes β
- Model requests continued after quota was exhausted: when the main session or any member runs out of quota, team messages are held and processed after you send your next message; members failing on exhausted quota now carry the same error code as the main session so clients can prompt directly.
- The last output of a stopped member was lost or flagged as a fault: the stop terminal state is now sent only after this round's output finishes writing (up to 3 seconds), and no further output from that round is forwarded afterwards, so late output is no longer treated as a protocol error.
- The session ended early after a steer: when the main session has already answered but is still waiting for members, a steer no longer ends the turn directly; the message is delivered to the main session first, and the turn only ends when delivery fails, a new request preempts it, or the user cancels.
- Members skipped model requests after resuming: fixed members inheriting an already-finished hook context on resume, which made them skip a normal model request.
- Some multimodal models were treated as text-only: corrected the direct image input check for these models and added per-model image input modes, so newly added models no longer require changes to the client allowlist.
- The lead agent did not receive member results: unprocessed member results are now kept after an interruption or session unload and delivered again on resume, and members can keep working in the background after the lead finishes a reply.