Added
- Voice input in the chat composer and the terminal input line. Hold or tap the mic and speak,
Korean and English mixed; the text lands in the box at the caret and is never sent by itself.
It uses your own OpenAI API key, kept on the server (Settings → Voice input), and falls back to
the browser's speech recognition without one. Off by default. Silence before, between and after
the words is left out of the recording, so it is neither uploaded nor billed.
(#231 by @nahwan-kim) - While the app is open, an alert drops in from the top edge as a card: an agent that needs input,
one that finished (by this device's alert choice) or a terminal that ended. A tap opens that
pane, a flick up puts the card away, and it leaves by itself after a few seconds. No card for
the pane already open, and none while the bell is off. Settings → Alerts → In the app turns it
off; it is on by default. Push and tab alerts are unchanged.
(#313 by @Haeminway1) - The sidebar opens a new tab in a workspace (a
+on the workspace, or on the row when it
holds a single pane) and splits a pane beside itself, throughPOST /api/tab/createand
POST /api/pane/split. The new pane is selected once herdr reports it.
(#307 by @piotrchabros) - Settings → Appearance lets you group sidebar sessions by folder, combining panes with the
same full working-directory path within each PC. Grouping by workspace remains the default;
the selected mode and each mode's collapsed groups are remembered independently.
(#299 by @beomq) - While an OmO pane has background tasks running, the chat's status line says how many, and tapping
it lists them: what each is doing, its category and model, how long it has run, its turns, tool
calls and tokens. The newest tasks that ended in the last day (up to ten) are one line under
them that says how many ended and how many failed, and opens to show whether each finished,
failed, was cancelled or was lost with OmO's process. A remote PC lists them once it runs a
bridge that knows this list.
(#305, #310) - The same list shows the workflows (DAG runs) the OmO session started: each one's name, how many
steps are done, running or failed, and its steps wave by wave, with why a failed step failed.
A workflow that ended folds into the same line as the tasks that ended.
(#306) - An OmO turn that set or updated a goal shows it on the turn, beside the skills, also while its work
is folded: the objective, whether it is in progress, complete, blocked, paused or out of budget, and
opened, the whole objective, why it is blocked and the time and tokens spent on it so far.
(#303) - Terminal and chat font families in Settings: a comma-separated list, such as
D2Coding, "Cascadia Mono", tried in order before the built-in fonts, so a font this device
lacks falls back as before. The chat font applies to message text; code stays monospace.
Stored per browser, like the other appearance settings.
(#308 by @Kuhave)
Changed
- Remote PCs use the
remote-v11runtime, which carries the server-side changes sinceremote-v10
to them: a new tab and a split from the sidebar, an OmO pane's background tasks and workflows,
and the access token asked before a Tailscale login is trusted. A PC connected with the
remote-v10bridge updates as it did for earlier runtimes.
(#322) - With an access token set (
HERDR_WEB_TOKEN), your own Tailscale devices are asked for it too:
once per device, and that browser then stays signed in for a year. A paired device still gets in
without it, and nothing changes when no token is set. Before, the token was skipped for a request
that named this PC's Tailscale login, and any other proxy on the same PC (nginx, Caddy, a tunnel)
passes a visitor's copy of that name on unless it is told to drop it, so the token did not keep
such a visitor out. (#309) - A mirrored terminal (a Windows PC, or one with no Node for the terminal attach) sends the rows
that changed instead of the whole screen each time, and shows what you type sooner. An agent at
work repaints a spinner about 12 times a second: measured with gjc, that was 88 KB a second to
every viewer and is 11 KB now. Typing waited for the mirror's next look at the screen, up to
0.4 s on an idle pane: on a real Windows PC a key's echo took 159 ms and takes 23 ms.
(#292)
Fixed
- On a phone, picking a pane (from the drawer, the palette or a notification) or switching between
chat and terminal no longer raises the keyboard over it: you read first, and a tap on the message
box or the terminal raises it. Turning direct typing on still does. A desktop is unchanged.
(#315 by @Haeminway1) - On a phone the status line above the message box is always one row. With a background-task
count, a model name and a reasoning level it wrapped to two rows, three with the context text
open, and took that room from the conversation. On a narrow screen the background-task chip now
shows its icon and the number (the icon alone while nothing runs), the reasoning chip the level
alone, and a model name that still does not fit is shortened. (#312) - The terminal accepts dropped file paths and uploads dropped or pasted files to
the pane's working directory before inserting their quoted paths, without submitting them.
(#304 by @beomq) - A message sent to Claude Code while it is working shows in the chat. Claude records such a
message differently from one sent while it waits, and the chat skipped it, so the agent acted
on words the chat never showed.
(#301) - In an OmO, omp or pi chat, a message that invoked a skill (
/skill:name,$name, or a keyword
such asulw) shows what you asked, not the whole SKILL.md the agent put before it: one such message
filled tens of KB of the chat. The skill shows as a chip under your message, standalone.md
skills included. (#302) - A chat message the page cannot draw no longer blanks the whole app. That message says it can't be
shown and the rest of the conversation stays; if the chat as a whole fails, it says so with Try
again, and the header, sidebar and terminal keep working.
(#300) - New session has a shortcut that works in a browser tab: Ctrl+Shift+O (Cmd+Shift+O on a Mac).
Chrome keeps Ctrl+Shift+N for a new incognito window and never passed it to the page, so it
worked only in the installed app, where it still does.
(#298) - Cmd+Shift+↑ and ↓ select text in the message box on a Mac again (Ctrl+Shift+↑ and ↓ in any text
field elsewhere). The pane shortcut took them wherever the cursor was, switched panes and left
the message behind; it now switches panes from the terminal and outside text fields only.
(#298) - Nerd Font icons (a Starship or Powerlevel10k prompt,
lsd,eza --icons, Neovim file
trees) show in the terminal instead of empty boxes. The terminal's fonts had none of them, and
Safari never uses a font the user installed, so even a Nerd Font set up for the native
terminal did not help there. The app now carries Symbols Nerd Font Mono for those characters
alone; the browser downloads it (1.2 MB) only once a pane prints one, and each icon is drawn to
its one cell, Powerline's separators at the full height of the row.
(#294 by @jmr533) - An agent's finish is no longer lost when a pane opens or closes somewhere at the same moment.
The server reopens its status subscription whenever the set of panes changes, and a status
that changed in between was never sent again: no done alert came, and a browser kept the old
state until its next refresh. The status is now read back once the new subscription is live
and told as the event it would have been. Seen as a flaky test first: with panes opening and
closing beside it, a pane's one status change was lost in 5 of 10 runs, and in none after.
(#291) - Frames and tables an agent draws in the terminal have whole lines. Box-drawing characters came
from the font, whose glyph is shorter than a row, so an upright line broke at every row and a
corner did not meet its lines; a phone drew the heavy lines━ ┃ ╋almost like the light ones,
and shades░▒▓as a dot pattern. These characters and the block elements (█ ▄ ▌and the
like, as in a progress bar) are now drawn to the cell, edge to edge, on whole screen pixels.
(#295) - Several lines sent to an agent from the terminal's input line, or pasted into the terminal,
stay in its message box until sent on a Linux or macOS PC that mirrors its terminals too (one
with no Node for the terminal attach). They went as bare lines there, and the agent sent the
first line as a message of its own. Measured with gjc on a mirrored Linux pane: two lines
arrived as two messages, and now arrive as one.
(#290)