What just shipped.

A relative link in a transcript was resolved against the project catalog alone, so a conversation running in a subdirectory — an Ask anything workspace in particular — produced a link that pointed at nothing. Resolution now takes the session's working directory as context and falls back to the catalog only when that directory is unknown, and the same context reaches markdown image targets so a preview opens the file the agent actually referenced.

Three reading defects in the transcript, fixed together because they share the same surfaces. A very long user message pushed the conversation off screen, so it now collapses behind a disclosure toggle measured from the real rendered height instead of a guessed pixel budget, which keeps dynamic type honest.

Ask anything creates one working directory per conversation, and Codex asks whether every previously unseen cwd is trusted. The mode therefore paid that dialog forever. A launch in an Ask anything directory now passes a single -c projects.<path>.trustlevel="trusted" override for that one invocation, so nothing is written to the person's config.toml and no other project gains trust.

The inline plan panel is capped to a fraction of the transcript, which is enough to notice a checkpoint and too little to actually read a long plan before approving it. The header now carries an expand control that lifts the same panel into a fullscreen overlay on desktop web, responsive web and native mobile, with the collapse control reserved for the inline state.

A search result carried the running flag captured when it was indexed. A session stopped since then was filtered out of History as if it were still open and disappeared from both lists, and one resumed since then could be listed twice. The current /api/sessions snapshot is the authority now: a result is kept out of History only when its session id is live in that snapshot, so a stale flag costs a card its section, never its existence.

Sharing was the only thing a project file could do on the phone: opening it in the system viewer or keeping a copy required going through another app. A small Expo module now backs three distinct actions — open in the platform viewer, save a copy through the system picker, and share — on both Android and iOS, and the file screen and Files tab expose them separately instead of folding everything into one share sheet.

The desktop-only CLI documentation view, its entry points and styles are gone; /docs/cli and /docs/windows-cli now return to the workspace on every surface. The browser check proves the removal instead of the removed copy.

A serialized command tail keeps a late progress update from recreating the Android foreground notification after the stop, and the sync pass releases the service as soon as the download queue is empty rather than after unrelated snapshot work.

A reader message announced itself in the Notification Center without a destination: the owner could only mark the row read. The server now carries a /share-messages/<share-id> app path, and every surface resolves it to that share's message list — desktop web through the workbench bus into the Shared links panel, responsive web through a real route, native mobile through its existing message page.

Filtering History client-side ran after the global 200-entry window, so an older conversation of a filtered project could never surface. /api/history now accepts repeated project parameters and filters before the limit; web and native mount a scoped query when a project filter is active and keep the unscoped window for project discovery and tab recovery.

The Windows .ico was the last icon still built from the bare relief mark on transparency, so the taskbar, the shortcut, the installer window title bar and the NSIS header all showed the mark floating on the host background while the Android launcher, the browser favicon, macOS and Linux showed the midnight-blue app tile. Render every .ico frame from that tile instead, and rename the mark source after what it still composes: the adaptive Android background and the splash lockups.

Every installation asked the stable channel for its update status unless updateChannel was set in its config, and nothing ever writes that key. No stable release is published, so stable/manifest.json answers 404 and the Updates panel showed "The server update check failed. Try again." on a build that was perfectly able to compare itself to the beta channel it came from.

The changelog documented 52 releases and offered a single button, and it led to /download, which always serves the channel's newest build. Every artifact of every past release is still online under its immutable release directory, so the only thing missing was a way in.

Approving a Plan checkpoint typed one fixed sentence into the session. The plan itself stayed inside the agent's context, where it died with the next compaction, restart or engine switch, and the button was worth exactly as much as typing "go" in the composer. A waiting checkpoint was worse than invisible: the agent stops after submitting, so its turn closes normally and the session was reported idle — finished, nothing waiting.

The route test and the browser check both simulate the plan sink, so the one seam that had never run was the real one: FocusPlanService.create with the schema, the idempotency scope and the exact task shape the route builds. This registers the real route on the real services and reads the plan back — order, notes, statuses, counts — then replays the approval to prove a decided checkpoint neither duplicates its plan nor delivers twice.

A second launch now quits to the primary window, and a shell restarted after a crash adopts the embedded server left alive: it verifies the public identity, the private runtime record, the owning PID and the same projects root before rotating its capability through a 0600 handoff file. The preload no longer requires a local module, so it works under a sandboxed renderer.

The frps vhost overwrites X-Forwarded-Proto with the scheme of its own loopback listener, so an instance read every tunnelled request as plain HTTP: pairing from an HTTPS QR code was refused outright, and auth and share cookies shipped without Secure.

The session menu's Full screen opens the conversation in its own browser tab. That tab renders the route directly — and the route is the responsive page, so a 24" screen got the phone shell: a hamburger opening the mobile drawer, and a back arrow that dropped the whole tab into the responsive application, workspace root included.

The receipt lands on top of the session search field, and the only way out was the six-second timer. The notification toast right below it has been dismissible with an upward flick since it shipped, so the gesture was already the expected one — it just was not wired here.

Two copies still shared a single point of failure: the host that pulls them. The pull host now also pushes to R2, so the relay stays credential-free — it holds nothing that could reach or erase any copy.

The shared conversation pins each question and hangs a stepper on it — previous, n / N, next. The session view has the same pinned question, so it now carries the same control, on desktop web, responsive web and native mobile.

The bench only ever mounted the transcript on its own route, so the desktop workbench — the one place where the reading column lives inside a panel that can be resized under it — was never covered. It now opens a session from the list, then squeezes the panel to a narrow width: the stepper must hang on the reading column's edge and stay inside the panel, never on the window edge and never clipped.

The authenticated server catalog is authoritative, but every cold start falls back to an embedded list that still stopped at Grok 4.5 and at three reasoning efforts. A Grok account that offers Grok 4.6 with X-High therefore lost both until the first catalog answer arrived, and the shared client fallback disagreed with the server.

Codex starts MCP servers with a sanitized environment, so a capability read from AIRCODECREDENTIALFILE is simply absent there. The browser server then failed on every call, and the Knowledge server — whose tool list is derived from the capability — advertised no tools at all, which is indistinguishable from a session that has no Knowledge. Both servers now accept --credential-file, like the planning server already did, and the Codex registration passes it.

Indexed code outnumbers indexed history several times over, and the lexical ranking weights a chunk's title and path above its text. An unfiltered search therefore answered with source files even when the answer had been written in a past conversation — and an agent searches once at the start of a task and never comes back, so the first page has to carry it. Half of an unfiltered first page is now reserved for conversations, decisions and notes, keeping the strongest overall match first and alternating from there.

A preview answered with a single launchUrl, and one link cannot serve both uses. The capability travels in a SameSite=Lax cookie, so an embedded preview keeps its access only while its origin stays same-site with the page showing it: a workspace served from localhost that embedded the relay origin lost the cookie and the preview answered "access denied". publicSession now answers with the transport the client itself arrived on, and adds shareUrl, which prefers the relay whenever the tunnel publishes one.

A standalone Fast preview publishes a URL; an application owns the process that serves it. Promotion now turns the first into the second on the same preview record, so the port, token, password and relay alias the user already shared keep working. The entry point is the Fast preview card in Browser, on desktop web, responsive web and native mobile.

An owner can now publish a whole conversation or a contiguous range of completed turns as one sanitized, immutable snapshot, in two renderings of the same document: a self-contained HTML export, and a revocable link served by the owner's own instance, optionally password-protected, optionally expiring. Both come from the same renderer, so the page a reader opens is the file the owner reviewed.

Read the download settings inside the write transaction so a mode chosen during a long synchronization is no longer overwritten, show a preparing state while offline storage is still opening, and coalesce cache-change notifications so a download storm stops starving the interface.

Marking read by in-app destination lets opening a session clear every pending row that pointed at it, on the server and on all three surfaces, without resolving an attention row.

Sequential requests are the protection, not the spacing: a foreground drain now runs until the queue is empty and stops on pause, storage, pressure, auth, profile switch or transport failure. The background invocation keeps its OS-enforced budget.

Connection thresholds move to shared constants with a slow state between healthy and lost, and the Focus Plans bridge panels give way to sticky phone tabs.

Add per-conversation and whole-library storage estimates, a staged background download queue with visible progress, live ingestion while the app runs, offline purge and storage monitoring, higher storage limits and a "Last N conversations" mode, across the server, native mobile and web.

The Offline access screen now reads storage estimates, download progress and disk space, so the fixture bundle gains those exports and a rendering failure reports the page error instead of a locator timeout.

Ship stops in three ways and only one is a failure: a published run whose local branch never realigned now proposes a guarded correction the user approves, with the blocker named as data instead of prose, and dirty paths that already carry the published bytes absorbed by the convergence helper.

The canvas stays deep, but each surface stacked on it now climbs a clear lightness step. At the previous spacing the assistant reading surface sat barely above the artwork glow, so long answers read as unframed copy on the background, and semantic blue only reached 2.9:1 against the card.

The native feedback pill hung on a negative top margin, so it collided with the card above — whose own bottom margin is 4 px — and read as a piece of that card rather than as the verdict on the turn below it.

A prompt waiting in the queue was only visible inside its own session, so a directory of sessions gave no sign that work was already lined up.

Mark read opened from the leading edge and Kill from the trailing one, so acknowledging a completed session meant learning that one row answers to two opposite gestures. Both actions now live in the right-side drawer, Mark read first, and the reveal widens to fit whatever the row renders.

Google withdrew Gemini CLI for individual accounts on 2026-06-18 and points that plan at the Antigravity suite, which the product already exposes as its own engine. Keep the engine registered so existing sessions and transcripts still resolve, mark it retired, and drop it from engineCatalog() — every launcher, Ship dialog, run dialog and AI Usage card is built from that catalogue, so one filter removes the choice everywhere.

install.sh resolves the stable channel by default and no stable manifest is published yet, so the copy-paste command in the README, the website, the docs and the CLI update hint all failed with "could not resolve latest stable version". Every advertised one-liner now selects --channel beta from a single site constant, and install.sh names the working command when a stable install finds no manifest.

The Fast preview challenge page, its Siteverify client, and the three client-side challenge hosts each carried their own copy of the same logic. Extract the reusable primitives so a new protected surface only declares its action, paths, and rate limiters.

Password sign-in was protected only by the local attempt throttle, so a reachable instance could still be probed automatically. Every /api/auth/login call now carries a Turnstile token that the server verifies through the accounts worker before the password is checked; a failed or replayed token answers 403 TURNSTILEFAILED.

Passwordless pairing refused any non-HTTPS exchange, so the common case of two devices on the same LAN or private VPN could never use a QR code at all. The HTTPS default stays, but an authenticated operator can now opt one specific five-minute capability into an HTTP exchange.

The changelog derived "latest release" from the curated notes and the build failed unless they matched the product package exactly. A new beta therefore either shipped with a stale website or forced editorial notes to be written before the release could be announced.

Native Liquid Light was flat where responsive web has depth, and its overlays leaned on one generic glass preset. Clipping the material and casting the shadow on the same view cancels the shadow, so the shell and the material are now separate: an unclipped exterior carries the outset depth while a radius-clipped child holds blur, tint, prism, sheen, and the border rails.

The hover command inside the unread badge paired a mail glyph with its label in a space sized for the label alone, so the text was the part that lost room. Keep the wording and remove the glyph.

Session titles rank ahead of passing message mentions, while legacy tabs recover their durable conversation identity.

Completed sessions can be acknowledged without opening them, keeping unread work accurate with fewer navigation steps.

Native views paint the full Liquid Light interior and preserve a consistent reading surface from edge to edge.

Elapsed-time indicators, feedback actions, dark messages, planning, and queue labels now carry less visual ambiguity.

Offline sessions and search results share clearer detail controls and more predictable navigation across screen sizes.

Usage surfaces explain reset windows more precisely and keep their information hierarchy readable in wide layouts.

Liquid Light surfaces, native perimeters, pill geometry, and composer density now align more consistently.

Launch flows share the live Engine, Model, Effort, and supported Permissions choices, with Claude defaulting to Opus when it is available.

Notification Center, Focus Plans, Project TODO, Project Health, and startup hand-offs now share the same luminous material hierarchy.

Past audits move into a detailed report picker so status and findings remain visible while older reports stay easy to reach.

Every surface presents the same six period metrics in the same order and labels cost according to whether it is reported, mixed, or estimated.

Gustav, Irezumi Tide, and Liquid Light use clearer reading surfaces, controls, and palette behavior across web and mobile.

Long conversations keep image galleries, attachments, and composer transitions responsive while messages paginate.

Responsive web and native mobile align more closely on session navigation, activity details, tags, and back behavior.

Notification history persists across restarts and groups related updates by destination and day without discarding earlier events.

Focus Plan launches and review actions use a clearer, more direct flow across web and mobile.

Images in web conversations can be opened and navigated as a gallery without leaving the active session.

Finding details now separate evidence, impact, and recommended action more clearly, making review decisions faster.

Project creation, source-control workflows, and mobile terminal controls now expose clearer actions and state.

Planning surfaces, live-session activity, and the workspace hierarchy are easier to scan and navigate.

The activity rhythm fills its available grid and shared actions remain readable across supported themes.

AI-assisted actions use the same understandable label across web and mobile.

Completed work stays behind its summary and attention previews fit on one concise line.

Version-sensitive provider update controls now share one guarded policy.

AI Usage opens on all retained history and Git statistics stay in the Project tab.

Settings groups and navigation behave consistently across desktop, tablet, and mobile widths.

Mobile progress motion and completed-turn actions are less distracting while remaining discoverable.

Knowledge preparation prioritizes useful retrieval and defers handoff context until the next user message.

Usage snapshots persist against the selected time zone and mobile age labels stay current.

Composer actions, themed activity, Settings navigation, and mobile Git labels hold together at narrow widths.

Conversation matches are ranked with bounded recency so relevant recent work appears first.

OpenRouter accounting and model usage behave consistently across supported engines.

Unfolded layouts, session navigation, Explorer uploads, and Knowledge handoff better match desktop capabilities.

Running-session motion uses shared sprites and the Working graph renders reliably across dense lists.

Launch surfaces show connections that are actually available instead of presenting unusable options.

Server health information is organized into clearer diagnostic sections on mobile.

Loading sections begin collapsed while live state and elapsed time stay easy to scan.

Native launch configuration exposes the same essential connection and runtime choices as the web workspace.

Completed and failed Runs have clearer status, actions, and cleanup behavior.

Knowledge context preserves the user prompt and review workflows make source handoff easier to understand.

Diagnostics distinguish the application server from the host machine it runs on.

Navigation, session cues, provider accounts, and terminal flows are polished across desktop and mobile.

Sessions retain the selected Antigravity model for status and usage reporting.

Active Runs report how long they have been working.

Common actions across the grouped workspace tools require fewer context switches.

Background work is organized by active, completed, and attention-needed state.

Essential conversation actions remain reachable while product Runs are active.

Session and workspace integrations follow the same contract across web, desktop, and mobile.

Desktop packages can recover a compatible bundled CLI artifact when the normal source is unavailable.

ANSI colors remain readable across every supported terminal theme.

Usage gauges can request fresh provider data instead of rereading a stale cache.

Legacy timeline views are retired in favor of Focus Plans and direct task actions.

Native session and activity timestamps refresh when the app returns to the foreground.

The narrow web layout follows the same primary navigation model as the native app.

Browser is a top-level destination and every mobile full-screen route retains a clear way back.

The composer chip shows permission tier and model while Focus Plans remain manageable from any local session.

Agent-rendered images appear in chat and generated images remain available in session assets.

Focus Plan guidance begins collapsed so active tasks remain the visual priority.

Text and controls use semantic surfaces instead of relief effects over artwork.

Web and mobile artwork themes share calmer translucent activity and reading surfaces.

A successful Ship realigns the checked-out branch with its published target history.

The startup agreement explains the basic pseudonymous product statistics included with use and links to full privacy details.

Artwork-backed themes use clearer local reading surfaces and more consistent product chrome.

The public website exposes the final legal documents and identifies the Swiss licensor.

Account and connection settings are grouped into a clearer web preferences flow.

Mobile theme surfaces and platform controls better match their interaction context.

Usage views support local reporting time zones and faster date movement.

Active tool work is represented consistently across supported engine transcripts.

Terminal scrolling and tablet roadmap navigation work with native touch gestures.

Animated code rain, canvas layering, and mobile bottom-bar contrast are tuned for readability.

Usage cards identify providers with their expected visual identity.

Launch controls explain the effect of higher permission tiers before a session starts.

Usage periods compare equivalent elapsed windows instead of mismatched full days.

Mobile usage views and account settings expose the same core information as web.

The launch form prioritizes the prompt and core runtime controls.

Session polling uses compact snapshots and adapts heartbeat frequency on mobile.

Code samples and mobile download previews retain contrast across website themes.

Review workflows provide clearer evidence and action paths.

Native Sunset navigation gains a lighter translucent treatment.

Transcript adapters follow one shared contract across engines.

Session lists and live status make active work easier to distinguish.

Sidebar search removes unnecessary hierarchy and quiets completed attention states.

Usage views expose more detail within the day for comparing sessions and agent work.

Native navigation and session interactions require fewer corrective taps.

Dock resizing and the Sunset bottom bar respond more cleanly on large mobile screens.

Links and project files in mobile chat open in the correct destination.

Native session screens reduce unnecessary polling and render churn.

Native completion notifications can be cleared with a swipe.

Session navigation and engine changes require fewer intermediate screens.

Source Control begins in the safe, guided publication mode.

Mobile navigation headers respond to content position without hiding essential actions.

Browsing and activity filters make active, resumable, and completed work easier to find.

Native session controls share one clearer visual hierarchy and recap flow.

Visitor-selected website themes, native Sunset surfaces, and workspace controls stay aligned.

Native views follow one current project instead of maintaining conflicting local choices.

Web and mobile session controls put the most useful recap actions first.

The homepage and sunset-bordered calls to action explain the cross-device workflow more directly.

Mobile navigation keeps essential session actions reachable and streamlines the session shell.

Web tools share one organized activity bar instead of competing for workspace space.

Web and mobile surfaces share the same canonical sunset theme colors.

Session, planning, Knowledge, preview, and theme behavior align across web and native clients.

The website demonstrates the cross-device workflow and provides a concrete feature comparison.

Reusable session context stays scoped to the relevant project without overwhelming the prompt.

Desktop payload links, Android signing checks, and portable package structure are validated before publication.