@oar-sh/oar 0.9.6 → 0.9.8

package/CHANGELOG.md

@@ -5,6 +5,291 @@ All notable changes to OAR are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.9.8] — 2026-10-04
+
+Highlights: OAR has a logo, an otter, with icons that follow Day and Night
+mode and a start screen that continues the phone's launch screen; a
+*Compacting context…* line shows while a Claude session compacts, and a
+changed auto-compact window now really applies; the one-line installer
+finishes the job and `oar start` brings the relay up without a session;
+scrollbars are easier to grab with a mouse.
+
+### Added
+
+- **The otter logo, matching Day and Night mode.** OAR has a new logo. The
+  start screen and the sign-in box show it on a white tile in Day mode and on
+  a dark tile in Night mode, and only the matching file is loaded. The tab
+  icon, the toolbar colour and the installed app's icon and launch background
+  follow the Theme setting too (Android launchers get a full-bleed icon that
+  fills their shape), and the theme is applied before the first
+  paint, so Day mode no longer starts with a dark screen. On Android the
+  installed app's own launch screen updates when the system refreshes the
+  app, which can take a day.
+- **The installed app starts in one motion.** The start screen continues the
+  phone's launch screen: the otter stands where and as large as the launch
+  screen showed it, then slides up and shrinks while *Connecting to OAR…*
+  fades in below. Without a stored token it travels on into the sign-in box,
+  which fades in around it. Launch screen, start screen and status bar share
+  one colour, so no plate shows around the logo. The app waits for the
+  animation (under a second); a browser tab starts at once as before, and so
+  does an installed app when motion is reduced in the system settings.
+- **A compaction shows while it runs.** When a Claude session starts
+  compacting its context, a *Compacting context…* line appears above the
+  running turn and its bubble says *Compacting the conversation…*. When the
+  compaction ends, the same line becomes *Context compacted · 120k → 40k
+  tokens*; one that ends without a result leaves no line.
+- **`oar start`, and `oar setup --start`.** `oar start` starts the relay of a
+  global install in the background, without a Copilot session tied to it
+  (through the systemd user service when one is installed), and prints the
+  relay URL. `oar setup --start` does the whole job without a question: where
+  a systemd user session exists it writes and enables the service and enables
+  lingering, elsewhere it starts the relay in the background. `oar setup
+  --port <port>` sets the port; a new config otherwise takes the first free
+  port from 3333 on.
+- **The macOS and Linux installer does everything after one confirmation.**
+  `curl -fsSL oar.sh/install | sh` prints what it will do, asks once (`--yes`
+  skips the question), then installs OAR and starts the relay. Without
+  Node.js, or with one older than 22.13, it downloads Node.js 24 from
+  nodejs.org into `~/.oar/runtime/node` for OAR alone. Nothing needs root.
+
+### Changed
+
+- **Scrollbars are easier to grab with a mouse.** A scrollbar doubles its
+  width while the pointer is on it and goes back to thin 2.5 seconds after
+  the pointer left. The space for the wide scrollbar is always kept, so
+  nothing on the page moves when it grows. Touch devices are unchanged.
+
+- **The auto-compact window slider saves when the 🧠 modal closes.** Moving
+  it only changes the label and the notes beneath it; the value is saved
+  when the modal is closed, and setting it back sends nothing. A notice
+  warns when the new window is below what the conversation already uses
+  (*The conversation will be compacted on the next message.*), and another
+  says when the change takes effect: after the current turn, when
+  background work has finished, or on the next message. The modal's
+  headline reads `60.9k used · compaction window 100.0k · model limit 1M`.
+
+### Fixed
+
+- **`oar start` no longer mistakes a leftover lock or another program for a
+  running relay.** It asks the relay itself: only an answer to OAR's own status
+  call with the configured token counts as running. A lock left behind by a
+  relay that did not stop cleanly is removed and the relay is started; if
+  another program holds the port, `oar start` says so and names
+  `oar setup --port`.
+- **A new config no longer picks a port that is in use on Windows.** The
+  free-port check binds the loopback addresses as well as all interfaces and
+  tries a connection, since Windows allows a wildcard bind beside a listener
+  on 127.0.0.1 alone.
+- **The compaction line survives a busy turn.** The live *Compacting context…*
+  / *Context compacted* line used to disappear after two dozen further
+  activity lines until the next reload.
+- **The auto-compact slider is saved when the page closes.** Closing the tab
+  or the app with the context window still open used to drop a moved slider.
+
+- **A "Compacting context…" line no longer stays on a waiting message.** When
+  the session compacted while a message waited behind a turn the agent had
+  opened itself, the line stayed on the waiting message for its whole turn.
+
+- **A new auto-compact window now reaches a running Claude session.** The
+  CLI reads the window only when it starts, so a changed window used to wait
+  until the session restarted for some other reason. The session now
+  restarts once, before the next message, when nothing is running in it
+  (no turn, question, compaction or background work); the reply notes it
+  (*Restarted the session to apply the compaction window (Auto → 100k)*).
+- **The installer no longer fails with `EACCES` on a Node.js from a
+  distribution or NodeSource package.** There npm's global folder needs root,
+  and the installer refuses to run as root, so the install could not succeed.
+  It now installs the package into `~/.oar/npm` and puts the `oar` command
+  into `~/.local/bin`.
+- **Updates land in the install that is running.** `oar update` and the
+  **Update** button ran whatever `npm` was first on `PATH` into npm's default
+  global folder. They now run the npm of the Node.js that runs the relay, into
+  the folder the package is installed in, so an install made with `--prefix`,
+  a relay service without `npm` on its `PATH`, and a version manager pointing
+  at another Node.js all update correctly.
+- **Installs and updates work on npm 12.** npm 12 runs no install script it
+  was not told to allow, so `better-sqlite3`, `koffi` and `cloudflared` were
+  installed without their binaries and the relay did not start. `oar update`,
+  the **Update** button and both installers now pass `--allow-scripts` for
+  these three; for a manual `npm install -g` the README gives the flag.
+- **The systemd user service finds your tools.** The unit `oar setup` writes
+  now carries the `PATH` of the shell that ran it, plus `~/.local/bin` and the
+  directory of its Node.js. A user service otherwise starts with systemd's
+  bare `PATH`, on which the relay's sessions found neither the provider CLIs
+  nor, with a version manager, `node` itself.
+
+## [0.9.7] — 2026-10-03
+
+Highlights: Claude Cloud chats (experimental, off by default) run Claude Code
+in a sandbox at Anthropic on a GitHub repository; conversations can be
+archived and have a context menu in the list; agents can start and use
+sessions on the relay they run on; commits of Claude sessions say "Open
+Agent Relay"; Check Usage opens at once.
+
+### Added
+
+- **Archive conversations, and a context menu in the list.** Every
+  conversation row has an **Archive** button beside Delete (and the chat's
+  `⋯` menu an **Archive conversation** entry). An archived chat leaves the
+  list and its session worker is stopped; the 🗄 toggle at the top of the
+  sidebar shows the archived chats, each with **Unarchive**. A Claude Cloud
+  chat's cloud session is archived and unarchived at Anthropic with it. A
+  message into an archived chat (an agent's, say) brings it back by itself;
+  the composer of an archived chat says so instead of sending. A right-click
+  on a row — a long press on a phone — opens a menu with Open, Edit title,
+  Stop turn, Kill session, Archive/Unarchive and Delete.
+- **Commits made from OAR say so.** Claude sessions now end their commit
+  messages with `Co-authored-by: Open Agent Relay (<model>) <no-reply@oar.sh>`
+  — the model's name in the parentheses, e.g. `Claude Fable 5.1` — and pull
+  request bodies with `🤖 Generated with [Open Agent Relay](https://oar.sh)`,
+  instead of Claude Code's own lines. Settings → Providers → Claude has the
+  choice: **OAR** (the default), **vanilla** (Claude Code's own attribution)
+  or **off** (none); a repo folder can override it from the 🧠 context modal
+  of any of its Claude sessions. A change reaches running sessions with their
+  next message. Claude Cloud chats follow the same setting: the sandbox gets
+  it with the first message and again when it changes, and in OAR mode the
+  `Claude-Session` link is left out of the commit as well. Other providers
+  are not touched: their tools have no such setting.
+- **Claude Cloud (experimental): chats that run in a sandbox at Anthropic.**
+  A new provider, off by default. A Claude Cloud chat runs Claude Code in
+  Anthropic's cloud, on its own clone of a GitHub repository instead of on
+  the relay host. It is billed to the Claude account the host's Claude CLI
+  is logged in to, and its results come back as branches the agent pushes.
+  Switch it on in Settings → Providers → Claude Cloud and choose the cloud
+  environment and a default model there; it needs the Claude CLI logged in
+  with a claude.ai account on the relay host, GitHub connected to that
+  account, and the Claude GitHub app allowed on the repository.
+  - **New Chat** fills **Repository** and **Branch** from the folder you
+    pick, offers the repositories the Claude GitHub app can reach (the ones
+    used here before first) and the branches of the picked repository, lets
+    you type both, and warns about commits that are not pushed, changes
+    that are not committed and a repository the app cannot reach.
+  - **In the chat** the reply streams in live, the agent's questions and
+    permission prompts arrive as cards, **Stop** interrupts the turn, images
+    can be attached, and the model can be changed between turns. A line
+    above the composer links the session on claude.ai and every branch the
+    agent pushed to its comparison on GitHub, and shows the cost so far.
+  - **Turns** survive a restart of the worker or the relay without sending
+    your message twice. A turn stays open while the agent's background work
+    runs, a turn the session starts by itself (after long background work,
+    or from a message sent on claude.ai) appears as a reply of its own, and
+    a turn refused at the usage limit is paused until the reset like a
+    local Claude turn.
+  - **Commits** follow the relay's attribution setting (see above), and
+    deleting or archiving the chat archives the cloud session.
+  - **Not there:** relay modes, a reasoning effort, steering during a turn,
+    files other than images and anything else from the relay host, and the
+    relay's tools and previews inside the sandbox.
+  - **Before you switch it on:** the provider uses the Claude CLI's stored
+    login to call the Anthropic API endpoints the CLI itself uses. These
+    are not a documented public API and may change. OAR only reads the
+    token: it never stores or logs it and sends it nowhere but to
+    Anthropic; when it has run out, OAR lets the CLI refresh it. While the
+    provider is off the relay fetches nothing with that login, except for
+    cloud chats you created before. See "Claude Cloud" in the README.
+    `scripts/claude-cloud-live-check.mjs` checks a running relay's Claude
+    Cloud end to end.
+- **Check Usage: live Claude limits and a Claude Cloud card.** With Claude
+  Cloud switched on, the Claude card reads the 5-hour, weekly and per-model
+  limits live from the account when you open the modal, instead of showing
+  the reading of your last Claude turn, and a limit that is getting close
+  carries Anthropic's warning. The card also shows which product the week
+  went to (Claude Code, chats and the others) and the organisation's prepaid
+  credits. The new Claude Cloud card shows the account's cloud credit (used,
+  left, and when it expires) and what the cloud chats on this relay have
+  cost as Anthropic reports it, in total and for the chat you opened the
+  modal from; a credit that is offered but not yet claimed is mentioned with
+  a link. The limit-reset vouchers (full reset, 5-hour reset) stay
+  claude.ai-only: no endpoint the CLI's login reaches carries them, so the
+  card links to the usage page instead. With Claude Cloud off, the Claude
+  card is what it was.
+- **Agent sessions: an agent can hand parts of its task to other sessions on
+  the same relay.** The `remote_relay` tool now also works on the relay the
+  agent runs on: it starts sessions there, waits for them and reads their
+  replies, and each one is an ordinary conversation in your list. Off by
+  default; switch it on in Settings → Relays → Agent sessions (**Agents may
+  start and use sessions on this relay**). No relay has to be paired. The
+  first time the agent of a conversation starts a session, a card asks you
+  once for that conversation. At most 4 sessions it started may be at work at
+  the same time, a session that an agent created cannot start sessions
+  itself, and an agent cannot prompt, stop or archive the conversation it
+  runs in. A session can use any provider that is enabled on the relay
+  (image chats excepted); a Claude Cloud chat is started with the new `repo`
+  and `branch` arguments, and an agent on a paired relay can now start a
+  cloud chat here the same way. Sessions an agent starts use this relay's
+  accounts, show **via agent** with the title of the conversation they came
+  from in the sidebar and the header (a click opens it), and are never
+  archived automatically. The new
+  **Longest wait per tool call** slider in the same place sets how long one
+  call may wait for a reply: 10 minutes as before, up to 60; it applies to
+  waits on paired relays too. See "Agent sessions" in the README.
+
+### Changed
+
+- **Check Usage opens at once.** The modal shows the reading it showed last
+  time immediately and reads only the open tab's provider live (the card says
+  "updating…" meanwhile), instead of fetching every provider and showing a
+  spinner until the slowest answered. A tab you switch to is read live when
+  its reading is older than a minute; **Refresh** reads the open tab only.
+  The relay keeps the last live answer of every provider, so the other cards
+  stay filled (`GET /api/usage?providers=…`).
+- **Windows: the relay no longer stops while it reads the process list.**
+  Before every launch, every kill and every check of a worker that went
+  quiet, the relay reads the list of all processes through PowerShell. It
+  did so synchronously: half a second to a second and a half on an idle
+  machine, several seconds under load, during which the relay answered
+  nothing — under CI load that was enough for the tunnel to report 502 for
+  the whole relay. The list is now read off the relay's thread; callers that
+  ask at the same time share one read, and a read is reused for 1.5 s. A
+  worker that went quiet is checked by its pid first and by the list last.
+  `GET /api/status` → `sessionWorker.processList` shows when the list was
+  last read, how long it took and whether it failed; a read slower than two
+  seconds is logged. A kill or a workspace relaunch that cannot read the
+  list answers 409 with the reason instead of failing with 500 or stopping
+  blind.
+
+### Fixed
+
+- **A reply that names an error code is a reply.** A reply a session
+  worker published was read as a failed turn when its one paragraph led up
+  to "Error code: relay.…" — a short report on a test that had failed with
+  that code, for instance. Workers always send the failure as a record, so
+  their replies are no longer read for one; the page's fix buttons under a
+  failure follow the same rule and no longer appear under a reply that
+  mentions a code in a quotation, a code span, a table or a list.
+- **Two prices in one paragraph were shown as a formula.** In a reply such
+  as `this run cost $4.20, the earlier one $3.80`, everything between the
+  two dollar signs was rendered as maths. A dollar sign now starts a formula
+  only when it is written the way inline maths is: no space after the
+  opening sign, no space before the closing one, and no digit right after
+  it. Prices stay text; `$x^2$` is still maths. A wide inline formula also
+  no longer makes the whole message scroll sideways: it stays inside the
+  bubble and scrolls within itself.
+
+- **Windows: no worker could start once an agent had run a command with an
+  arrow or a bullet in it.** Before every launch the relay reads the list of
+  all processes through PowerShell. Under the console's OEM code page
+  PowerShell wrote characters such as `→` and `•` as control bytes, the list
+  stopped being valid JSON, and every launch on the relay failed: each session
+  you wrote to turned yellow after six tries and stayed so, for every
+  provider, until the relay was restarted. The list is now written as UTF-8, a
+  control byte that still gets through is tolerated, a list the relay cannot
+  read no longer stops a launch, and a session whose launches were exhausted
+  is tried once more every minute instead of waiting for a restart.
+- **A session whose worker cannot be started now says so.** Until now such a
+  session showed a yellow dot and nothing else. The relay now writes one note
+  into the conversation — why the worker could not be started, in one
+  sentence plus the cause — and keeps that same note up to date: it tries
+  again every minute for ten minutes, then stops and the note gets a
+  **Retry** button for once the cause is fixed; when the worker starts, the
+  note says so. Your message stays queued the whole time, and a queued
+  restart of the relay no longer waits for a message the relay has stopped
+  trying to deliver.
+- **The Claude usage card showed extra-usage credits 100 times too high.**
+  Claude reports these amounts in the currency's minor units (cents), and
+  the card showed them as dollars: 12.50 used of a 50.00 limit read as 1250
+  of 5000. The percentage was right.
+
 ## [0.9.6] — 2026-09-29
 
 Highlights: a Claude turn pauses at the usage limit and carries on after the