v0.77.0

Added

• Antigravity is its own ACP harness on desktop and on the phone. Enabling it downloads that runtime, and the account is separate from Grok. The phone shows its icon, uses that agent's permission modes, models, and slash commands, and groups usage by model family. Each session keeps the model of the agent it started with. Steer Now cancels the live turn and sends the queued message; Steer Soon injects it at the next safe point. A finished tool row shows that step's MCP result, including output that was spilled to a file, and widget arguments are kept. A file write stays on the approved card and keeps its diff. The usage footer counts newly uploaded input. An empty reasoning block is not shown. A queued message leaves the queue when the turn starts. Switching between Grok and Antigravity on an empty draft clears the previous agent's context.
• The sidebar usage gauge is a multi-account subscription hub showing billing cycles, reset dates, and quota status across connected providers.
• The Grok usage meter shows the login email.
• Streamed markdown and reasoning fade each new commit in over 120ms. Code fences and finished history stay instant, and reduced motion disables the fade.
• One desktop process per userData profile, so a second Windows shortcut does not claim the same remote session. A named instance and a side-by-side alpha still start.
• A markdown table can be transposed so each record reads down one column. Header marks stay on the cells that had them, and the original first column stays body text. Original Layout restores the table.
• Chat and the phone can preview temporary files on a remote node, including files outside a registered project. Reads are scoped and transferred in chunks. A missing file is reported as missing. Both the desktop and the node need this version.

Fixed

• Codex tasks on remote nodes keep running past five minutes, including long tool calls and automatic context compaction, without false timeout or compression failures.
• A Codex question on a remote node can be answered or dismissed. The reply is stored after the node accepts it, and it survives a retry or a restart.
• Deferred reasoning collapses when thinking finishes. Opening it by hand after that still stays open.
• A CLI-only install can load session archive handlers.
• Antigravity and ACP AskUserQuestion interactions render as interactive question cards in the chat transcript.
• A running Grok background bash task remains visible in the status bar and holds the session active until finished.
• The appearance popover matches the usage panel's width and aligns to the sidebar's left edge.
• The worktree popover stays above the chip and springs to the destination height, including the carry-local-changes row.
• A remote Codex voice call is placed by the node that owns the session.
• Session rename, tag, and cleanup run on the owning node. A delete still waits on the confirm card, and a reconnect restores that card.
• A phone learns when its session control is revoked, and the next send asks for control again.
• A collapsed widget stays folded when the transcript unloads it.
• A remote draft stays hidden once the node assigns the session id.
• Adding a project grants Grok folder trust without a dialog. Project rules, MCP, hooks, and skills still load.
• Switching to an ACP harness clears an effort level that harness does not offer.
• A suggested task on a remote node opens its linked checkout under the owning project. An unknown worktree path is not registered as its own sidebar project.
• An unnamed remote session keeps the title taken from its first message. A title set explicitly stays.
• A remote suggested task keeps the model, effort, and settled state it was launched with.
• Review branches and commits are read from the repository on the session's host.
• Git status for a remote worktree is read on the node that owns it.
• A sent remote draft stays deleted after refresh.
• A remote node's capabilities and sync roots stay until it disconnects.
• A remote collaboration wake stays out of the chat. It is not shown as a message the user sent, and a retry does not deliver it twice.