🗂️ File Browser & Editor

Navigate files faster — A configurable path bar switches between breadcrumb and text modes, completes folders from the keyboard, and makes entire file rows clickable without a loading overlay.
Create and rename in place — One create-new menu replaces separate file and folder buttons, while the shared footer supports inline rename and new-folder creation without removing the existing rename modal for external callers.
Navigation keeps its context — Ancestor folders remain clickable, the starting folder is configurable and defaults to /a0, file pickers no longer blank live canvas listings, and path links reuse the current browser.
Patches preserve filesystem intent — Editor changes retain executable bits and host-user ownership instead of replacing files with root-owned 0600 copies.
Large source files avoid hidden preview work — Skipping unused Markdown previews cuts the reported median open time from about 22.5 seconds to 0.37 seconds, while all three text-editor patch forms are now documented explicitly.
Renamed documents keep saving correctly — LibreOffice uses native Save As after a desktop rename so Writer follows the new target.

🗃️ Projects, Chats & Workers

Chats and tasks organize into project folders — Collapsible groups support a flat view, creation-time sorting, drag-and-drop reordering, and moving an entire chat family between projects.
Projects can stay pinned — Folder pins include a default No project group, with reactive indicators beside affected chat and task titles.
Deep subordinate trees render correctly — Workers beyond the first child level expand recursively with tapered indentation.
Large sidebars drag smoothly — Median hover-handler time in the measured 240-chat sidebar drops from roughly 10 milliseconds to 0.1 milliseconds, alongside clearer All, Working, Idle, and Last active labels.

Telegram gains full slash commands — Built-in, plugin, global, and project commands appear in paginated menus with compaction confirmation, transcript export, and fresh-chat session binding.
WhatsApp shares the same command catalog — Text menus expose context-aware commands, tool permissions, plugin settings, and persistent chat selection.
Messaging settings respect scope — Telegram, Email, and WhatsApp gain project- and agent-profile configuration, token-native status pages, and shared settings accordions.
Telegram bots are easier to manage — Unnamed bots receive stable names, duplicate names are rejected, and connection changes restart bots automatically; plugin authoring guidance now documents the shared slash-command contract.

Native commentary streams as thoughts — Public commentary from native tool calls appears progressively in generation logs and survives eligible Responses history replay.
Chat Completions caches stay stable — Breakpoints no longer move on every tool turn; they mark the last leading context and the last two nonempty assistant messages.
Provider refusals reach the user — Content-filter and refusal finish reasons flow to the visible error handler instead of being retried silently.
Anthropic models receive scoped guidance — Direct, OpenRouter, and Bedrock Anthropic models are asked for public action summaries without changing other providers' prompts.
Subagents keep their intended models and names — Parent overrides copy only when a new subordinate resolves to Default, existing context names are honored, and automatic chat naming no longer overwrites delegation labels.
Chat titles follow changing topics — Main-chat names refresh by default as the conversation evolves.

Settings save about 6.5× faster — Reusing the resolved Git version across 214 active contexts cuts the reported median from 10.1 seconds to 1.6 seconds.
Global model presets are cached — get_effective_config falls from 36.2 milliseconds to 0.5 milliseconds per measured call.
Unused work is skipped — Native tools build only for Responses turns, and the rate limiter avoids roughly 70 milliseconds of token counting when no limits are configured.
Codex and plugin paths reuse more — Pooled HTTP connections save a reported 50–80 milliseconds per Codex request, while caching empty plugin lookups cuts Responses tool building from 112 milliseconds to 58 milliseconds.
Browser prompts remain cache-stable — Browser context moves from the system prompt into loop extras, and tool JSON stays compact in history while remaining readable in the WebUI.
Evaluation fails safely — evaluate_timeout_seconds defaults to 30 seconds with recoverable cancellation, empty scripts return an actionable error, and stale startup or chat-switch state is cleared.
SOCKS proxies work out of the box — Framework requirements include socksio, and the Browser install hook repairs existing environments that lack it.

Composer controls share responsive overflow menus — The reusable menus tolerate browser zoom, while context usage refreshes during tool-only runs after four root-agent calls.
Mobile composition and settings are reliable again — Editors grow naturally, Welcome uses the correct viewport height, touch targets are larger, Save no longer depends on optional stores, and section navigation uses a native picker.
Touch and terminal output stay readable — Mobile text inflation is prevented and touch-generated hover events no longer leave tooltips behind.
Small rendering fixes remove daily friction — Notification actions work inside their modal, preset editing opens the actual selection, process groups stop flashing, and splash and safe-mode pages regain the Bootstrap favicon.
Keys and secrets survive editing — Comma-separated API-key pools remain intact, and masked multiline, Unicode, special-character, and mixed-case secrets retain their values.
Plugin updates respect repository work — Installation preserves tracked thumbnails, local commits rebase with conflict detection and rollback, persistent toasts surface failures, and nested secret substitution works in parallel calls.

Runtime packaging catches up — Codex client 0.155.1 closes upstream SSE streams correctly, Orchestrator runtime data stays out of default backups, Desktop dependencies use Python 3.13-compatible signed Debian packages, and Launcher links point to v1.8.

Remote execution no longer accepts runtime=input; use input_remote instead. No compatibility alias is provided.
LM Studio, llama.cpp, oMLX, and vLLM no longer receive built-in dummy API keys. Save a key explicitly or use LiteLLM's keyless mode.