@oar-sh/oar 0.9.11 → 0.9.13

package/CHANGELOG.md

@@ -3,6 +3,338 @@
 All notable changes to OAR are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow semver.
 
+## [0.9.13] — 2026-10-20
+
+Highlights: a queued relay restart now shows every page what it waits for,
+which messages it holds and which background tasks keep running, and after a
+time you set it asks instead of waiting forever; it never restarts by itself
+while turns run, and can tell the sessions a restart cut off to carry on
+(opt-in). The task console survives a relay restart, marks where a `| tail`
+holds output back, keeps the task's row in view, and counts a test run over
+its whole log. A message
+sent without a model keeps the conversation's model, effort and mode,
+`remote_relay` refuses a model the provider does not list, watching agents
+are no longer woken by every finished shell command, workers reconnect after
+a hung restart, and the unit suite passes on Windows again.
+
+### Upgrade notes
+
+- Migration 0018 (the table `background_task_rows`) runs by itself on the
+  first start. Rows the runtime before this update held in memory are lost
+  one last time at the restart into it. The Node.js requirement is unchanged
+  (22.13 or newer).
+- New settings in **Settings › General**: **Ask after a queued relay restart
+  has waited** (30 minutes by default) and **After a relay restart, tell
+  interrupted sessions to carry on** (off by default); a new push event,
+  **Queued relay restart waited its maximum time** (Settings › Notifications),
+  is on by default.
+- **Watching agents:** a subscription that named no events now leaves out
+  successful shell commands (sub-agent ends and failures still wake it); one
+  that named its events keeps them. Name `task_finished` to get every task end.
+- **Scripts that post `/api/message` without a model** to an existing
+  conversation now get the conversation's own model, effort and mode, or a
+  `409 CONVERSATION_MODEL_UNAVAILABLE` when that model left the catalog,
+  instead of the relay's first model.
+- The npm package guard allows 7.75 MiB unpacked and 520 entries (was 7.5
+  MiB and 510); the restart queue, the stored task rows and the restart note
+  grew the server and the app to about 7.57 MiB and 514 entries.
+
+### Added
+
+- **After a relay restart, tell interrupted sessions to carry on** (Settings
+  › General, off by default, a setting of the relay). A turn a restart cut
+  off for good (the agent had already taken the message, so it cannot run
+  again) used to stop without the agent ever hearing of it. With the setting
+  on, its session gets one compact **relay** note once the relay is back:
+  when the relay restarted, and to check what it was doing and carry on.
+  The user's message is never sent again, and nothing goes to idle sessions,
+  to turns the relay requeues (they run again by themselves), to archived
+  conversations or while a usage-limit pause holds the session; a message
+  queued meanwhile goes first.
+- **The task console marks where a `| tail` holds the output back.** A
+  command piped into `tail` (`npm test 2>&1 | tail -40`) writes nothing
+  until it ends, so its console looked stuck. When the task's command line
+  shows such a pipe (`tail -f` and `head` pass lines on and are left
+  alone), the console marks where the output stops, with a hint to log to a
+  file instead, until more output comes or the task ends; the row's quiet
+  hint says the same on hover. The Claude, Copilot and Grok workers now report a
+  shell task's command line on its row (scrubbed of credentials by the relay
+  and cut at 2,000 characters; `read_session` passes it on).
+- **Load earlier in the console's header.** It sat only above the first
+  line, out of reach while following the end of a long log; the header now
+  has it too whenever there is earlier output.
+
+- **A queued relay restart shows what it waits for, and asks instead of
+  waiting forever.** **🌄 Restart web relay** first lists the sessions with
+  a running turn it would wait for, the messages it would hold, and the
+  sessions with background tasks (commands, monitors, sub-agents), each with
+  whether it keeps running; **Restart when idle** queues the restart,
+  **Restart now** does not wait. While a restart is queued every page shows a
+  banner: *Relay restart queued — waiting for N sessions*, the sessions as
+  links, how long it has waited, that new messages are held until then, the
+  background tasks, and **Restart now** (it asks first and names the
+  sessions it does not wait for) and **Cancel restart**. A new setting,
+  **Ask after a queued relay restart has waited** (Settings › General,
+  30 minutes by default, 5 minutes to 4 hours or no limit), bounds the wait:
+  after it the banner asks *restart now, keep waiting or cancel?* and a push
+  notification (a new event, on by default) asks the same. It never
+  restarts while the turns run, and still restarts as soon as they end;
+  **Keep waiting** waits another period.
+  `POST /api/relay/shutdown` answers with the same picture (`waitingFor`,
+  `held`, `backgroundTasks` with `survives`), so an agent that requests a
+  restart can tell the user, and takes `immediate: true`; `GET
+  /api/relay/shutdown` and `POST /api/relay/shutdown/keep-waiting` are new.
+
+### Changed
+
+- **The open console leaves the task's row in view.** On a screen wider
+  than a phone the console now ends above the task's row in the composer
+  panel, so the row's ✓/✘ chip, clock and **Stop** stay visible and live
+  beside it; on a phone it stays full-screen, with the same chip in its
+  header.
+- **One wording for a task without output.** The row's hover title said
+  "output not available for this provider" and the console "Output is not
+  available for this provider."; both now use the sentence, from the same
+  text the relay answers with.
+- **A watching agent is no longer woken for every shell command that ended
+  well.** A relay event subscription that names no `events` now gets
+  `subagent_finished` instead of `task_finished`: a background sub-agent that
+  finished still wakes the watcher, and so does any task that failed or
+  exited non-zero (`task_failed`), but a shell command that ended well does
+  not. A busy worker ends one every minute or so, and each was a turn of the
+  watcher on its whole context (35 during one 20-minute wait were seen).
+  Name `task_finished` in `events` to get every task end, as before.
+  Existing subscriptions that named no events switch to the new default by
+  themselves; those that named their events keep them. A paired relay on an
+  older OAR applies its own default and refuses `subagent_finished` by name.
+
+### Fixed
+
+- **A message sent without a model keeps the conversation's model and
+  effort.** A message to an existing Copilot conversation that named no model
+  (sent by a script or an agent, not by the composer) ran on the first model
+  of the catalog with effort `none`, which some models refuse, and then saved
+  that model and effort as the conversation's own, so the composer showed
+  them from then on. Such a message now runs on the conversation's model and
+  effort, and saves nothing it did not name. If the conversation's model has
+  left the catalog, the send is refused with a message saying so instead of
+  switching to another model. OpenAI, Claude, Cursor and Grok conversations
+  keep their effort the same way, and so does the follow-up of a plan
+  board's action. A message that names no mode runs in the conversation's
+  mode instead of agent mode, and no longer switches a plan-mode
+  conversation to agent. A message whose turn failed can be sent again at
+  once: it no longer counts as a duplicate of itself.
+- **Test counts of a long run no longer drop out.** The relay counted a
+  test run from the last 64 KB of its output only, so a live run that wrote
+  more lost its runner's first line: the chip disappeared or undercounted.
+  A run still going is now counted over its whole log, read on as it grows
+  (and read again in bounded steps after a relay restart); the closing
+  summary still decides once it is there.
+- **Credentials in background-task rows are blanked.** A task's
+  description, summary and last tool call went to the pages, `read_session`
+  and the stored console rows as the worker sent them, and a Grok terminal's
+  (or a Copilot shell's) description is its command line. The relay now
+  scrubs them like the console output. The scrubber also catches `curl -u
+  name:password` (also attached), `--password`/`--token`/`--secret`
+  values, `mysql -p…`, `docker login -p`, `sshpass -p`, `redis-cli -a`,
+  `aws_secret_access_key` in a file or `aws configure set`, Slack webhook
+  paths, `?key=`/`&sig=`/`&token=` query values and an `Authorization`
+  header in any case and with any scheme word, and leaves a reference such
+  as `$(cat ~/.token)` or `$API_TOKEN` alone.
+- **Inverse text in the task console.** vitest's RUN, PASS and FAIL badges
+  (SGR 7) showed as plain words; inverse text now swaps its colours, so
+  they show filled.
+- **The task console survives a relay restart.** Its rows lived in the
+  relay's memory: after a restart a running command came back to the panel
+  once its worker reported, but the dimmed rows of commands that had
+  finished within the hour were gone, and a console open at the time said
+  the output was no longer available. The rows are now kept in the database
+  (migration 0018): finished rows come back with their ✓ or ✘ for the rest
+  of their hour, and a running command's console reads its output at once.
+  Such a command is shown as running again only when its worker says so
+  (until then its console says it waits for the worker, without **Stop**);
+  one whose worker did not survive the restart is marked finished with an
+  unknown result (a neutral ? instead of ✓ or ✘) after about a minute and a
+  half, its output still readable.
+- **A scroll right after older messages load is no longer undone.** The page
+  put the reader back where they were when the older page arrived, a frame
+  later: scrolling in that frame (up again after the jump-to-bottom button,
+  for instance) was reverted, and could leave you at the end, following new
+  rows you meant to read later.
+- **The jump-to-bottom badge counts a message that arrives just as you scroll
+  up.** One that landed before the page had noted the scroll, a frame and on
+  a busy page up to a tenth of a second, was taken as already seen.
+- **The background-task panel no longer shrinks back for a moment.** While
+  the agent works the page re-reads the conversation, and an answer read
+  before the panel grew put the smaller set of tasks back until the next
+  read. The panel jumped, and a reader following the newest messages could be
+  left above them.
+- **A worker reconnects after a relay restart even when its connect hangs.**
+  A worker's link to the relay was retried only once the socket reported an
+  error or a close. A connect that never finished, a socket the relay
+  accepted but never greeted, or a close that never completed while the
+  relay hung in its shutdown left the worker without a connection and
+  without a next attempt, and messages to its session stayed queued; the
+  relay's replacement of such a worker does not step in while the session
+  is working. The link now gives up a socket that has not completed its
+  handshake within 15 seconds, does not wait for a close after the relay
+  says it is shutting down, and retries a socket that fails to construct.
+  There is always exactly one next attempt, with the usual backoff of up to
+  8 seconds, which now starts over only after a completed handshake. Failed
+  attempts log one line each in the worker log, at most one a minute after
+  the first three.
+- **`remote_relay` refuses a model the provider does not list.**
+  `create_session` passed any model id on, so a Copilot id written with a
+  hyphen ("gpt-5-4" for "gpt-5.4") created a session on another model, which
+  every later `send` with that id failed to reach. A model in
+  `create_session` or `send` is now checked against the list New Chat offers
+  for the provider on the target relay, before any approval card: an unknown
+  one is refused with the close matches and the valid ids ("Unknown model
+  'gpt-5-4' for Copilot on relay …; did you mean 'gpt-5.4'?"), and nothing is created
+  or sent. Claude also takes `opus`, `sonnet` and `haiku` (the newest listed
+  model of that name), and a Copilot id with its effort (`gpt-5.4-high`) runs
+  as that model with that effort. When the relay has no list for the provider yet, the
+  model goes on unchecked and the answer says so. A relay also refuses an
+  unknown Copilot model when another relay's agent starts a session on it.
+- **A preview's websocket is dropped when the browser hangs up before the dev
+  server answers.** A browser that closed its connection with a plain FIN
+  while the upgrade was still waiting on the dev server left both sides
+  open, even when a reset followed: the request
+  to the dev server stayed pending, and the preview lane could not stop
+  until the dev server answered. Both sides are now dropped, and stopping
+  the lane also drops upgrades still waiting on the dev server.
+- **The unit test suite passes and finishes on Windows again.** A preview
+  test waited forever for a websocket hang-up (fixed in the product, above),
+  and several tests expected bare program names or Unix paths where Windows
+  resolves the full path of its own tools; two unlocks recorded in the same
+  millisecond are now listed in the order they were recorded.
+
+## [0.9.12] — 2026-10-18
+
+Highlights: a background command or monitor in the task panel opens a
+console with its output, live, in colour and with secrets blanked, paging
+back through the whole log and with its own **Stop**. Task rows say when a
+task has gone quiet ("no output for 12 min", amber after a time you set in
+Settings) and show a **✓ 412 ✘ 2** chip when the output is a test run;
+sub-agent rows count their steps, and agents read a task's output on a
+paired relay with `remote_relay` `read_task_output`. Long conversations open
+and page back fast, and switching away and back, or reloading, returns to
+the message you were reading, older pages included; new messages wait below
+a place far up the history instead of skipping the ones in between.
+
+### Upgrade notes
+
+- Migration 0017 (two indexes for the history of long conversations) runs by
+  itself on the first start. The Node.js requirement is unchanged (22.13 or
+  newer), and no setting or config key needs changing.
+- Two new settings in **Settings › General**: **Mark a background task as
+  quiet after** (10 minutes by default, for the relay) and **Messages kept
+  per conversation for switching back** (200 by default, per browser).
+- **Claude background commands may run for 2 hours** before Claude Code
+  stops them, and up to 8 hours when Claude asks; **Settings › Providers ›
+  Claude** sets the limit. OAR now sets `BASH_DEFAULT_TIMEOUT_MS`, `BASH_MAX_TIMEOUT_MS` and
+  `CLAUDE_CODE_AUTO_BACKGROUND_TIMEOUT_MS` for the Claude sessions it starts,
+  so values of these in the relay's environment no longer apply. Commands
+  that start with `sleep`, and sub-agents' commands, are not moved to the
+  background after 2 minutes and may block a turn up to the limit.
+
+### Added
+
+- **Click a background command to watch its output.** A backgrounded shell
+  command or monitor in the composer's task panel opens a console: the last
+  2,000 lines, following live, with **Load earlier** paging back through the
+  whole log (about 5 MB at most). Progress-bar redraws collapse to their last
+  state, repeated lines fold into one with ×N, colours are kept and other
+  control codes dropped, secrets are blanked, and the console has its own
+  **Stop**. A finished command keeps a dimmed ✓/✘ row for an hour so a failed
+  run can still be read. Claude reads the file its CLI writes for the command,
+  Copilot a detached shell's log or an attached shell's recent output, and
+  Grok now lists its terminals as tasks. A session started before this
+  release names no output file; its console says so and that a restart of
+  the session helps.
+- **Task rows say when a task has gone quiet** ("no output for 12 min", amber
+  after **Settings › General › Mark a background task as quiet after**, 10
+  minutes by default) and show a **✓ 412 ✘ 2** chip when the output is a
+  vitest, Playwright, node:test, jest, pytest or turbo run (also through
+  pnpm); the console header's chip jumps to the first failure, and a run
+  that ends shows its final counts within a moment.
+- **Sub-agent rows in the task panel show their step count** ("22 steps"), as
+  the rows in the reply already did.
+- **Settings › Providers › Claude › Claude background command limit** (30
+  minutes to 8 hours, 2 hours by default) sets how long a command Claude runs
+  in the background may take before Claude Code stops it, when Claude gives it
+  no timeout of its own; Claude may still ask for up to 8 hours for one
+  command. A foreground command moves to the background after 2 minutes, so
+  the turn goes on while it runs. Claude is also told to write the output of
+  long runs to a log file instead of piping it into `tail`, and to start runs
+  that must survive a session restart with `nohup`. A change applies to Claude
+  sessions started afterwards; Claude Cloud is not affected.
+- **`remote_relay` action `read_task_output`** gives agents the same tail,
+  quiet time and counts of a task on a relay they may read; `read_session`
+  lists the task ids with that health.
+
+### Changed
+
+- **Long conversations open and scroll back fast.** A history page used to
+  load and prepare every message of the conversation, so a chat with a few
+  thousand messages took about two seconds per page and per live refresh. The
+  relay now reads only the requested page from the database (migration 0017
+  adds the indexes for it), so a page loads in well under a tenth of a second
+  however long the conversation is.
+- Switching back to a conversation already viewed in this tab draws it at
+  once from what the page kept of it; the relay's fresh answer is merged into
+  it when it arrives.
+- **Settings › General › Messages kept per conversation for switching back**
+  (200 by default, 100 to 1,000 or no limit, saved in this browser) sets how
+  many loaded messages each of the last eight conversations keeps.
+- **The conversation list shows activity by the title's colour.** The three
+  animated dots after a working session's title are gone: a ready session
+  that runs a turn or background work keeps the bright green title, an idle
+  one turns a darker green (a muted green in the light theme), and the chat
+  header follows the same rule. Question, error, offline and archived titles
+  keep their colours.
+- The npm package guard allows 7.5 MiB unpacked and 510 entries (was 7.25
+  MiB and 490); the task console, the transcript's handling of new
+  messages below a place far up the history, the Copilot task report and the
+  Claude background command limit grew the server and the app to about 7.37
+  MiB and 505 entries.
+
+### Fixed
+
+- **Copilot background tasks report how they ended.** Finished shells and
+  sub-agents of Copilot's SDK engine showed the status *unknown* and no exit
+  code, in the task data agents read and wherever the end is shown. The
+  worker now reports completed, failed or cancelled, a shell's exit code, and
+  a sub-agent's result (or its error) as its summary; a passing status line
+  such as *Thinking…* is no longer kept as the final summary.
+- **Cancel on a usage-limit pause removes the relay's held follow-up from the
+  open conversation at once.** The *Automatic message from OAR* row was
+  deleted on the relay but stayed on the page, and in what the page kept for
+  switching back, until a reload. A row deleted while you were elsewhere
+  leaves too, also when it was the conversation's newest.
+
+- **Switching away from a long conversation and back keeps your place.** After
+  loading older messages and scrolling back into them, a switch to another
+  conversation and back lost the reading position: with more than 100 messages
+  loaded the oldest were dropped, and messages written meanwhile moved the view
+  by as many rows. The page now remembers the message you were reading and
+  keeps the loaded messages, so you come back to the same message at the same
+  place, older pages included; after a reload it opens at that message too.
+- **New messages no longer skip the ones in between while you read far up.**
+  Opened at a pin, a search result or the place you were reading after a
+  reload, a conversation shows the messages around it. A message or reply that
+  arrived then was put right under them, and the messages between were never
+  loaded when you scrolled down, only the jump-to-bottom button brought them.
+  Now new messages wait: the button counts them, and scrolling down loads
+  every message in between, in order, before them. A reply still being
+  written shows once you are there. A message you send from there takes you
+  to the end, where it, its reply and everything in between show.
+- **Images that load late no longer push the message you are reading down.**
+  In a browser without scroll anchoring (Safari, for one), pictures above
+  your place that arrived after a switch back, a reload or an older page moved
+  the text by their height. The transcript now holds your place while they
+  load, and lets go as soon as you scroll.
+
 ## [0.9.11] — 2026-10-17
 
 Highlights: sessions an agent starts now sit in a group under the session

package/README.md

@@ -45,29 +45,29 @@ flowchart LR
 <table>
 <tr>
 <td width="42%" rowspan="4" valign="top">
-<a href="https://oar.sh/assets/shots/cfmail-mobile.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-mobile.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/cfmail-mobile.png?v=0.9.11" alt="OAR on a phone: a finished agent turn in a conversation, with the composer below"></picture></a>
+<a href="https://oar.sh/assets/shots/cfmail-mobile.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-mobile.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/cfmail-mobile.png?v=0.9.13" alt="OAR on a phone: a finished agent turn in a conversation, with the composer below"></picture></a>
 <br><sub>On a phone: the same conversations, installable as an app.</sub>
 </td>
 <td width="58%" valign="top">
-<a href="https://oar.sh/assets/shots/cfmail-agents.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-agents.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/cfmail-agents.png?v=0.9.11" alt="Background subagents running in parallel in the task panel, each with live token counts, elapsed time, and its own Stop button"></picture></a>
+<a href="https://oar.sh/assets/shots/cfmail-agents.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-agents.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/cfmail-agents.png?v=0.9.13" alt="Background subagents running in parallel in the task panel, each with live token counts, elapsed time, and its own Stop button"></picture></a>
 <br><sub>Agents working in parallel, each with live token counts and its own Stop.</sub>
 </td>
 </tr>
 <tr>
 <td valign="top">
-<a href="https://oar.sh/assets/shots/cfmail-question.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-question.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/cfmail-question.png?v=0.9.11" alt="A question card in the middle of a turn: the agent offers several choices and a free-text reply"></picture></a>
+<a href="https://oar.sh/assets/shots/cfmail-question.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-question.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/cfmail-question.png?v=0.9.13" alt="A question card in the middle of a turn: the agent offers several choices and a free-text reply"></picture></a>
 <br><sub>When the agent needs a decision, it asks, and waits for your answer.</sub>
 </td>
 </tr>
 <tr>
 <td valign="top">
-<a href="https://oar.sh/assets/shots/pingcf-thoughts.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pingcf-thoughts.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/pingcf-thoughts.png?v=0.9.11" alt="An expanded Thoughts block showing the agent's reasoning above its reply"></picture></a>
+<a href="https://oar.sh/assets/shots/pingcf-thoughts.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pingcf-thoughts.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/pingcf-thoughts.png?v=0.9.13" alt="An expanded Thoughts block showing the agent's reasoning above its reply"></picture></a>
 <br><sub>Read the reasoning, not just the answer.</sub>
 </td>
 </tr>
 <tr>
 <td valign="top">
-<a href="https://oar.sh/assets/shots/pagewright-watching.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-watching.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/pagewright-watching.png?v=0.9.11" alt="A session watching two other sessions: a finished reply arrives as a compact relay-event row, the watching 2 sessions list is open with Unsubscribe, and a request to also watch a session on a paired relay waits on an Allow / Deny card"></picture></a>
+<a href="https://oar.sh/assets/shots/pagewright-watching.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-watching.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/pagewright-watching.png?v=0.9.13" alt="A session watching two other sessions: a finished reply arrives as a compact relay-event row, the watching 2 sessions list is open with Unsubscribe, and a request to also watch a session on a paired relay waits on an Allow / Deny card"></picture></a>
 <br><sub>Agents that watch agents: woken by events, approving nothing.</sub>
 </td>
 </tr>
@@ -116,11 +116,11 @@ API keys are entered in **⚙️ Settings** and stay on the relay host. The Clau
 <table>
 <tr>
 <td width="62%" valign="top">
-<a href="https://oar.sh/assets/shots/cfmail-steering.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-steering.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/cfmail-steering.png?v=0.9.11" alt="A running Claude turn with a message steered into it mid-turn, the reply streaming with its tool calls, and the Steer button in the composer"></picture></a>
+<a href="https://oar.sh/assets/shots/cfmail-steering.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-steering.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/cfmail-steering.png?v=0.9.13" alt="A running Claude turn with a message steered into it mid-turn, the reply streaming with its tool calls, and the Steer button in the composer"></picture></a>
 <br><sub>Send a message while the agent works, and it steers the running turn.</sub>
 </td>
 <td width="38%" valign="top">
-<a href="https://oar.sh/assets/shots/usage-copilot-compact.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/usage-copilot-compact.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/usage-copilot-compact.png?v=0.9.11" alt="The GitHub Copilot card in Check Usage: premium requests and plan quota with reset dates, and the cost of the last turn"></picture></a>
+<a href="https://oar.sh/assets/shots/usage-copilot-compact.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/usage-copilot-compact.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/usage-copilot-compact.png?v=0.9.13" alt="The GitHub Copilot card in Check Usage: premium requests and plan quota with reset dates, and the cost of the last turn"></picture></a>
 <br><sub>What each plan has left, in one place.</sub>
 </td>
 </tr>
@@ -129,7 +129,7 @@ API keys are entered in **⚙️ Settings** and stay on the relay host. The Clau
 - **Watch a turn live**: the reply, the agent's thoughts and every tool call appear as they happen, and each sub-agent gets a bubble of its own. **Stop** is always one tap away ([While a turn runs](docs/web-ui.md#while-a-turn-runs)).
 - **Steer or queue**: a message sent during a turn goes into it (Claude, Copilot) or waits behind it ([While a turn runs](docs/web-ui.md#while-a-turn-runs)).
 - **Answer questions**: the agent asks on a card with one-click choices, checkmarks or free text, and waits for you ([Question cards](docs/web-ui.md#question-cards)).
-- **Background work**: a task panel lists the commands and sub-agents that outlive a reply, each with its own **Stop** and its full record ([Background tasks](docs/web-ui.md#background-tasks)).
+- **Background work**: a task panel lists the commands and sub-agents that outlive a reply, each with its own **Stop** and its full record; a command's console shows its output live, says when it has gone quiet and counts a test run's passes and failures ([Background tasks](docs/web-ui.md#background-tasks)).
 - **Choose how the agent works**: `ask`, `plan`, `agent` or `autopilot`, plus model and reasoning effort, per message ([Relay modes](docs/web-ui.md#relay-modes)).
 - **Files and git**: browse the workspace, preview files, review git changes in a diff viewer, and publish a dev server as a preview link ([Files, git, and previews](docs/web-ui.md#files-git-and-previews), [preview servers](docs/preview-servers.md)).
 - **Usage and context**: plan limits and credits of every provider, and what fills the model's context window ([Usage and context](docs/web-ui.md#usage-and-context)).
@@ -137,7 +137,7 @@ API keys are entered in **⚙️ Settings** and stay on the relay host. The Clau
 - **Share** a conversation as a read-only link, hide single messages and the host's paths from it, and see when it was opened ([Sharing](docs/web-ui.md#sharing)).
 - **On your phone**: install OAR as an app and get push notifications ([Notifications and the app](docs/web-ui.md#notifications-and-the-app)).
 
-The full tour is in [Using the web UI](docs/web-ui.md); every setting and config key is in [Settings and configuration](docs/configuration.md). What changed in each release is in the [changelog](CHANGELOG.md), with [0.9.11](CHANGELOG.md#0911--2026-10-17) as the latest.
+The full tour is in [Using the web UI](docs/web-ui.md); every setting and config key is in [Settings and configuration](docs/configuration.md). What changed in each release is in the [changelog](CHANGELOG.md), with [0.9.13](CHANGELOG.md#0913--2026-10-20) as the latest.
 
 ## Remote access
 
@@ -188,7 +188,7 @@ flowchart LR
 
 You stay in charge: per paired relay you decide whether agents may only read, also prompt, or do everything, and in the `ask` and `plan` modes every write asks you first. A subscription only notifies; it approves nothing.
 
-<p><a href="https://oar.sh/assets/shots/pagewright-cross-relay.png?v=0.9.11"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-cross-relay.light.png?v=0.9.11"><img src="https://oar.sh/assets/shots/pagewright-cross-relay.png?v=0.9.11" alt="A session watching two sessions on a paired relay: a reply arrives as a relay-event row, and after a short outage the events the other relay kept arrive as one replayed row" width="720"></picture></a></p>
+<p><a href="https://oar.sh/assets/shots/pagewright-cross-relay.png?v=0.9.13"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-cross-relay.light.png?v=0.9.13"><img src="https://oar.sh/assets/shots/pagewright-cross-relay.png?v=0.9.13" alt="A session watching two sessions on a paired relay: a reply arrives as a relay-event row, and after a short outage the events the other relay kept arrive as one replayed row" width="720"></picture></a></p>
 
 How pairing, permissions and limits work is in [Agents working together](docs/agents-together.md).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oar-sh/oar",
-  "version": "0.9.11",
+  "version": "0.9.13",
   "type": "module",
   "description": "OAR — Open Agent Relay: drive your local coding agents from any browser",
   "license": "MIT",