fleetlens 0.7.1 → 0.10.0

package/app/apps/web/components/usage-gauges.tsx

@@ -1,12 +1,17 @@
 import type { UsageSnapshot, UsageWindow } from "@/lib/usage-data";
+import { paceToneForCycle, toneVar } from "@/lib/utilization-tone";
 
-type Row = { label: string; window: UsageWindow | null };
+const HOUR = 3_600_000;
+const FIVE_HOURS_MS = 5 * HOUR;
+const SEVEN_DAYS_MS = 7 * 24 * HOUR;
+
+type Row = { label: string; window: UsageWindow | null; windowMs: number };
 
 export function UsageGauges({ snapshot }: { snapshot: UsageSnapshot }) {
   const rows: Row[] = [
-    { label: "5 hour", window: snapshot.five_hour },
-    { label: "7 day (all)", window: snapshot.seven_day },
-    { label: "7 day Sonnet", window: snapshot.seven_day_sonnet },
+    { label: "5 hour", window: snapshot.five_hour, windowMs: FIVE_HOURS_MS },
+    { label: "7 day (all)", window: snapshot.seven_day, windowMs: SEVEN_DAYS_MS },
+    { label: "7 day Sonnet", window: snapshot.seven_day_sonnet, windowMs: SEVEN_DAYS_MS },
   ];
 
   return (
@@ -24,16 +29,17 @@ export function UsageGauges({ snapshot }: { snapshot: UsageSnapshot }) {
   );
 }
 
-function Gauge({ label, window }: Row) {
+function Gauge({ label, window, windowMs }: Row) {
   const pct = window?.utilization ?? null;
   const hasData = pct !== null;
   const clamped = hasData ? Math.max(0, Math.min(100, pct!)) : 0;
-  const toneVar =
-    clamped >= 90
-      ? "var(--af-danger)"
-      : clamped >= 70
-        ? "var(--af-warning)"
-        : "var(--af-success)";
+  // Live gauges color by pace, not absolute %. Without resets_at we have
+  // no cycle to anchor against — drop to a neutral border tone so the bar
+  // still renders rather than picking a misleading pace color.
+  const cycleEndMs = window?.resets_at ? new Date(window.resets_at).getTime() : null;
+  const fillColor = hasData && cycleEndMs
+    ? toneVar(paceToneForCycle(clamped, cycleEndMs, windowMs))
+    : "var(--af-border-subtle)";
 
   return (
     <div className="af-card" style={{ padding: "16px 18px" }}>
@@ -77,7 +83,7 @@ function Gauge({ label, window }: Row) {
           style={{
             height: "100%",
             width: hasData ? `${clamped}%` : "0%",
-            background: toneVar,
+            background: fillColor,
             borderRadius: 999,
             transition: "width 0.24s ease",
           }}

package/app/apps/web/components/usage-sidebar.tsx

@@ -3,6 +3,11 @@
 import Link from "next/link";
 import type { UsageSnapshot, UsageWindow } from "@/lib/usage-data";
 import { usePersistentBoolean } from "@/lib/use-persistent-boolean";
+import { paceToneForCycle, toneVar } from "@/lib/utilization-tone";
+
+const HOUR = 3_600_000;
+const FIVE_HOURS_MS = 5 * HOUR;
+const SEVEN_DAYS_MS = 7 * 24 * HOUR;
 
 /**
  * Compact current-usage widget for the sidebar. Always visible on every page.
@@ -38,14 +43,14 @@ export function UsageSidebar({ snapshot }: { snapshot: UsageSnapshot | null }) {
     );
   }
 
-  const rows: { label: string; window: UsageWindow | null }[] = [
-    { label: "5h", window: snapshot.five_hour },
-    { label: "7d", window: snapshot.seven_day },
+  const rows: { label: string; window: UsageWindow | null; windowMs: number }[] = [
+    { label: "5h", window: snapshot.five_hour, windowMs: FIVE_HOURS_MS },
+    { label: "7d", window: snapshot.seven_day, windowMs: SEVEN_DAYS_MS },
   ];
   // Only include Sonnet after hydration to avoid a layout flash where
   // the SSR pass renders it, then the client removes it on hydrate.
   if (sonnetHydrated && showSonnet) {
-    rows.push({ label: "Sonnet 7d", window: snapshot.seven_day_sonnet });
+    rows.push({ label: "Sonnet 7d", window: snapshot.seven_day_sonnet, windowMs: SEVEN_DAYS_MS });
   }
 
   return (
@@ -93,16 +98,22 @@ export function UsageSidebar({ snapshot }: { snapshot: UsageSnapshot | null }) {
   );
 }
 
-function UsageRow({ label, window }: { label: string; window: UsageWindow | null }) {
+function UsageRow({
+  label,
+  window,
+  windowMs,
+}: {
+  label: string;
+  window: UsageWindow | null;
+  windowMs: number;
+}) {
   const pct = window?.utilization ?? null;
   const hasData = pct !== null;
   const clamped = hasData ? Math.max(0, Math.min(100, pct!)) : 0;
-  const toneVar =
-    clamped >= 90
-      ? "var(--af-danger)"
-      : clamped >= 70
-        ? "var(--af-warning)"
-        : "var(--af-success)";
+  const cycleEndMs = window?.resets_at ? new Date(window.resets_at).getTime() : null;
+  const fillColor = hasData && cycleEndMs
+    ? toneVar(paceToneForCycle(clamped, cycleEndMs, windowMs))
+    : "var(--af-border-subtle)";
 
   return (
     <div>
@@ -150,7 +161,7 @@ function UsageRow({ label, window }: { label: string; window: UsageWindow | null
           style={{
             height: "100%",
             width: hasData ? `${clamped}%` : "0%",
-            background: toneVar,
+            background: fillColor,
             borderRadius: 999,
             transition: "width 0.24s ease",
           }}

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.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.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/lib/utilization-tone.ts

@@ -0,0 +1,74 @@
+/**
+ * Utilization tone — the "high usage = good" framing.
+ *
+ * Paying for a plan and barely touching it is the wasteful outcome,
+ * not the safe one. ≥70% peaks = getting value (green). <40% = paying
+ * for headroom you don't need (red). Throttling (real wall hits) is
+ * tracked separately and stays red regardless.
+ *
+ * SYNC: packages/team-server/src/lib/utilization-tone.ts
+ */
+
+export type Tone = "success" | "warning" | "danger";
+
+export const UTILIZATION_THRESHOLDS = { good: 70, low: 40 } as const;
+
+export function utilizationTone(pct: number): Tone {
+  if (pct >= UTILIZATION_THRESHOLDS.good) return "success";
+  if (pct >= UTILIZATION_THRESHOLDS.low) return "warning";
+  return "danger";
+}
+
+export function toneVar(tone: Tone): string {
+  switch (tone) {
+    case "success":
+      return "var(--af-success)";
+    case "warning":
+      return "#b58400";
+    case "danger":
+      return "var(--af-danger)";
+  }
+}
+
+export function utilizationVar(pct: number): string {
+  return toneVar(utilizationTone(pct));
+}
+
+/**
+ * Pace label for the burndown chart. Three states only — describing
+ * the pattern, not judging it. ±15pp band around ideal is "on pace";
+ * outside that, we name what's happening.
+ *
+ * delta = currentRemaining − idealRemaining
+ *   delta < -15 → "may exhaust early" (danger — over-burning)
+ *   delta > 15  → "below pace"        (warning — under-burn)
+ *   else        → "on pace"           (success)
+ *
+ * The band is wider than feels intuitive on purpose: a 7d cycle has
+ * ~14pp/day of ideal burn, so anything tighter flips amber every time
+ * the user takes a night off.
+ */
+export function paceLabel(delta: number): { tone: Tone; label: string } {
+  if (delta < -15) return { tone: "danger", label: "may exhaust early" };
+  if (delta > 15) return { tone: "warning", label: "below pace" };
+  return { tone: "success", label: "on pace" };
+}
+
+/**
+ * Tone for an in-progress cycle/gauge — derived from pace (utilization vs
+ * elapsed-fraction-of-cycle), not from absolute peak. A 50% peak halfway
+ * through a cycle is on pace = green; the same 50% peak in a completed
+ * cycle is moderate-use = amber. Use `utilizationTone()` for completed
+ * cycles, this for live ones.
+ */
+export function paceToneForCycle(
+  utilizationPct: number,
+  cycleEndsAtMs: number,
+  windowMs: number,
+  nowMs: number = Date.now(),
+): Tone {
+  const cycleStart = cycleEndsAtMs - windowMs;
+  const elapsed = Math.max(0, Math.min(1, (nowMs - cycleStart) / windowMs));
+  const idealUsedPct = elapsed * 100;
+  return paceLabel(idealUsedPct - utilizationPct).tone;
+}

package/app/apps/web/package.json

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