Skip to content

fix(sessions): sidebar "All" badge counts only genuinely live runs (v0.193.2) #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vikasprogrammer merged 1 commit into from
Jul 14, 2026
Merged

fix(sessions): sidebar "All" badge counts only genuinely live runs (v0.193.2) #324

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,15 @@ new version heading in the same commit.

## [Unreleased]

## [0.193.2] — 2026-07-14
### Fixed
- **Sidebar "All" session badge now counts only genuinely live runs.** It was keyed off `isLive`, which
is deliberately broad — an interactive session that reported `done` but keeps an attachable pane reads
live so its dot stays green and reattachable. That inflated the badge with finished sessions whose tmux
panes were never reaped (some days old), so the count could read ~10 when only a handful were actually
running. The badge now mirrors the server's canonical `aliveSessionCount`: a session with stored status
`running` and a live (or unpollable) pane. Per-session dots/reattach affordances are unchanged.

## [0.193.1] — 2026-07-14
### Fixed
- **Chat replies no longer stall on "thinking…" forever.** The v1 Chat surface delivered a follow-up by
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "agent-os",
"version": "0.193.1",
"version": "0.193.2",
"description": "A generic, governed operating system for running autonomous agents safely across brands. Ships with a local web console.",
"license": "MIT",
"type": "commonjs",
Expand Down
8 changes: 7 additions & 1 deletion web/src/App.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -997,7 +997,13 @@ function Console({ me }: { me: Member }) {
const pendingApprovals = messages.filter(isActionRequired).length
// Sessions where Claude is blocked waiting on the human — drives the per-session bell everywhere.
const waiting = new Set(messages.filter((m) => m.type === 'notification' && m.status === 'open').map((m) => m.sessionId))
const runningSessions = sessions.filter(isLive).length
// The sidebar "All" badge counts genuinely LIVE runs — a session actively RUNNING with a live pane —
// mirroring the server's canonical aliveSessionCount. `isLive` is deliberately broader (an interactive
// session that reported `done` but keeps an attachable pane reads live so its dot stays green +
// reattachable), which would inflate this badge with finished sessions whose panes were never reaped.
// A running row with a confirmed-dead pane (alive === false) is mid-reap → excluded; alive undefined
// (poll failed / launcher backend) falls back to the stored 'running' status.
const runningSessions = sessions.filter((s) => s.status === 'running' && s.alive !== false).length
// The sidebar is a switcher over the sessions *I'm accountable for* — ones I started directly
// (spawnedBy is my member id) OR ones a trigger spawned that run AS me (runAs): a Task I own that
// auto-dispatched, a chat message I sent. Those have a `task:`/`automation:` provenance, so keying
Expand Down
Loading