fleetlens 0.10.1 → 0.10.2

package/app/apps/web/app/sessions/[id]/session-view.tsx

@@ -292,34 +292,42 @@ export function SessionView({
   /** Detect PR creations in this session. */
   const prMarkers = useMemo(() => detectPrMarkers(session), [session]);
 
-  /** Idle bands derived from raw event timestamps, classified per gap.
+  /** Idle bands derived from raw event timestamps. Anchors include every
+   *  timestamped event (agent-thinking and meta are activity too), and
+   *  each emitted band's `start..end` is a literal time range so the
+   *  minimap stripe width tracks actual idle duration — no across-gap
+   *  merging.
    *
-   *  Two flavors:
-   *    - In-turn idle (gap between agent activities within the same user
-   *      turn) — multiple of these inside one turn collapse into ONE merged
-   *      band whose `start..end` spans the whole period and `durationMs`
-   *      sums the actual idle.
-   *    - Between-turn idle (gap whose terminating anchor IS a user message)
-   *      — emitted standalone. This is "user paused, walked away, came
-   *      back" time and is conceptually distinct from agent thinking.
-   *
-   *  Anchors only count user / agent / tool-call / tool-result events —
-   *  meta + thinking events are skipped so sub-second event-to-event gaps
-   *  don't crowd the strip.
+   *  Two exclusions keep "delegated work" and "response latency" out of
+   *  idle:
+   *    - Subagent run spans are carved out of every candidate gap. When a
+   *      parent dispatches an Agent tool call the gap between tool_use and
+   *      tool_result is the subagent's runtime — not idle. Background
+   *      runs that overlap a user-away gap likewise get clipped out so
+   *      only the genuinely-unwatched portion remains. The carve can
+   *      produce multiple surviving slices per gap; each becomes its own
+   *      band so the visual extent matches reality.
+   *    - "Awaiting first response" — the period between a user message
+   *      and the first agent/tool-call anchor — is dropped wholesale,
+   *      even if intermediate thinking/meta anchors split it into
+   *      multiple sub-gaps. Long model reasoning before the first reply
+   *      is composing, not idle. (User→user gaps still register as
+   *      between-turn idle because no agent activity occurred between.)
    *
    *  Side effect: the leading warm-up gap before the first agent response
    *  drops out unless it crosses MIN_GAP_MS — which the first 6s in a
    *  typical Codex session does not. */
   const rawIdleBands = useMemo(() => {
-    const isAnchor = (role: string) =>
-      role === "user" ||
-      role === "agent" ||
-      role === "tool-call" ||
-      role === "tool-result";
-    const MIN_GAP_MS = 10_000;
+    // Anchor on ANY timestamped event so agent-thinking, meta, and other
+    // intra-turn signals prove the parent is doing work. Only what we
+    // need to distinguish is "user" (turn boundary) vs everything else.
+    const isUserRole = (role: string) => role === "user";
+    // 30s threshold: keeps ordinary tool latency (Read big file, slow Bash,
+    // model thinking between anchors) out of the idle stripes while still
+    // catching anything that reads as a real pause.
+    const MIN_GAP_MS = 30_000;
     const anchors: { ms: number; role: string }[] = [];
     for (const e of events) {
-      if (!isAnchor(e.role)) continue;
       if (!e.timestamp) continue;
       const ms = Date.parse(e.timestamp);
       if (!Number.isFinite(ms)) continue;
@@ -329,38 +337,103 @@ export function SessionView({
     anchors.sort((a, b) => a.ms - b.ms);
     const sessionStartMs = anchors[0]!.ms - (events.find((e) => e.timestamp)?.tOffsetMs ?? 0);
 
+    const subagentSpans = (session.subagents ?? [])
+      .filter(
+        (s): s is SubagentRun & { startTOffsetMs: number; endTOffsetMs: number } =>
+          s.startTOffsetMs !== undefined && s.endTOffsetMs !== undefined,
+      )
+      .map((s) => ({ start: s.startTOffsetMs, end: s.endTOffsetMs }))
+      .sort((a, b) => a.start - b.start);
+
+    /** Subtract subagent spans from [start, end] in offset coordinates,
+     *  returning 0+ remaining slices in time order. */
+    const carveOutSubagents = (
+      start: number,
+      end: number,
+    ): { start: number; end: number }[] => {
+      let pieces: { start: number; end: number }[] = [{ start, end }];
+      for (const span of subagentSpans) {
+        if (span.end <= start) continue;
+        if (span.start >= end) break;
+        const next: { start: number; end: number }[] = [];
+        for (const p of pieces) {
+          if (span.end <= p.start || span.start >= p.end) {
+            next.push(p);
+            continue;
+          }
+          if (span.start > p.start) next.push({ start: p.start, end: span.start });
+          if (span.end < p.end) next.push({ start: span.end, end: p.end });
+        }
+        pieces = next;
+      }
+      return pieces;
+    };
+
+    const overlapsSubagent = (start: number, end: number): boolean => {
+      for (const span of subagentSpans) {
+        if (span.end <= start) continue;
+        // subagentSpans is sorted by start, so once span.start >= end no
+        // later span can overlap [start, end] either — bail out cleanly.
+        if (span.start >= end) return false;
+        return true;
+      }
+      return false;
+    };
+
     type Band = { start: number; end: number; durationMs: number };
     const bands: Band[] = [];
-    let inTurn: Band | null = null;
 
-    const flushInTurn = () => {
-      if (inTurn && inTurn.durationMs > MIN_GAP_MS) bands.push(inTurn);
-      inTurn = null;
-    };
+    // "Awaiting first response" — true after a user message, false once an
+    // agent or tool-call anchor proves the model started replying.
+    // Thinking and meta events don't clear it, so a user→thinking→agent
+    // sequence where thinking→agent crosses MIN_GAP_MS still reads as
+    // response latency rather than idle.
+    let awaitingFirstResponse = false;
+    if (anchors[0]) {
+      if (isUserRole(anchors[0].role)) awaitingFirstResponse = true;
+    }
 
     for (let i = 1; i < anchors.length; i++) {
-      const gap = anchors[i]!.ms - anchors[i - 1]!.ms;
-      if (gap <= MIN_GAP_MS) continue;
+      const rawGap = anchors[i]!.ms - anchors[i - 1]!.ms;
+      const curRole = anchors[i]!.role;
+      // Snapshot the phase BEFORE updating, so the gap is classified by
+      // the state at its start (anchors[i-1]).
+      const skipAsLatency = awaitingFirstResponse && !isUserRole(curRole);
+
+      if (isUserRole(curRole)) awaitingFirstResponse = true;
+      else if (curRole === "agent" || curRole === "tool-call") awaitingFirstResponse = false;
+
+      if (rawGap <= MIN_GAP_MS) continue;
+      if (skipAsLatency) continue;
+
       const gStart = anchors[i - 1]!.ms - sessionStartMs;
       const gEnd = anchors[i]!.ms - sessionStartMs;
+      const betweenTurn = isUserRole(curRole);
+
+      if (!betweenTurn) {
+        // In-turn gap: the parent is mid-turn. If any subagent run overlaps,
+        // the parent is waiting on delegated work — not idle. Drop the
+        // whole gap rather than carving out startup/teardown slivers that
+        // would clutter the minimap with thin stripes. Gaps with no
+        // subagent overlap (long Bash runs, model thinking between tool
+        // calls) still emit as a single band.
+        if (overlapsSubagent(gStart, gEnd)) continue;
+        bands.push({ start: gStart, end: gEnd, durationMs: gEnd - gStart });
+        continue;
+      }
 
-      if (anchors[i]!.role === "user") {
-        // Between-turn idle — close any in-progress in-turn merge first,
-        // then push the between-turn band on its own.
-        flushInTurn();
-        bands.push({ start: gStart, end: gEnd, durationMs: gap });
-      } else {
-        // In-turn idle — accumulate into the running merged band.
-        if (!inTurn) inTurn = { start: gStart, end: gEnd, durationMs: gap };
-        else {
-          inTurn.end = gEnd;
-          inTurn.durationMs += gap;
+      // Between-turn gap: user walked away. Carve out background subagent
+      // activity so only the genuinely-unwatched portion counts as idle.
+      // Each surviving slice becomes its own band.
+      for (const slice of carveOutSubagents(gStart, gEnd)) {
+        const dur = slice.end - slice.start;
+        if (dur > MIN_GAP_MS) {
+          bands.push({ start: slice.start, end: slice.end, durationMs: dur });
         }
       }
     }
-    flushInTurn();
     return bands;
-  }, [events]);
+  }, [events, session.subagents]);
 
   const coldResumeMarkers = useMemo(() => {
     const seen = new Set<string>();
@@ -2668,14 +2741,15 @@ function TranscriptList({
   }
 
   const idleBandList = (rawIdleBands ?? []).slice().sort((a, b) => a.start - b.start);
-  /** Returns the durationMs of the idle band that ends at (or just before)
-   *  the given row's tOffset, or null if no band matches. Tolerance is 1s
-   *  to absorb Date.parse rounding differences between anchor.ms and the
-   *  presentation row's tOffsetMs. */
-  const idleBeforeOffset = (tOff: number | undefined): number | null => {
+  /** Returns the first matching idle band (or null) whose end falls within
+   *  1s of the given row's tOffset. Tolerance absorbs Date.parse rounding
+   *  between anchor.ms and the presentation row's tOffsetMs. */
+  const idleBandBeforeOffset = (
+    tOff: number | undefined,
+  ): { start: number; durationMs: number } | null => {
     if (tOff === undefined) return null;
     for (const b of idleBandList) {
-      if (Math.abs(b.end - tOff) < 1000) return b.durationMs;
+      if (Math.abs(b.end - tOff) < 1000) return b;
     }
     return null;
   };
@@ -2687,6 +2761,11 @@ function TranscriptList({
   };
 
   const out: React.ReactNode[] = [];
+  // A user row and the turn-collapsed row that follows it share a
+  // tOffsetMs (turn anchors at the user message — see buildMegaRows), so
+  // both would match the same between-turn band without this guard. Track
+  // emitted band starts and skip duplicates.
+  const emittedBandStarts = new Set<number>();
   for (let i = 0; i < displayRows.length; i++) {
     const d = displayRows[i];
     // Emit a "Session idle" divider before any row that starts right after
@@ -2694,9 +2773,14 @@ function TranscriptList({
     // expanded turn doesn't render dividers for its inner steps.
     const indented = d.kind === "presentation" ? d.indented : false;
     if (!indented) {
-      const idleMs = idleBeforeOffset(rowTOffset(d));
-      if (idleMs !== null && idleMs > IDLE_THRESHOLD_MS) {
-        out.push(<IdleDivider key={`idle-before-${i}`} gapMs={idleMs} />);
+      const band = idleBandBeforeOffset(rowTOffset(d));
+      if (
+        band !== null &&
+        band.durationMs > IDLE_THRESHOLD_MS &&
+        !emittedBandStarts.has(band.start)
+      ) {
+        emittedBandStarts.add(band.start);
+        out.push(<IdleDivider key={`idle-before-${i}`} gapMs={band.durationMs} />);
       }
     }
 

package/app/apps/web/lib/changelog-data.generated.ts

@@ -1,3 +1,3 @@
 // AUTOGENERATED by scripts/build-changelog.mjs from CHANGELOG.md.
 // Do not edit by hand — run `pnpm changelog:sync`.
-export const RAW_CHANGELOG = "# Changelog\n\nAll notable user-facing changes to the Fleetlens CLI (`fleetlens` on npm) are\nrecorded here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).\nThe team-server has its own log at `packages/team-server/CHANGELOG.md`.\n\n## [0.10.1] — 2026-05-14\n\n### Added\n- **Alternative claude runtime via tmux.** When `tmux` is on PATH, both the LLM pipeline (digest synth, entry enrichment, top-session perception) and the `/ask` feature now drive `claude` through a detached tmux session instead of `claude -p`. Sessions produced this way carry `entrypoint: cli` in their JSONL, which is also extracted by the parser and surfaced as a small badge on `/sessions/<id>` next to the model chip — green for `cli` / `claude-desktop`, amber for `sdk-*`. The path falls back to `claude -p` whenever tmux is unavailable or the run errors; set `FLEETLENS_FORCE_PRINT_MODE=1` to disable the tmux path entirely.\n- **`CCLENS_HOME` env override.** All `~/.cclens/` state (pid file, daemon log, perception state, usage snapshot log, llm-runs traces) is now reached through a shared `cclensHome()` helper that honors `CCLENS_HOME`. Lets multiple installs / workspaces run side-by-side without stomping on each other's state.\n\n### Fixed\n- `/api/runs` rendered every successful tmux-driven run as `status=error`. Tmux runs have no subprocess exit code (the session is killed by cleanup), and the runs viewer was treating a missing code as failure. End records now stamp `exit_code: 0` on success and the active-process filter no longer requires the literal `claude -p` flag, so tmux-driven processes also show up in the \"active\" panel while they're running.\n- `JobQueueWidget`'s `/api/jobs` polling effect listed `jobs` in its deps, so each tick re-armed the effect on the freshly-set state ref — effective cadence collapsed to a 1–4 ms refetch loop. Now tracks `hasActive` in a closure-local var and runs the effect once on mount.\n\n### Conductor\n- New `conductor.json` + `scripts/conductor-{setup,run,archive}.sh` so each Conductor workspace allocates its own 3-port band (web / team-server / postgres) and boots its own `fleetlens-<workspace>` Compose stack against `.harness/cclens-state`. Replaces ~30 hard-coded `join(homedir(), \".cclens\", …)` call sites with the shared `cclensHome()/cclensPath()` helper so a second workspace can boot without colliding with the user's primary install.\n\n## [0.10.0] — 2026-05-08\n\n### Changed\n- **Plan utilization reframed.** High utilization is now \"getting plan value\" (green); low utilization is \"paying for unused headroom\" (red). Mirrors how an operator actually looks at the dashboard: the wasteful outcome is paying for a plan and barely touching it, not running near the cap. Applied across `/usage` burndown, gauges, sidebar, and previous-cycles strip.\n- **In-progress cycles colored by pace, not peak.** A 50% peak halfway through a 7-day cycle reads on-pace green, not amber — the chart no longer cries wolf on a fresh cycle that just hasn't burnt yet. Completed cycles still use peak tone.\n- **Pace label ±15pp band.** \"On pace\" now covers a ±15pp window around ideal; outside that, label is \"below pace\" (under-burning) or \"may exhaust early\" (over-burning). The previous +5/-50 thresholds flipped amber every time the user took a night off.\n- **Pace label collapses to three states.** \"May exhaust early\" / \"below pace\" / \"on pace\" — same color tones, one fewer qualifier to read.\n- **Wording softened across the utilization views** to describe the pattern rather than judge the user. \"Behind schedule\" → \"below pace\"; \"on track (+x%)\" → \"on pace (+xpp vs ideal)\".\n\n### Added\n- **Conductor multi-agent workspace support.** Sessions inside Conductor's worktree-style agent workspaces (`~/conductor/workspaces/<repo>/<agent>/...`) now group correctly under their parent project, with each agent shown as a separate worktree. Mirrors the existing `.worktrees/` handling.\n\n### Fixed\n- Hydration mismatch on `/usage` when pace labels rendered before client mount.\n\n### Notes for operators\n- The CLI's team push now ships **only Claude Code usage snapshots** to the team server. Codex snapshots stay local until `plan_utilization` gets a per-agent partition — without one, the team-server's \"latest snapshot\" pick flips between agents and miscolors the in-progress cycle. Existing rows in `plan_utilization` stay; new pushes are claude-code only.\n\n## [0.9.0] — 2026-05-07\n\n### Added\n- **Gemini CLI** as the third agent source. Sessions written to `~/.gemini/tmp/<slug>/chats/session-*.jsonl` are now read, parsed, and rendered alongside Claude Code and Codex. Tool calls (`read_file`, `list_directory`, `glob`, `run_shell_command`, `update_topic`, …) and their results show in the session timeline; thinking blocks, multi-write status replay, `$set` / `$rewindTo` semantics, and the legacy single-JSON file shape all handled. Slug → cwd inversion via `~/.gemini/projects.json`. `✺` glyph + purple accent in the UI.\n\n### Changed\n- Session detail timeline drops in-turn idle hatching. Within a turn, every wait — model loading, tool execution, network — is the agent's active time. Only between-turn idle (user reading + composing the next message) renders as hatched.\n- Gemini parser anchors `firstTimestamp`, `lastTimestamp`, and `activeSegments` on conversational events only. Login/OAuth `info` records and `metadata.startTime` (file-creation moment) no longer stretch the session bar back to before the first user message.\n\n## [0.7.1] — 2026-05-07\n\n### Fixed\n- Cycle-peaks trend no longer renders two bars labeled the same day. When Anthropic's rolling 7-day window slid its anchor between consecutive polls, the daemon's bucketer (hour-rounded) recorded both reset boundaries as distinct cycles. They're now merged within a 12 h tolerance — same fix in `apps/web/lib/cycle-peaks.ts` (used by `/usage`) and in `packages/cli/src/team/sync.ts` (the daemon's team-server push), so both the personal `/usage` chart and the team-server's plan-utilization view stay consistent. 5-hour cycles keep no merge tolerance (their anchor is stable; merging would collapse legitimate distinct cycles).\n\n## [0.6.4] — 2026-05-04\n\n### Fixed\n- Cached calibration events per-file so `/usage` warm renders complete in well under a second on large session histories.\n\n## [0.6.3] — 2026-05-04\n\n### Fixed\n- Dropped poisoned auto-week locks left behind by interrupted runs; backfill now gates on the live pipeline lock instead.\n\n## [0.6.2] — 2026-05-04\n\n### Added\n- Last week's digest auto-generates on launch when AI features are on. Disable in Settings → AI features.\n\n## [0.6.1] — 2026-05-04\n\n### Changed\n- Smaller install size — published bundle no longer drags in unused workspace metadata.\n\n## [0.6.0] — 2026-04-30\n\n### Added\n- V2 perception layer. Daily, weekly, and monthly digests synthesized from per-session entries via a strict hierarchical pipeline (entry → day → week → month). Past-period digests are immutable on disk; current-period digests use a 10-min in-memory TTL.\n- `/insights` route with on-demand week and month digest generation, picker history, and force-regen.\n- `fleetlens digest day | week | month [--json]` — CLI surface that reproduces the same digests served at `/insights`.\n- `fleetlens entries [--day | --session | --all] [--json]` — inspect the per-session entry primitive.\n\n### Changed\n- Renamed \"active time\" to \"agent time\" across the dashboard and CLI for clarity.\n\n## [0.4.1] — 2026-04-23\n\n### Added\n- Concurrency view on `/parallelism` page. Bursts colored teal for same-project and purple for cross-project (the genuinely interesting fleet-work signal).\n- Plan utilization sparkline on the sidebar, fed by the usage daemon's 5-min snapshots.\n\n### Fixed\n- Auto-update no longer leaves a zombie web server on the old binary; both server and daemon are torn down before re-exec.\n\n## [0.4.0] — 2026-04-18\n\n### Added\n- Usage daemon (`fleetlens daemon …`) polls `/api/oauth/usage` every 5 min and appends snapshots to `~/.cclens/usage.jsonl`. `fleetlens start` and `fleetlens stop` manage server + daemon together.\n- `fleetlens usage --history` for inspecting past plan utilization.\n\n## [0.3.0] — 2026-04-10\n\n### Added\n- Project rollups with worktree aggregation. Sessions inside `<project>/.worktrees/<name>` roll up under their parent canonical project with a `+N wt` badge.\n- Pinned projects in the sidebar (per-browser via localStorage).\n\n## [0.2.0] — 2026-04-01\n\n### Changed\n- Active-segment computation now uses all timestamped events (system + summary + sidechain + conversational) instead of conversational-only. Earlier filter undercounted by up to 100x on tool-heavy sessions.\n\n## [0.1.0] — 2026-03-15\n\n### Added\n- Initial release. Local-only dashboard for Claude Code sessions: timeline, projects, daily activity bucketing, parallelism detection, per-model cost estimation. Reads JSONL transcripts from `~/.claude/projects/`.\n";
+export const RAW_CHANGELOG = "# Changelog\n\nAll notable user-facing changes to the Fleetlens CLI (`fleetlens` on npm) are\nrecorded here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).\nThe team-server has its own log at `packages/team-server/CHANGELOG.md`.\n\n## [0.10.2] — 2026-05-15\n\n### Fixed\n- **Session-detail minimap no longer paints subagent runtime as idle.** Long agent runs that dispatched many subagents were reading as wall-to-wall \"Session idle\" stripes because the parent's tool_use → tool_result gap (the subagent's actual runtime) was classified as in-turn idle. `rawIdleBands` now carves subagent run spans out of every candidate gap; for in-turn gaps that overlap any subagent run the entire gap is dropped, and between-turn gaps with background subagent activity keep only the genuinely-unwatched residue.\n- **First-response thinking stops registering as idle.** Anchors now include every timestamped event (agent-thinking, meta, etc.), and the loop tracks an \"awaiting first response\" phase across intermediate thinking anchors. A `user → thinking → thinking → agent` sequence where the model takes a while to compose its first reply is now treated as response latency rather than painted as a stripe.\n- **Turn duration no longer shows `0ms` for single-row turns.** `buildMegaRows` now anchors a turn's `tOffsetMs` and `durationMs` at the originating user message rather than at the first agent row. Single-row turns show the actual user → agent latency, and the visual span of the turn rectangle on the minimap covers the whole arc.\n- **Single `Session idle` divider per band.** A user row and the turn-collapsed row that follows it now share a `tOffsetMs`, so the body's `IdleDivider` emitter dedupes per band to stop two consecutive identical idle markers around the same boundary.\n\n### Changed\n- Minimap idle threshold raised from 10s to 30s. Ordinary tool latency (slow Bash, big-file Read, between-anchor model thinking) no longer registers as idle.\n\n## [0.10.1] — 2026-05-14\n\n### Added\n- **Alternative claude runtime via tmux.** When `tmux` is on PATH, both the LLM pipeline (digest synth, entry enrichment, top-session perception) and the `/ask` feature now drive `claude` through a detached tmux session instead of `claude -p`. Sessions produced this way carry `entrypoint: cli` in their JSONL, which is also extracted by the parser and surfaced as a small badge on `/sessions/<id>` next to the model chip — green for `cli` / `claude-desktop`, amber for `sdk-*`. The path falls back to `claude -p` whenever tmux is unavailable or the run errors; set `FLEETLENS_FORCE_PRINT_MODE=1` to disable the tmux path entirely.\n- **`CCLENS_HOME` env override.** All `~/.cclens/` state (pid file, daemon log, perception state, usage snapshot log, llm-runs traces) is now reached through a shared `cclensHome()` helper that honors `CCLENS_HOME`. Lets multiple installs / workspaces run side-by-side without stomping on each other's state.\n\n### Fixed\n- `/api/runs` rendered every successful tmux-driven run as `status=error`. Tmux runs have no subprocess exit code (the session is killed by cleanup), and the runs viewer was treating a missing code as failure. End records now stamp `exit_code: 0` on success and the active-process filter no longer requires the literal `claude -p` flag, so tmux-driven processes also show up in the \"active\" panel while they're running.\n- `JobQueueWidget`'s `/api/jobs` polling effect listed `jobs` in its deps, so each tick re-armed the effect on the freshly-set state ref — effective cadence collapsed to a 1–4 ms refetch loop. Now tracks `hasActive` in a closure-local var and runs the effect once on mount.\n\n### Conductor\n- New `conductor.json` + `scripts/conductor-{setup,run,archive}.sh` so each Conductor workspace allocates its own 3-port band (web / team-server / postgres) and boots its own `fleetlens-<workspace>` Compose stack against `.harness/cclens-state`. Replaces ~30 hard-coded `join(homedir(), \".cclens\", …)` call sites with the shared `cclensHome()/cclensPath()` helper so a second workspace can boot without colliding with the user's primary install.\n\n## [0.10.0] — 2026-05-08\n\n### Changed\n- **Plan utilization reframed.** High utilization is now \"getting plan value\" (green); low utilization is \"paying for unused headroom\" (red). Mirrors how an operator actually looks at the dashboard: the wasteful outcome is paying for a plan and barely touching it, not running near the cap. Applied across `/usage` burndown, gauges, sidebar, and previous-cycles strip.\n- **In-progress cycles colored by pace, not peak.** A 50% peak halfway through a 7-day cycle reads on-pace green, not amber — the chart no longer cries wolf on a fresh cycle that just hasn't burnt yet. Completed cycles still use peak tone.\n- **Pace label ±15pp band.** \"On pace\" now covers a ±15pp window around ideal; outside that, label is \"below pace\" (under-burning) or \"may exhaust early\" (over-burning). The previous +5/-50 thresholds flipped amber every time the user took a night off.\n- **Pace label collapses to three states.** \"May exhaust early\" / \"below pace\" / \"on pace\" — same color tones, one fewer qualifier to read.\n- **Wording softened across the utilization views** to describe the pattern rather than judge the user. \"Behind schedule\" → \"below pace\"; \"on track (+x%)\" → \"on pace (+xpp vs ideal)\".\n\n### Added\n- **Conductor multi-agent workspace support.** Sessions inside Conductor's worktree-style agent workspaces (`~/conductor/workspaces/<repo>/<agent>/...`) now group correctly under their parent project, with each agent shown as a separate worktree. Mirrors the existing `.worktrees/` handling.\n\n### Fixed\n- Hydration mismatch on `/usage` when pace labels rendered before client mount.\n\n### Notes for operators\n- The CLI's team push now ships **only Claude Code usage snapshots** to the team server. Codex snapshots stay local until `plan_utilization` gets a per-agent partition — without one, the team-server's \"latest snapshot\" pick flips between agents and miscolors the in-progress cycle. Existing rows in `plan_utilization` stay; new pushes are claude-code only.\n\n## [0.9.0] — 2026-05-07\n\n### Added\n- **Gemini CLI** as the third agent source. Sessions written to `~/.gemini/tmp/<slug>/chats/session-*.jsonl` are now read, parsed, and rendered alongside Claude Code and Codex. Tool calls (`read_file`, `list_directory`, `glob`, `run_shell_command`, `update_topic`, …) and their results show in the session timeline; thinking blocks, multi-write status replay, `$set` / `$rewindTo` semantics, and the legacy single-JSON file shape all handled. Slug → cwd inversion via `~/.gemini/projects.json`. `✺` glyph + purple accent in the UI.\n\n### Changed\n- Session detail timeline drops in-turn idle hatching. Within a turn, every wait — model loading, tool execution, network — is the agent's active time. Only between-turn idle (user reading + composing the next message) renders as hatched.\n- Gemini parser anchors `firstTimestamp`, `lastTimestamp`, and `activeSegments` on conversational events only. Login/OAuth `info` records and `metadata.startTime` (file-creation moment) no longer stretch the session bar back to before the first user message.\n\n## [0.7.1] — 2026-05-07\n\n### Fixed\n- Cycle-peaks trend no longer renders two bars labeled the same day. When Anthropic's rolling 7-day window slid its anchor between consecutive polls, the daemon's bucketer (hour-rounded) recorded both reset boundaries as distinct cycles. They're now merged within a 12 h tolerance — same fix in `apps/web/lib/cycle-peaks.ts` (used by `/usage`) and in `packages/cli/src/team/sync.ts` (the daemon's team-server push), so both the personal `/usage` chart and the team-server's plan-utilization view stay consistent. 5-hour cycles keep no merge tolerance (their anchor is stable; merging would collapse legitimate distinct cycles).\n\n## [0.6.4] — 2026-05-04\n\n### Fixed\n- Cached calibration events per-file so `/usage` warm renders complete in well under a second on large session histories.\n\n## [0.6.3] — 2026-05-04\n\n### Fixed\n- Dropped poisoned auto-week locks left behind by interrupted runs; backfill now gates on the live pipeline lock instead.\n\n## [0.6.2] — 2026-05-04\n\n### Added\n- Last week's digest auto-generates on launch when AI features are on. Disable in Settings → AI features.\n\n## [0.6.1] — 2026-05-04\n\n### Changed\n- Smaller install size — published bundle no longer drags in unused workspace metadata.\n\n## [0.6.0] — 2026-04-30\n\n### Added\n- V2 perception layer. Daily, weekly, and monthly digests synthesized from per-session entries via a strict hierarchical pipeline (entry → day → week → month). Past-period digests are immutable on disk; current-period digests use a 10-min in-memory TTL.\n- `/insights` route with on-demand week and month digest generation, picker history, and force-regen.\n- `fleetlens digest day | week | month [--json]` — CLI surface that reproduces the same digests served at `/insights`.\n- `fleetlens entries [--day | --session | --all] [--json]` — inspect the per-session entry primitive.\n\n### Changed\n- Renamed \"active time\" to \"agent time\" across the dashboard and CLI for clarity.\n\n## [0.4.1] — 2026-04-23\n\n### Added\n- Concurrency view on `/parallelism` page. Bursts colored teal for same-project and purple for cross-project (the genuinely interesting fleet-work signal).\n- Plan utilization sparkline on the sidebar, fed by the usage daemon's 5-min snapshots.\n\n### Fixed\n- Auto-update no longer leaves a zombie web server on the old binary; both server and daemon are torn down before re-exec.\n\n## [0.4.0] — 2026-04-18\n\n### Added\n- Usage daemon (`fleetlens daemon …`) polls `/api/oauth/usage` every 5 min and appends snapshots to `~/.cclens/usage.jsonl`. `fleetlens start` and `fleetlens stop` manage server + daemon together.\n- `fleetlens usage --history` for inspecting past plan utilization.\n\n## [0.3.0] — 2026-04-10\n\n### Added\n- Project rollups with worktree aggregation. Sessions inside `<project>/.worktrees/<name>` roll up under their parent canonical project with a `+N wt` badge.\n- Pinned projects in the sidebar (per-browser via localStorage).\n\n## [0.2.0] — 2026-04-01\n\n### Changed\n- Active-segment computation now uses all timestamped events (system + summary + sidechain + conversational) instead of conversational-only. Earlier filter undercounted by up to 100x on tool-heavy sessions.\n\n## [0.1.0] — 2026-03-15\n\n### Added\n- Initial release. Local-only dashboard for Claude Code sessions: timeline, projects, daily activity bucketing, parallelism detection, per-model cost estimation. Reads JSONL transcripts from `~/.claude/projects/`.\n";

package/app/apps/web/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claude-lens/web",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "private": true,
   "description": "Local-only dashboard for Claude Code sessions. Reads ~/.claude/projects/*.jsonl and visualizes agent activity.",
   "license": "MIT",