## Why
Sidebar previews load a snapshot of the file when opened, so edits on disk
leave the open tab showing stale content.
## What changed
Watch each previewed file’s parent directory through the app server so the
preview refreshes even when an editor saves by atomically replacing the file.
Poll every three seconds when a watch cannot be registered, and resubscribe
when reconnecting to the same backend.
Preserve the text preview’s reading position across reloads, including when
the file temporarily becomes unreadable and then returns.
## Testing
The sidebar test covers atomic saves and recovery after moving a directory
away and back. It checks that the tab shows updated content at the existing
reading position.
GitOrigin-RevId: d5f7507d1a81a118fb10a0febf5e274c18f19d81
## Why
An unsupported `\underbrace` leaves the display equation as LaTeX source,
so readers have to interpret which terms each label groups.
## What changed
Render `\underbrace{expression}_{label}` with a Unicode brace that spans
the expression's terminal columns and a label centered below it. Keep
surrounding math aligned with the expression. Inline math, unsupported
arguments, and layouts that exceed the available width still use the
existing fallback.
## Testing
Add a snapshot for labeled Boolean clauses, short expressions, and labels
wider than their expressions. Check fallback for inline, malformed,
nested, multiline, and over-width cases.
GitOrigin-RevId: 8fbe92d512d06c73cf21247343ad869743bebd0c
## What changed
Request emoji presentation for the cloud marker in thread labels.
Preserve the emoji variation selector immediately after the cloud
symbol in Unicode terminal titles and keep GNU Screen titles ASCII.
## Testing
Update rendering snapshots for the task overview, side panes, mentions,
resume picker, and thread identity displays. Extend the terminal title
test to cover the cloud marker in both title encodings.
GitOrigin-RevId: 15959a0760f63a45d8fff917df2e008cda7536a5
## Why
A fixed gap cannot keep two statusline groups at opposite edges as the terminal width changes.
## What changed
Set `justify: "between"` on a root `row` to distribute spare footer columns between its items on each line, in addition to the configured `gap`. Nested rows size to their content within the available width, so they can keep related fields together.
Use `justify: "start"` to pack items at the leading edge with the configured gap. Both explicit modes group adjacent bare strings into one item. Separate `text` or `row` elements can be positioned independently. Omitting `justify` preserves the existing gaps between authored children.
## Testing
Add renderer tests for edge alignment during resizing, spacing on wrapped lines, and root versus nested rows. Extend the row decoding tests and the TypeScript contract fixture to cover `justify`.
GitOrigin-RevId: 3319e688f3adfe6d35709ef279345f1db3eb9693
## What changed
Use `esc close` to show how to combine the Escape binding's display
label with the action text and use the shared shortcut styling in
views and mockups.
GitOrigin-RevId: 0bb0dc94e503932443076dbe2495e5494e3df5b2
## What changed
Apply the same Unicode combining tilde as `\tilde` when the
`\widetilde` argument is a single grapheme.
## Testing
Extend the Unicode math snapshot to cover both `\widetilde{I}` and
`\widetilde I` in fraction numerators.
GitOrigin-RevId: e6976f998bb0955ba9c73117bd19dd814b07399a
## Why
The terminal renderer already supports line breaks in flowchart node
labels. The same syntax in an edge label causes the diagram to fall
back to source text.
## What changed
Treat `<br>`, `<br/>`, and `<br />` as line breaks in edge labels.
For example, `A -->|"Review<br/>order"| B` renders the label on two
lines. Reserve space for each line and preserve blank lines without
erasing edge connectors.
## Testing
Add snapshots for all four layout directions and update the terminal
Markdown snapshot to include a multiline edge label. Test blank lines
and terminal width limits.
GitOrigin-RevId: 277525d92c6c1f105bc34516893c67eccc22a22c
## Why
Clients need to distinguish a caller who must enroll in Daybreak from a
model that does not support it. The list of accepted access programs
alone cannot express that distinction.
## What changed
Carry the server-resolved status for each caller and model from the
model catalog into `model/list` as `availableAccessPrograms.daybreakAvailability`.
Update the JSON schemas, TypeScript bindings, and Python SDK to expose
the field.
Rust decoders use `default` for missing or unrecognized statuses. The
Python SDK also defaults missing statuses and preserves new strings
from newer hosts.
## Testing
Cover catalog decoding, app-server response serialization, and Python
SDK round trips with known, missing, and future status values.
GitOrigin-RevId: c1e5ddef68fd19b25e583bb6996a93fd78ab9d18
## Why
Cloud turn and item pages can reflect different points in time. A reply
restored from history may still be unfinished even when its turn is marked
complete. When the final text arrives, the TUI can leave a stale prefix in
the transcript or put the final reply after intervening tool output.
## What changed
Track Cloud replies by turn and item across history replay, pagination, and
live streaming. Reserve a transcript position even for an unfinished reply
with no visible text. When it completes, replace its fragments in place or
remove them if the final text contains only hidden directives. Keep late
completions from interrupting another reply's stream.
Preserve transcript order when choosing the latest copyable reply. When a
turn completion notification has no response text, fall back to the latest
completed response from that turn.
## Testing
Cover replies restored from older history pages, late completions during
another stream, and directive-only completions that remove a visible prefix.
Check the resulting transcript order, copy text, and notification fallback.
GitOrigin-RevId: a0abb75bf1378524461a519fe9a0656e15bca4bf
## Testing
Add a regression test that checks that hovering over a saved chat's
preview highlights both its title and preview without moving the
selection. Moving to the title keeps the highlight without requesting
another redraw, and moving to the Side chats heading clears it.
GitOrigin-RevId: d54501f28c00112281389f67bb3671dfa6b18513
## Why
The pointer shape can signal that transcript links are clickable, but the
text itself does not change on hover. A foreground change makes the
clickable region visible.
## What changed
Change the foreground color of hovered transcript and status-line
links, transcript disclosure controls, and the warning notice. Use the
rendered link spans so the highlight follows the visible text, including
wide characters. Recompute the highlight on redraw so it follows the
content under a stationary pointer as the transcript scrolls or updates.
## Testing
Add a mouse-motion regression test that checks highlight and restore
behavior for transcript links, including wide characters and Markdown
table links, as well as status-line links, disclosure controls, and the
warning notice. The test also checks that a URL in the editable draft
keeps its original styling.
GitOrigin-RevId: 4c7da58705e2ad4c710ec6c55727d5a064f3cf1f
## Why
Custom status lines previously depended on a feature flag in the TUI
client's configuration. When the TUI connects to a separate app server,
that flag can differ from the setting in the server's active profile.
## What changed
Add **Custom status line** to `/experimental` as an opt-in feature. Save
the toggle on the connected app server, restart the TUI, then use
`/statusline` to choose a provider.
Read `tui_extensions_statusline` from the app server's effective
configuration at startup. Keep that value when switching conversations
or reloading local status line preferences, so toggling the feature
takes effect on the next TUI launch.
## Testing
Add a menu snapshot and regression coverage for saving the toggle in a
server profile while preserving the active provider across a thread
change.
GitOrigin-RevId: 4025c9771e560d6d7b1e6bd97236bffc44201556
## What changed
Use `Overlay::input_transcript` to determine which overlay handles
transcript interaction keys and which keymap context applies during
search and selection. Apply runtime keymap bindings through `Overlay`
so the app can refresh them without matching the transcript variant
directly.
GitOrigin-RevId: 3592ddb62a6bddb760e2923604faff41a28cd150
## Why
A TUI connected to an app server on another platform can receive workspace
roots that its own filesystem cannot represent. For example, a Windows
drive path from the server cannot be stored as a native absolute path on
a Unix client.
## What changed
Keep `runtimeWorkspaceRoots` as native path strings on the wire for thread
start, resume, and fork. Validate absolute paths on the server and store
the returned roots as `PathUri` values in the TUI. Use the session's roots
for active remote forks, including side chats, and preserve permissions
for those roots in the TUI's permission display.
## Testing
Cover thread startup with workspace and writable roots from another
platform, remote root retention through start, turn, resume, and fork,
and server rejection of relative roots.
GitOrigin-RevId: 1e9e3bff64a6e7ddadb941f16c4952c44724af54
## Why
A TUI connected to an app server on a different operating system could
fail to decode a workspace-write policy. For example, a Unix client could
reject a Windows writable root such as `C:\extra` because it is relative
under Unix path rules.
## What changed
Keep `writableRoots` as path strings on the wire. Use path URIs to
preserve server paths when displaying thread permissions, and forward
the original sandbox policy to the first turn of a child thread that
inherits a legacy policy. The app server validates that each writable
root is absolute on its host before enforcing a policy supplied to
`command/exec` or `turn/start`.
## Testing
Cover writable roots from another platform in permission profile
templates, their round trip through thread lifecycle responses, and
rejection of home-relative roots during enforcement conversion.
GitOrigin-RevId: 57365b977bfced6c6ee864a0e54f25e8f9d09981
## Why
A remote app server can report a working directory in a different path
convention from the client. Decoding a Windows drive path as a client-native
absolute path can make a Unix client reject the thread response.
## What changed
Keep thread `cwd` values as server-native strings in summaries, settings,
and start, resume, and fork responses. Preserve the JSON and generated SDK
types. In the TUI, store the session directory as a `PathUri` using the
server's path convention when available. Use that directory to match diff
and skill results and to display the project name in the terminal title.
## Testing
Add regression coverage for foreign-path response round trips, diff results
matched against a remote session directory, and terminal titles derived
from a Windows path. Verify that the server rejects a working directory
that cannot be encoded as UTF-8.
GitOrigin-RevId: 600f0b531939db4cd4ec884de166224082995e00
## Why
When a file preview fails, the generic error can leave users guessing
which file failed, especially when the sidebar truncates the tab label.
## What changed
Show the filename and directory in the failed preview. Give users
specific guidance for missing files and permission errors, and retain
the error details for other failures. If the file link cannot be
resolved, include the original path in the chat error.
Preserve typed filesystem RPC errors so the preview can classify
failures from `fs/readFile`, and strip the server's diagnostic payload
before the errors can reach TUI logs.
## Testing
Cover narrow-pane error rendering, missing-file and permission error
classification, unresolved links, and diagnostic payload removal for
remote file reads.
GitOrigin-RevId: 1db35c831bb112d67e8c0171a85a20d02cc15a08
## Why
The slash command menu helps users find commands, but leaves them to
recall fixed arguments such as `on` and `off` for `/raw`.
## What changed
Show prefix-filtered suggestions for the first argument of supported
slash commands. For example, type `/mcp lo` and press `Tab` to complete
`/mcp login`. `Enter` and configured submit shortcuts still submit the
draft as typed.
Give mention completion priority and limit argument suggestions to
commands available in the current thread and connection state.
## Testing
Add tests for popup rendering, argument replacement, submit shortcuts,
and changes in thread availability and connection state.
GitOrigin-RevId: 8682c323064457dd9307b0a1520469011a8df9f3
## Why
Read-only chats offer a Left Arrow shortcut to the command center when
agent navigation is available. Chats blocked by model provider errors
were missing that shortcut.
## What changed
Share notice rendering and shortcut availability between provider
errors and read-only threads. Show `← command center` on provider error
notices when the shortcut is available, and open it on a plain Left
Arrow press even when offline.
## Testing
Add a regression test that checks the shortcut hint, verifies that
repeat events leave the notice open, and confirms that opening the
command center preserves the draft both online and offline. Update
provider error snapshots to cover the new hint, including at narrow
terminal widths.
GitOrigin-RevId: be2ce80cade02c84baeff7fd48fa8973f0dcc1dc
## Why
Conversation search results can point users to saved transcripts. Users
need to be able to follow those links without leaving their terminal session.
## What changed
- Make Markdown links such as `[Review notes](codex://threads/<id>)`
open the linked conversation from chat and transcript views. In the
resume picker, follow the link to another transcript preview.
- Resolve nested agent links through their owning session and select the
requested agent. Show archived conversations in read-only mode and
let users explicitly reopen them.
- Include the Markdown link format in thread search results, including
archived results.
## Testing
Add coverage for thread link parsing and activation, nested agent
navigation, archived thread reopening, and mouse capture during
transcript preview transitions.
GitOrigin-RevId: 40a39c43acf643b97e066ba663aefcf9cda0bc81
## Why
Generic quota errors hide whether the project or organization spend limit
blocked a request. Reporting the scope tells users which limit to check.
## What changed
Recognize API key, project, and organization spend limit errors across
HTTP, SSE, and WebSocket responses. Show a message that names the scope and
treat the error as non-retryable, even when the provider sends
`Retry-After`. Apply the existing usage-limit handling to goals and
compaction.
Expose distinct `CodexErrorInfo` values in the app-server protocol and
generated bindings so clients can identify the limit in live errors and
failed turn history.
## Testing
Extend the transport tests to cover all three scopes and verify that they
stop retries. Extend the app-server test to check that the error survives
`thread/read` and that a subsequent turn can succeed in the same thread.
GitOrigin-RevId: 03341f7a78daa7540e7baa519f1a29ec07e34509
## Why
A realtime call can end with completed speech that has yet to reach a
Codex turn. The next turn needs that context even if the call's transport
has already disconnected.
## What changed
- For V3 calls with realtime frame history enabled, save pending speech
as context for the next turn. Restore it on thread reload and exclude
it from the turn count used by rollback.
- Drain already received transcript events and settle pending handoffs
before saving the call's closing marker. Report recovery required if
shutdown cannot confirm that history was saved.
- Keep transport detach separate from ending a call. Reattaching restores
saved pending speech, and an open call can be ended from persisted
history after a reload. Use the call ID for TUI attachments so successive
calls on one thread have distinct history.
## Testing
Add coverage for queued speech at hangup, reconnect and stop after
reload, retries after an uncertain write, and rollback across saved
session-end context.
GitOrigin-RevId: 657491f1d7e446a1a48e22189758810c8bdd82cb
## Why
The app server's Bedrock setup and login flows always selected Mantle.
Clients using Bedrock Runtime had to configure that provider separately.
## What changed
Accept an optional `providerId` in `account/bedrock/setup` for AWS profiles
and environment credentials, and in `account/login/start` for Bedrock API
keys and AWS access keys. Pass `"amazon-bedrock-runtime"` to select
Runtime. Omit the field or pass `null` to keep the Mantle default.
Save configuration for the selected provider and check that provider for
an existing `aws.credential_export` before changing credential sources.
## Testing
Extend app-server tests to cover Runtime setup with profiles and
environment credentials, Runtime login with both key types, and Mantle
fallback. Verify that environment setup selects the Runtime default
model for a new thread and that a configured Runtime credential exporter
blocks profile setup.
GitOrigin-RevId: 6396b638208ab9b12f50f13f13bd517a919d0848
## Why
A choice taller than the TUI's answer area could never be displayed in
full at that terminal size, so users could neither read it to the end
nor submit it.
## What changed
Let `PageUp` and `PageDown` scroll through the wrapped lines of an
oversized choice while keeping it selected. Allow submission once every
line of the choice has been displayed in order and at full width.
## Testing
Add regression coverage for paging without changing the selection,
rejecting submission when repeated page keys skip lines before redraw,
and rejecting choices clipped horizontally.
GitOrigin-RevId: c296323494bd387581c2bb046272a8ccd773ad75
## Why
`/status` appends `(unknown)` to the server label when a cloud or remote
server does not report a version.
## What changed
Show the cloud label or remote address on its own when the version is
unavailable. When a version is reported, use the same `v` prefix for cloud
and remote servers. The daemon menu still displays `unknown` for a running
local daemon whose version is unavailable.
## Testing
Add `/status` snapshots for cloud connections with and without a reported
version and for a remote WebSocket connection without a reported version.
GitOrigin-RevId: 113d2502fc7de6af37da3b3029ee28923af29e6f
## Why
Row and page navigation make users step through tasks to reach another group.
## What changed
Use `Shift+Down` or `Shift+J` to jump to the first task in the next
visible group, and `Shift+Up` or `Shift+K` to jump to the first task
in the previous group. Navigation stops at the ends of the list.
Expose `agents.next_group` and `agents.previous_group` in the keymap
picker and show the active shortcuts in Task shortcuts.
## Testing
Add coverage for jumps in both directions, list boundaries, and key
handling during search and rename. Update snapshots for shortcut help
and the keymap picker.
GitOrigin-RevId: 2542a75e7fdd7a3326c0914e19a9f5c191de082b
## Why
An immediate redraw can happen before the TUI receives a resize event.
For example, submitting a turn just after shrinking the terminal can
render the frame using the previous dimensions.
## What changed
Resolve the screen size and run resize handling before immediate paints
for turn submission, session lifecycle actions, startup modals, Cloud
switching, and shutdown. Consume the reserved size when drawing the frame
and preserve the scheduled recheck for settled terminal dimensions.
## Testing
Add regression coverage for fullscreen turn submission and archive
progress after a terminal shrink, plus checks that a draw consumes its
reserved size and an early paint preserves the scheduled size recheck.
GitOrigin-RevId: 494c746cb02712350cc600ea4aea64460c608639
## Why
When the composer footer gains or loses a hint row, typing the first
character or deleting the last one can move the caret vertically.
## What changed
Reserve a row for passive footer hints when the status line is visible
and there is room after laying out the input, slash-command suggestions,
and previews. The row can stay blank until a hint appears.
## Testing
Add a regression test that checks the caret row before typing, after
typing one character, and after pressing Backspace. Extend coverage to
check that slash-command suggestions and a short status line fit together
when space is tight.
GitOrigin-RevId: 25df697826cebc4b7cb4aab4460c432b7454d5ea
## What changed
Move subscription state updates, history hydration, and resumed session
setup into `finish_thread_resume`. Let callers supply a
`HistoryHydrationScope` and keep using `HistoryHydrationScope::Initial`
for the existing resume path.
GitOrigin-RevId: ebb8b422827a2374d8dce194e8d59afe57327f29
## Why
When a transcript mentions a subagent, readers have to find it in the
sidebar chooser to inspect its work.
## What changed
Underline subagent labels in transcript activity when the sidebar is
available. Clicking a label opens that agent's transcript beside the
parent conversation, including when the link is in an unfocused pane.
Use backend ancestry to confirm that the linked agent belongs to the
current conversation. If a click arrives while agent discovery is in
progress after resume, resolve it when discovery finishes.
## Testing
Cover clicks from the parent transcript and a nested-agent link in an
unfocused pane, along with clicks during discovery and inherited
activity from a fork. Snapshot the underline across a wrapped label.
GitOrigin-RevId: 75b343c56eac4a009d644f0cfc135b6d9bfbe3a0
## Why
Selecting a subagent from the sidebar switched the active conversation
to that agent. Keeping the parent conversation visible makes it easier
to review the agent's work in context.
## What changed
- Open the selected subagent in a sidebar tab alongside its parent
conversation. Switch focus between the two panes as needed.
- Show parent-owned subagents in a watch-only reader with transcript
navigation, search, and selection.
- Press `Esc` from the reader to return to the subagent list with the
same agent selected. The tab also supports the sidebar's close button
and close shortcut.
## Testing
Add a TUI integration test that opens a saved subagent through the
sidebar, snapshots the watch-only view, and covers transcript
navigation, search, resizing, and tab dismissal.
GitOrigin-RevId: 60da0759b7c046c33b665abdbb063153c5beafa4
## Why
An in-flight Cloud task list from the agents overview can keep the Cloud
worker busy while the TUI waits for a session request, such as listing
tasks in the resume picker or unsubscribing from a discarded blank task.
## What changed
Cancel the affected backend's Cloud overview refresh when dismissing the
overview or before session operations that need the same worker. Wait for
the aborted task to drop its request before proceeding. When opening the
resume picker, clear queued Cloud refreshes first so canceling the active
refresh cannot start another page ahead of the picker's requests.
## Testing
Add regression tests that hold Cloud list requests open while returning to
the current chat, opening the resume picker, or switching backends.
Cover canceling a refresh before starting a fresh plan implementation
session and preserving another backend's in-flight page during archive.
GitOrigin-RevId: 94993aa0014ac895a30f454e3ff5f4cbc45bb429
## Why
The sidebar chooser lists side chats and files. Adding subagents lets
users check their progress and switch to their conversations from the
same menu.
## What changed
- Add a `Subagents` section for the main conversation's spawn tree.
Show each agent's name and status, and let users select an agent to
switch to its conversation.
- Keep explicit outcomes such as `Completed`, `Stopped`, and `Failed`
visible through idle or unloaded updates. Restore outcomes from saved
activity and give live updates precedence over in-flight discovery.
## Testing
Add wide and narrow chooser snapshots and regression tests for outcome
retention and discovery updates that race with live notifications.
GitOrigin-RevId: 93092e6bd5c59724f69f52785e3c22aa2c1313d8
## Why
Rapid wheel input can trigger a synchronous transcript redraw for each tick, even when the current layout can still be used.
## What changed
Accumulate wheel movement in the main transcript and side panes until the next frame when the rendered layout is safe to reuse. Refresh first when the transcript has changed, cached content can change height, or the side pane has buffered reply text. Refresh immediately when toggling side-pane zoom so subsequent mouse events use the new layout.
Start composer scrolling from the caret-adjusted viewport after an edit so wheel ticks can accumulate before the next frame.
## Testing
Cover wheel bursts while the plan menu is open, composer scrolling after edits, refresh requirements for mutable history and buffered side replies, and immediate layout updates when toggling side-pane zoom.
GitOrigin-RevId: 342d4d4c014d8a41b2e690b91622197ee97fc059
## Why
App-server clients receive `account/updated` both when routing is ready
for a saved ChatGPT workspace and when a user logs in, logs out, or
switches workspaces. The notification payload gives clients no explicit
way to identify the initial routing update.
## What changed
Add a nullable `reason` to `account/updated`. Set it to
`workspaceRoutingReady` on the initial saved-workspace routing
notification when the authenticated owner is unchanged, including when
routing is ready before the connection initializes. Login, logout, and
workspace-switch updates send `null`. Update the protocol schemas,
TypeScript types, and Python SDK models.
## Testing
Extend the app-server integration tests to check the reason in the JSON
payloads for saved-workspace discovery, login, workspace switching, and
logout.
GitOrigin-RevId: 96758519985a6bdb07474e48307ed53b125823ee
## Why
Listing root threads for chat and task analytics can trigger filesystem
scans and metadata repair. The state database can serve these lists
without that work.
## What changed
Start root thread pagination with `thread/list` and `useStateDbOnly`
enabled. If the server returns JSON-RPC error `-32603`, discard the
partial results and restart from the first page with filesystem repair
enabled. SQLite cursors may identify different pages in the filesystem
listing.
## Testing
The chat analytics regression test simulates an error on the second
indexed page and checks that the fallback restarts pagination, excludes
discarded results, and preserves the usage estimate budget. The task
analytics test checks that only root listings use the database-only mode.
GitOrigin-RevId: 9de78a9eca4662df06d22a86cffb6e7bcba428cb
## Why
Clients using `thread/search` have to wait for the search to finish before
they can show any matches. A search can also outlive the query that triggered
it, such as when a user changes their task mention query.
## What changed
- Add experimental `thread/search/stream` with best-effort
`thread/search/partial` notifications. Each notification carries the original
`requestId` and a batch of verified matches. Clients replace provisional
matches with the final page, which determines results, ordering, and cursors.
- Support connection-scoped cancellation through `thread/search/stream/cancel`
and `thread/search/cancel` for their respective search methods. Disconnecting
also stops active searches and reaps their search subprocesses.
- Cancel superseded or timed-out TUI task mention searches without delaying
available title matches.
## Testing
Add coverage for incremental results and final-page parity, slow clients,
connection-scoped cancellation and subprocess cleanup, and TUI task search
cancellation.
GitOrigin-RevId: b58abf7a1df424f191c8ede806d1d5266d299548
## Why
The resume picker starts local-only listings from the state database.
When multiple backends are available, the shared listing mode makes
local backends use the default thread store listing too.
## What changed
Choose the initial page mode per backend. Local workspaces start with
`StateDbOnly`, and remote workspaces use `StoreDefault`. Each backend
paginates in its current mode and can fall back to `StoreDefault`
independently. Explicit recovery requests keep their requested mode.
## Testing
Cover mixed local and remote listings, per-backend fallback and
pagination, and an explicit recovery request after fallback fails.
GitOrigin-RevId: d0c9284211b86bb781b3df6642660054cb3c6ccf
## Why
The status line and terminal title pickers duplicated the logic for
ordering configured items and displaying live rate-limit labels.
## What changed
Build both pickers' item lists with the same helper. Keep configured
items in order, skip unknown IDs, and collapse aliases to one row per
canonical ID. Use live rate-limit names and descriptions when available.
Use the shared multi-select picker directly for terminal title setup
and opt it in to accepting input while disconnected.
## Testing
Cover alias deduplication and configured order, and assert that the
title picker accepts input while disconnected while the shared picker
defaults to disabling it.
GitOrigin-RevId: 48971f003bd73523599d1d1ad677d855844767db
## What changed
Open `/rc` (or `/remote`) to enable or disable remote control for the
managed local background server. The menu checks whether the preference
was saved for the next restart and reports when saving fails. Once remote
control is enabled, **Add device** displays a manual pairing code.
The command can also manage the local server while viewing a cloud
session. Its actions apply only to local sessions.
## Testing
Add tests for menu states, daemon requests and manual pairing, local
daemon selection from a cloud session, and timeout messages.
GitOrigin-RevId: 888abaec3b041d78a6b35a9e76e28cd7dc5305ca
## Why
Model fetches can delay the startup screens that PTY tests wait for. Daemon compatibility recovery also probes the daemon version on a separate connection before offering a recovery choice.
## What changed
- Configure the daemon compatibility and external editor tests with a local catalog of bundled models to avoid model-fetch delays.
- Return a complete `InitializeResponse` from the mock daemon and verify the version probe's `initialize`/`initialized` handshake before selecting recovery.
- Keep the daemon listener open and assert that the TUI does not reconnect after choosing to run without the daemon, for both explicit feature enable and disable scenarios.
GitOrigin-RevId: 243f5075fca42d1192f0087e2cc21a6b0796226b
## What changed
- Add `gpt-6.2-sol` and `gpt-6.2-astra` to the bundled, Amazon Bedrock, and Vertex catalogs, including Bedrock Runtime global and US cross-region variants.
- Make GPT-6.2 Sol the default catalog selection and refresh model ordering, descriptions, and bundled instructions.
- Increase the GPT-6.1 Sol context window to 500,000 tokens.
- Advertise the `ultrafast` service tier for GPT-6.2 Astra on Bedrock.
- Supply the same current model catalog to both executors in the prompt-prefix compatibility test so catalog updates do not cause prefix mismatches.
## Testing
Extend provider, app-server, and TUI coverage for catalog ordering, model fallback, Vertex requests, and GPT-6.2 Astra's Bedrock `ultrafast` selection and clearing behavior. Refresh model-picker and request snapshots.
GitOrigin-RevId: f28940e4a255fcdd88f7114873259bd1f3399812
## Why
`codex login --device-auth` still used browser authorization when config server sign-in was required, preventing the selected device-code flow from being used there.
## What changed
- Use device authorization for config server sign-in when `--device-auth` is selected, display the verification URL and code, and report a missing `config_server.oauth.device_authorization_url` explicitly.
- Include the configured OAuth `resource` in device authorization and token polling requests.
- Reserve sign-in per credential across Codex processes, reuse saved grants, and release the reservation when sign-in completes or is canceled.
- Report config server sign-in failures with guidance specific to `config_server.oauth` and the credential store.
## Testing
Add or extend tests for the device-code prompt, config server failure messages, OAuth resource parameters, policy reload after credential replacement, and rejection of concurrent sign-in with retry after cancellation.
GitOrigin-RevId: 013176d0e10128c347dd072b818e22b5038a2791
## What changed
Let users switch from the grouped shortcut list to a US QWERTY keyboard diagram with `Tab`. Highlight keys with unmodified runtime bindings and point users back to the list for keys outside the diagram. Choose an available function key when `Tab` conflicts with configured bindings or chord prefixes.
Fall back to the action list when the diagram does not fit, and size the guide to fit an `80x24` conversation view. Preserve input priority for sidebar navigation and active transcript interactions.
## Testing
Add snapshots and regression tests for keyboard layouts, terminal colors, small-area fallback, remapped bindings, and sidebar and transcript input priority.
GitOrigin-RevId: 606edcc25e9dc98d0548e86d4b7544cb97f2db6f
## What changed
Add `codex.statusline.provider_started` and `codex.statusline.provider_failed` counters through the existing status line metrics collector. Classify failures with `kind=timeout` or `kind=error`, and ignore events from stale readers.
## Testing
Extend reader and picker tests to check counters for explicit selection, polling, invalid content, timeouts, restarts, and stale events.
GitOrigin-RevId: 8c3074743f3b31409ccd713edb228e4dce809ea8
## What changed
Emit `codex.statusline.first_prompt` once per thread visit, with a `mode` label of `feature_off`, `builtin`, or `custom`. Reset the counter guard when attaching a different primary thread, and count only user prompts for the active primary thread. Use the existing analytics consent and exporter checks.
## Testing
Add coverage for counting once across first prompts and follow-ups on fresh and resumed threads, and verify that cloud async-question replies do not emit the metric.
GitOrigin-RevId: 3ba48a8fbbb3015d22de3252efcc5ae3ba96baab
## What changed
- Count status line picker openings and successful provider changes with fixed labels for enabling a custom provider, switching custom providers, and returning to the default. Skip unchanged selections and failed saves.
- Apply current analytics consent to the built-in exporter. Suppress built-in reporting for custom environments, unrecognized originators, or custom OpenTelemetry resource attributes and headers, while allowing explicitly configured OTLP collectors.
- Stop recording through the captured collector if the configured metrics exporter changes.
## Testing
Add assertions for picker and provider-change counters, unchanged selections, failed saves, custom resource and header suppression, and exporter changes.
GitOrigin-RevId: 600bc06d6587e83a6ca09241f0285b47d30a331e
## What changed
- Add “Create a custom status line” when `tui_extensions_statusline` is enabled outside cloud mode. Open a new conversation with an editable draft bound to the bundled `create-statusline` skill when available, falling back to a plain request otherwise.
- Preserve the previous thread’s draft and queued input, including input restored by a late interrupt, while switching conversations.
- Guard against stale create actions and held Enter submitting the new draft. Rename the provider action to “Choose a status line provider”.
## Testing
Add regression coverage for draft editing, bundled skill binding, input preservation, activation-key handling, dismissed setup actions, and hiding the create action in cloud mode.
GitOrigin-RevId: d40dd12914cf38968e605987f67d1ddee5ba7dd1
## What changed
Bundle a generated `statusline.d.ts` reference with the `create-statusline` skill, covering status snapshots, UI trees, colors, and canonical statusline item IDs. Add test-only `ts-rs` derives and an `UPDATE_STATUSLINE_TYPES` regeneration path.
Clarify that rate-limit usage percentages can exceed 100.
## Testing
Add a Rust test that checks key type exports in the installed skill and a strict TypeScript fixture covering provider rendering and invalid item IDs, row props, and colors.
GitOrigin-RevId: f615e0b3c2cd3d0d95a75de36ce0a84467ecd5b6
## Why
Status line provider discovery failures were silently ignored, and startup lookup timeouts appeared as unavailable providers.
## What changed
- Show incomplete provider discovery in the warnings viewer, with sanitized server names, bounded summaries, and no raw RPC error details. Preserve the warning across canceled scans and clear it after a successful scan.
- Share a single five-second startup deadline across provider lookup retries and report timed-out lookups as `Status line timed out`.
## Testing
Add coverage for discovery warning rendering and lifecycle, and for a hung lookup retry exhausting the remaining startup deadline. Update the startup timeout expectation.
GitOrigin-RevId: 0403af2ed688c31c175d1b5c47d2cdd4cd355653