WOB-120 · Wispr access · 20 October 2026
A Wob job can now read Wispr through its own profile
Chat could already read Wispr, but background jobs could not: every job profile had an empty list of outside connections. The on-demand job wispr-access-check now runs under its own profile, wispr-capture, which lists four Wispr read tools.
list_folders is not on the list. The job named the blocker and handled no item.metadata entries on one search page. More pages exist and were not read.
source transcript characters, exactly, from one finalized recording.
wall time in the traced run. Exit 0 means the job ran and produced its result.
PR 309 (WOB-120) was first installed in the 04:02 EDT window, by run 20261020T080059Z-49296. The 05:31 EDT run 20261020T093017Z-23597 installed f66d4f2 (exit 0, running new code), which holds PR 309 and PR 318 (WOB-121, on-demand, filing only to a configured scratch folder). A later install, 2043813 at 06:56 EDT, is dated in the morning and status pages, which own the current runtime.
The real job entry point and real Wispr sign-in, in scratch config and state. A tracing launcher on PATH forwarded to the real claude binary, but switched its output from json to stream-json and added --verbose and --no-session-persistence. PR 309's evidence body records 252 tests and 77 subtests at final head 8974ab0. The evidence note at 8974ab0 shows ruff, format and pyright passing. LSP inspection ran earlier, at 73cf5bb.
Not proven: an uninstrumented JSON-output run, launchd runs, token refresh over days, an expired grant (401), the Codex route, and real new, revised or debrief filing. The profile is not a universal shell or filesystem sandbox.
Sources: WobOS PR 309 and PR 318; install receipts 20261020T080059Z-49296, 20261020T093017Z-23597 and, later, 20261020T105529Z-27704; PR 309 evidence body (final head 8974ab0); evidence note docs/evidence/wob-120-job-access.md (its header is candidate-era).