Skip to content

πŸš€ CodeBuddy Code v2.179.3 Release ​

πŸ“¦ Version Info ​

ComponentVersion
CodeBuddy Code CLIv2.179.3
Agent SDK JSv0.3.299
Agent SDK Pythonv0.3.298

✨ New Features ​

Title bar menu and tray icon on Windows and Linux desktop ​

A new menu button on the left side of the title bar opens the settings that were previously available only from the macOS menu bar, such as switching between the built-in and external CLI, or stopping the background service on exit.

A tray icon is also available for showing the window, quitting, or stopping the background service and quitting.

Behavior change: closing the window now minimizes it to the tray instead of quitting. To restore quit-on-close, clear "Minimize to tray when closing the window" in the tray menu or in the title bar menu under "Service". macOS behavior is unchanged.

πŸ”§ Improvements ​

  • Pre-read sensitive detection in Enterprise Security Center: Enterprise administrators can enable "Scan files before reading" in sensitive protection. When enabled, files read by the agent (including originals loaded before editing an existing file) are scanned before the content enters the tool, and matches are handled with the options defined by enterprise policy. Accounts without the policy, and personal editions, keep the previous behavior
  • Sandbox follows enterprise-wide policies: Sandboxes now honor enterprise-wide program blocklists, strict network mode, malicious site blocking, and HTTP request interception, as well as the enterprise-defined auto-backup switch, total backup limit, and per-file size limit. Items not delivered by the enterprise continue to use local settings
  • Faster startup: Project rules and custom commands are now discovered and loaded concurrently, unrelated settings merges and repeated tool argument conversion are skipped during startup, and the first-screen model display no longer waits for every agent to register
  • WebSearch results skip sensitive information detection by default: Reduces false positives on ordinary search results, while existing ciphertext protection, egress checks, and tool execution approvals stay in place

πŸ› Bug Fixes ​

  • MCP still showed "needs auth" after authorization: Fixed MCP servers still showing needs-auth or connection failure after completing OAuth and connecting successfully. A successful connection now clears the auth flag and error message left by a previous 401, the Web UI no longer lets a stale auth state cover a connected server, and "not connected", "pending approval", and "connection failed" are distinguished
  • Short error codes from custom model services displayed incorrectly: When a service returns short numeric codes such as 429, 500, or 503 as text, the message now shows the code returned by the service instead of the request status code, making it easier to cross-check service logs. Letter-based codes keep the previous behavior
  • Some product error codes were treated as HTTP status codes: Product codes such as 402, 404, and 502 carried in an HTTP 400 response are now passed through as-is, while 429 and 5xx that match the HTTP status are still treated as status codes
  • Hovering over an exited session started a background process: Hovering an exited agent or session in the Web UI list no longer starts a background process. Hover now prefetches history only, avoiding hundreds of MB of memory being consumed while browsing the list, and opening the session still restores it automatically and shows the prefetched history right away
  • --serve processes were hard to identify from outside: The process title now keeps the original command line with the display name in front, so health checks, pid lookups, and sampling that identify codebuddy --serve processes no longer silently mismatch after an upgrade
  • Downstream tasks on the channel task board got stuck: After an upstream step is abandoned, the lead or a user can now rewrite the dependencies of downstream tasks (point them at a replacement step, or remove the dependency), while task numbers and history stay unchanged. Dependency errors now also suggest a concrete next step
  • Sessions kept writing to the old directory after switching data directories: Fixed sessions continuing to write to the old location after a prewarmed activation switched data directories, and the first save failing after a session directory was cleaned up. Missing directories are recreated and the save is retried once, without extra probing on normal saves