@oar-sh/oar 0.9.14 → 0.9.16

package/CHANGELOG.md

@@ -3,6 +3,185 @@
 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.16] — 2026-10-24
+
+Highlights: agents can file the sessions they start into your session
+groups, change another session's model, mode or other settings, watch other
+sessions with fewer wake-ups (digests, quiet hours, exclusions), and
+schedule prompts that survive a relay restart. Agents can ask you a question
+without stopping their work, and the new Inbox lists every open question
+from this relay and its paired relays in one place. A new switch lets the
+agents of a conversation start sessions themselves.
+
+### Added
+
+- **Agents can put a new session into an existing session group.**
+  `remote_relay` create_session takes `group` (a group id, or its name in
+  any case) on this relay or a paired one, and `relay_info` lists the groups
+  there. An unknown group is refused with the groups listed, and nothing is
+  created. The approval card names the group, and the result carries it. A
+  relay too old for this is refused before anything is created. Renaming
+  and rearranging groups stays the owner's. An argument an action does not
+  take is no longer dropped without a word: create_session refuses it, and
+  the other actions list it in `ignored`.
+- **Agents can change another session's settings.** `remote_relay`
+  update_session sets a session's model, reasoning effort, relay mode,
+  auto-compact window, title, group, thinking or working folder for its next
+  turns, on this relay or a paired one, and answers the settings and what
+  changed. An unknown model is refused with the close matches; a group name
+  that does not exist makes a new group, and `none` takes the session out (a
+  group you made is never removed this way: it stays, shown empty in the
+  sidebar for you to rename or dissolve); a new folder
+  restarts the session's CLI there and is refused while it works. Only a
+  session the agent's own conversation started may be changed freely; any
+  other, yours or another agent's, needs your Allow once per conversation and
+  relay. A failed change still lists what it wrote. An open page shows the
+  change at once.
+- **"Agents in this conversation may start sessions."** A switch in the 🧠
+  settings of a session an agent started lets its agents start sessions
+  themselves, past the one-level rule; the limit of four at work and your
+  first Allow still apply. Only you can set it: agents and paired relays are
+  refused.
+- **Fewer wake-ups for watching agents.** A `remote_relay` subscription takes
+  `digest_minutes` (its events come as one message every N minutes),
+  `quiet_hours` (a daily window in a time zone, crossing midnight and the
+  clock changes included, whose events come as one message when it ends) and
+  `exclude` (sessions a subscription to all leaves out). Questions and errors
+  still come at once, held events survive a restart, and the hourly limit
+  stays on top. A turn the watcher prompted itself and whose finished reply it
+  waited for no longer wakes it a second time with turn_end.
+  `list_subscriptions` shows how many events each subscription holds and when
+  they are due, and the watching chip shows a small digest or quiet-hours hint.
+- **Scheduled prompts that survive a restart.** `remote_relay` schedule
+  queues a prompt at a time (`at`) or every N minutes (`every_minutes`, 5 to
+  10080), into the agent's own conversation or, with the user's approval in
+  ask and plan mode, another session on this relay. The relay keeps it in its
+  database, so a nightly review or a sweep no longer has to be set up again
+  after a deploy. A time missed while the relay was down fires once when it is
+  back, and a repeat waits while the one before is still queued. The message
+  says it is automated and approves nothing. `list_schedules` and `unschedule`
+  manage them, archiving a session ends its schedules, and a conversation
+  holds at most 20. The sidebar marks a scheduled session, and its header
+  lists the schedules with a Cancel button each.
+- **Questions that don't block, and the Inbox.** `remote_relay` ask puts a
+  question for you into the agent's session (up to eight options, a
+  recommendation, a folded detail, and urgency `now` for a push) and returns
+  at once, so the agent goes on with what does not depend on it. Your answer
+  or dismissal reaches it as a relay event, question_answered, without a
+  subscription, and does not count as your message for the agents' loop
+  guard. A lead can ask on behalf of another session, on this relay or a
+  paired one (kept where that session lives); `list_questions` and `withdraw`
+  manage them, and `read_session` lists them with their kind. The new
+  **Inbox** in the sidebar, with its count, lists every pending question
+  across this relay and the paired relays that answer, grouped by relay,
+  with a filter for your sessions or the agents', and what you answered in
+  the last day under a divider. An ask is answered there or in its session,
+  also one on a paired relay; a paired relay's cards open there, and the
+  pairing never carries an answer to a card. Agent text shows as plain text,
+  and on a phone the Inbox is one column with full-width buttons.
+
+### Fixed
+
+- **The agents' loop guard no longer counts the relay's own messages as the
+  user's.** A relay event, the usage-limit follow-up or the note after a
+  restart reset the count of prompts an agent may send to other agents
+  before the user is asked, so two agents that watched each other could go
+  on without the user. Only a message the user wrote resets it now.
+
+## [0.9.15] — 2026-10-22
+
+Highlights: `oar setup` asks how the relay starts on Windows, at sign-in or
+at boot before anyone signs in, and `oar autostart` switches between them
+later. `oar uninstall` takes OAR off the machine and keeps your data unless
+you ask for `--purge`. A declined administrator prompt changes nothing, boot
+tasks work in profile folders with spaces or non-ASCII names, and a
+hand-made task, or one only an administrator can read, is never deleted
+without a copy. The package is smaller.
+
+### Upgrade notes
+
+- **From 0.9.14 with a hand-made autostart task:** switching to boot mode
+  in 0.9.14 could delete an existing task of the same name (`oar-relay` or
+  the pre-rebrand name) without a copy. 0.9.15 keeps such a task and asks
+  for `--replace`, which saves a copy first.
+
+### Added
+
+- **`oar setup` asks how the relay starts** on Windows: at sign-in, at boot
+  (before anyone signs in; one administrator prompt) or not at all, with the
+  current mode as the default. `--autostart signin|boot|off` answers it
+  without a question.
+- **`oar autostart signin|boot|off|status`.** Switching to or from boot mode
+  asks for an administrator once, only for the schtasks call; sign-in mode
+  needs none. A declined prompt changes nothing. `status` lists each entry,
+  whether OAR generated it, and which other OAR install a stale one starts.
+  `--replace` replaces hand-made entries with generated ones, keeping a copy
+  of each (`<name>.bak`: a launcher's beside it, a task's exported XML and a
+  Startup entry's in the OAR folder); nothing else ever does. On Linux it is
+  the systemd user service (`oar service`); elsewhere it says it is not
+  supported.
+- **`oar uninstall [--purge]`** stops the relay, takes out the autostart
+  entries OAR generated and the Copilot extension wrapper OAR wrote for this
+  install (a changed one, or one of another install, stays and is named),
+  and has npm remove the package once `oar` has ended. **The data stays** (config,
+  database, uploads, logs in the state root), and the command says where.
+  `--purge` deletes the state root after you type `delete`; a data folder
+  outside it, one in a git checkout, and `rescued-package-data` are each
+  deleted only after a question of their own; a drive root, the home folder
+  or a folder above it, a system folder and a folder without OAR's config or
+  database in it are refused, whatever is typed. A relay that holds its lock
+  without answering (bringing over a database) stops the command before it
+  deletes anything. Programs that still run from the package (session
+  workers) are named: npm leaves the files they hold in a hidden `.oar-*`
+  folder, which the log names. A step
+  that fails stops the command, which says what is done and what is left.
+
+### Changed
+
+- The two developer READMEs (`server/README.md` with the HTTP API, and the
+  web-relay extension's) are no longer in the npm package; they are on
+  [GitHub](https://github.com/oar-sh/oar).
+
+### Fixed
+
+- **A hand-made autostart entry is never deleted or written over.** Leaving
+  boot mode deleted a boot task or launcher edited by hand, and *Off* also
+  a task OAR did not make; switching to sign-in replaced an edited Startup
+  entry. Only entries exactly as an OAR version generated them are changed
+  now, in the web UI as in `oar autostart`: a hand-made entry that would stay
+  beside the new mode, or be replaced by it, stops the switch with the same
+  message. Picking *At system startup* no longer replaces a hand-edited
+  launcher or a task someone else made, the pre-rebrand one included. A boot
+  task is OAR's own only while it is exactly the one OAR registers: the
+  account, the run level, one action, one boot trigger and its settings.
+- **Boot mode switches on and off with a space, an apostrophe or non-ASCII
+  characters in the profile path.** The elevated step was a script file
+  passed unquoted, and read in the wrong encoding; it now travels as an
+  encoded command with every path quoted. A failed switch is no longer
+  reported as a declined prompt: it puts back the tasks it deleted from their
+  copies and keeps the copies, and a declined one leaves no file behind.
+  Windows PowerShell can report a declined prompt with an error that does not
+  stop it, or with no process at all; that read as confirmed, so leaving boot
+  mode deleted the launcher but kept the task, and switching it on removed
+  the sign-in entry without registering the task. Both now count as declined.
+  Leaving boot mode in the web UI switches the sign-in entry only after the
+  prompt was confirmed. Leaving boot mode removes the task XML and the record of
+  the sweep too, and the web UI names a Startup entry OAR did not make.
+- **A boot task with non-ASCII characters in its paths reads right.**
+  schtasks writes its XML in the console's code page, so a profile path like
+  `C:\Users\Jürgen` came back garbled and OAR took its own task for a
+  hand-made one: switching boot on reported a failure and deleted the new
+  launcher, and *Off* refused to remove the task. Such a task is now read
+  again through PowerShell in UTF-8. A task that still cannot be read is
+  never taken as missing, removed, put back or someone else's, and never
+  deleted without a copy: nothing is changed while it cannot be read, and
+  after a confirmed prompt OAR says it could not check, and undoes nothing.
+- **A boot task only an administrator can read is never deleted.** One that
+  stores another account's password answers "Access is denied" to OAR; that
+  read as no task, so `oar autostart boot` deleted it without a copy. Any
+  failed read of a task that is there now counts as unreadable: status says
+  so, and OAR changes nothing, `--replace` included.
+
 ## [0.9.14] — 2026-10-21
 
 Highlights: a relay started by Windows autostart, or by a plain

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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-mobile.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/cfmail-mobile.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-mobile.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/cfmail-mobile.png?v=0.9.16" 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-agents.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/cfmail-agents.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-agents.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/cfmail-agents.png?v=0.9.16" 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-question.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/cfmail-question.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-question.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/cfmail-question.png?v=0.9.16" 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pingcf-thoughts.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/pingcf-thoughts.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pingcf-thoughts.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/pingcf-thoughts.png?v=0.9.16" 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-watching.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/pagewright-watching.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-watching.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/pagewright-watching.png?v=0.9.16" 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-steering.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/cfmail-steering.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/cfmail-steering.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/cfmail-steering.png?v=0.9.16" 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/usage-copilot-compact.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/usage-copilot-compact.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/usage-copilot-compact.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/usage-copilot-compact.png?v=0.9.16" 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>
@@ -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.14](CHANGELOG.md#0914--2026-10-21) 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.16](CHANGELOG.md#0916--2026-10-24) 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.14"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-cross-relay.light.png?v=0.9.14"><img src="https://oar.sh/assets/shots/pagewright-cross-relay.png?v=0.9.14" 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.16"><picture><source media="(prefers-color-scheme: light)" srcset="https://oar.sh/assets/shots/pagewright-cross-relay.light.png?v=0.9.16"><img src="https://oar.sh/assets/shots/pagewright-cross-relay.png?v=0.9.16" 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).