You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v1.4.2 — Chat pings and a neon chat frame (2026-11-03)
The room, the inbox and a DM thread wear one frame. A title row with clickable buttons
(Room, Inbox ●N, DM ▸, @ pings on|off, ← Back), heavy accent rules above and below,
a colour chip per person (six neon tones by a hash of the name, the same everywhere; you amber,
the model violet), @name drawn in that person's colour, a bar on any line that names you,
and dividers where a day or ten quiet minutes passed. Inbox rows carry the unread mark, the
chip, presence, the time, N new and the last line; an opened thread bars the lines that were
unread. The bottom line counts mentions since you last looked (@ (2)), and the compact
layout now shows the unread-DM count too. Compact terminals keep the plain footer and
one-line inbox rows.
Chat pings. A person's room line that names you with @name prints a dim User replied: <who> (chat) in your transcript, on your terminals only, so someone watching
the agent work knows to look; the rest of the room, and the model's own replies, print
nothing. A DM to you while you are attached prints New DM (<who>). /chat pings on|off is
your own switch for the mention lines, saved in the host's config as chat.pings; the room's
footer says pings off while it is.
A setting changed from inside a session — /theme, /chat pings, /update check on|off, /coworkers add|remove, /online add, and the standing model_reload consent, in both UIs — is written by
loading the config file afresh and saving that, so the session's own copy, which carries the a key's "always run shell commands" and "approve every write" for the session under the
same keys, is never written to disk by it. Any of those used to make a session's a
permanent.
A job's own compaction summary — a model call that streams nothing back — no longer counts as
silence for the stall clock: it is a wait like a tool call, shown as waiting (compaction),
on the run-time meter, until it has run for twice stall_after (a hung summary call is
still reported). A long chore used to earn one spurious stall line.
A second session on the same workspace no longer closes at startup a job the first session
is still running: each session's work record (work.enabled) now lists its running jobs,
and an open job another live session reports is left as it is with a notice naming that
session. A job nobody reports is closed blocked: interrupted as before — which includes a
job run by a session still on v1.4.1 or earlier, whose record carries no job list.
When the main model's next request waits behind a co-worker's request on the shared server,
the status line says so after two seconds (waiting for the shared server: big's request is in flight; the request goes out when it ends) until the lane is free, instead of pausing in
silence.
The VS Code extension is in the repository. The packaged be-code-vscode-<version>.vsix
is committed under extensions/ (refreshed by the vscode build target) and attached to
every release from v1.4.1 on; the releases before it shipped without the file.