Biorouter v1.93.2

Biorouter v1.93.2

This patch release replaces v1.93.1. It fixes the in-app update: a download that loses its connection now picks up where it stopped, and Restart & update always either restarts Biorouter or says why it could not. It also carries everything v1.93.1 brought: Claude Code chats that use the context window the way other models do, Crew automatic setup on a shared server, fixed local model retries, and biorouter serve behind HTTPS proxies such as JupyterHub.

Updates

• An update download that loses its connection continues from where it stopped instead of failing. Updating from 1.93.0 to 1.93.1 could end with "Update download failed" and net::ERR_CONNECTION_RESET, and the next attempt came three hours later and started from the beginning.
• When an update cannot be downloaded or installed, the update dialog shows the reason and a Try again button.
• On macOS, Restart & update appears once macOS has finished checking the downloaded update. Until then the dialog says Preparing the update…. Before, a click during that check did nothing visible, and quitting Biorouter by hand then installed the update without reopening it.
• On macOS, Restart & update no longer does nothing after an earlier update check failed. If macOS cannot install the update, for example because Biorouter is running from the Downloads folder or a disk image, the dialog says so.
• If Biorouter cannot close to install an update, it reopens a window and tells you, instead of leaving no windows open.
• A downloaded update is no longer downloaded and prepared again every three hours while it waits to be installed.
• On Windows, the update dialog gives the installer steps for a downloaded installer and no longer offers Open Folder Only, which could leave a broken install if the installer ran while Biorouter was open.

Claude Code and Codex

• A Claude Code chat no longer fills its context window about twice as fast as the same chat on Versa or Codex. The context gauge counted every request Claude Code made in a turn, so each tool call added a whole context to it: a short Haiku 4.5 chat read 295,000 of a 200,000 token window when it held 59,000. It now shows the context the last request carried.
• Claude Code no longer sends every Biorouter tool definition with every request. It loads a tool's definition when the model needs that tool, so a new chat on Opus 5.5 starts at about 31,000 tokens instead of 77,000, close to what Versa uses for the same chat. Claude Code still has no tools of its own.
• Auto compaction no longer gives up on these chats by mistaking the inflated figure for an oversized system prompt.
• The per reply token budget still counts everything a reply spent.

Crew

• Crew sets itself up on a shared Linux server with only your server login. Setup sends the Crew program over SSH, checks it, signs you in when the server asks for a password or code, and starts or joins the workspace. biorouter crew setup, host and doctor do the same from a terminal.
• New workspaces are open: every member can create, rename and delete teams and channels and add people.
• An agent can work on the server in a confined folder, or as you, with your login shell and tools. Confined folders need Linux 6.2 or later.
• Ask the agent from a channel with @agent. Tasks, models and cluster details are part of each workspace.
• Setup now says when it updated or replaced the Crew program, and the Add people dialog labels a channel's owner as Channel owner.

Local models

• Llama Server no longer fails a reply with "Provider reported an error while streaming" when two chats share its memory. The cut reply is retried and continued.
• A retried turn keeps answering what you asked instead of talking about the error.
• A continued reply keeps the space where it joins the cut off text.
• Pressing Stop while a retry waits no longer leaves a hidden instruction in front of your next message.
• A tool call cut off by an error is no longer shown or saved as a reply.
• The GPU out of memory notice no longer asks you to try again just before Biorouter does.

Browser access

• biorouter serve works behind HTTPS reverse proxies and under a path prefix, including JupyterHub, and built apps connect there too. --public-url names the address people open.
• A stale cookie no longer blocks a fresh access link.

Fixes

• An idle background service no longer uses a quarter of a CPU core retrying Remote access. It now waits longer between failed reconnects, up to five minutes.
• A finishing scheduled run can no longer remove the next run's Stop control. This also stops a capped /loop from pausing itself before it ever ran.

Crew user manual