Repository navigation
Releases
v0.39.0 — Merge projects
Merge projects into one card
The last item of the CCMeter settings-panel quartet — joining star (v0.30.0), hide (v0.32.0), and rename (v0.34.0).
Fold several on-disk project folders (e.g. a repo and its git worktree) into one logical card whose metrics sum the members. Drill into a merged card and the heatmaps + KPIs filter across every member at once.
Using it
- Click the ⧉ button on a project card to arm merge mode, then click another project's name to fold it in.
- A merged card shows an ⧉N badge (member count); ⊟ dissolves the group.
- Press Esc or Cancel to abort an armed merge.
Merge groups live in your browser only (localStorage, like star/hide/rename) — the on-disk project keys are never touched and nothing is sent over the wire.
Under the hood
?project=on/v1/metricsand/v1/heatmapnow accepts a comma-separated key list; the aggregator and heatmap filter by set membership. A single project keeps the v0.31.0 fast path.
Gate: 308 tests green across Linux/macOS/Windows · src 7562/8000 LOC.
v0.38.0 — Telegram edit-on-tap
Highlights
Polishes the v0.35.0 inline-approval loop. When you tap [✓ Allow] or
[✕ Deny] in Telegram, the original message now updates in-thread:
Before tap: After tap:
───────────────── ─────────────────
Polaris — approval needed Polaris — approval needed
Session: abc… Session: abc…
cwd: /Users/you/repo cwd: /Users/you/repo
Tool: Bash Tool: Bash
[ ✓ Allow ] [ ✕ Deny ] _Allowed by @yourname at 14:32 UTC_
(buttons removed)
Two improvements:
- Buttons are removed → no accidental double-taps and no "Approval
already handled" toast on re-tap. - The resolution is in-thread, not just as a fleeting toast, so the
chat history shows what happened.
callback_query carries message.message_id + chat.id + text, so
the poller edits without keeping any in-memory state. Best-effort: if
Telegram refuses the edit, the answerCallbackQuery toast still
informs the user.
Image
docker pull ghcr.io/onestepat4time/polaris:0.38.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(telegram): edit message after Allow/Deny tap (#89)
Full changelog: v0.37.0...v0.38.0
v0.37.0 — heatmap trend sparklines
Highlights
Closes the last CCMeter visual gap. The 4-up heatmaps from v0.28.0
matched CCMeter's grid layout, but CCMeter shows a small dashed-line
trend immediately beneath each grid. This release adds a 22 px-tall
SVG area+line sparkline under each card — tinted to the card's accent
(blue input / violet output / amber lines / green cost):
┌─ Input $2.9M ───┐ ┌─ Output 15.5M ──┐
│ ▢▢▢▢▢▣▣▣▣▣▢▢▢▢▢ │ │ ▢▢▢▢▢▣▣▣▣▣▢▢▢▢▢ │
│ ▢▢▢▣▣▣▣▣▣▢▢▢▢▢▢ │ │ ▢▢▣▣▣▣▣▣▣▢▢▢▢▢▢ │
│ ▁▂▃▅▆▇█▇▆▅▃▂▁ │ │ ▁▃▆▇█▇▅▃▂▁ │ ← new
└──────────────────┘ └──────────────────┘
Renders from the existing /v1/heatmap dailyValues — no new
endpoint, no new fetch. The same v0.33.0 auto-refresh tick keeps trend
and grid in lockstep.
Image
docker pull ghcr.io/onestepat4time/polaris:0.37.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(ui): daily trend sparkline under each heatmap card (#88)
Full changelog: v0.36.0...v0.37.0
v0.36.0 — per-session lifetime cost
Highlights
The Sessions tab now shows lifetime cost + token totals on every
session card, right under the header. Until v0.35.0 the tab only
exposed status + settings — auto-refresh from v0.33.0 made the gap
visible: you'd watch the page update with no signal about spend.
┌─ /Users/you/repo abc123def456 · idle ──┐
│ $0.42 1.2K in · 8.4K out · 14 ev │ ← new
│ loaded: CLAUDE.md · settings.json · .mcp.json (2: fs,db)│
│ model: claude-sonnet-4-5 · permissions: 14 allow… │
└─────────────────────────────────────────────────────────┘
How it works
| Step | Component |
|---|---|
GROUP BY (session_file, model) |
db.aggregateBySessionFile() |
Roll up by {sessionId}.jsonl basename |
buildSessionCostMap() |
raw_cost_usd preferred when every event in a bucket carries one |
mirrors aggregator semantics from v0.24.0 |
| Render under session card header | .session-stats row |
Live cost accuracy is preserved even when a session hops between
models — each (file, model) bucket is priced separately and summed.
Image
docker pull ghcr.io/onestepat4time/polaris:0.36.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(metrics): per-session lifetime cost on Sessions tab (#87)
Full changelog: v0.35.0...v0.36.0
v0.35.0 — Telegram inline approval buttons
Highlights
Closes the approve-from-your-phone loop CHARTER §3 promises.
v0.27.0 added a Telegram notification when a Claude Code session hits a
tool-permission prompt. You still had to open the dashboard to approve.
Not anymore. The notification now ships with [✓ Allow] / [✕ Deny]
buttons directly in the Telegram chat:
Polaris — approval needed
Session: abc123def456
cwd: /Users/you/my-project
Tool: Bash
[ ✓ Allow ] [ ✕ Deny ]
Tap a button → SessionManager.respondToApproval fires within seconds,
the agent unblocks, Telegram acks with Allowed by @yourname. No
browser round-trip required.
How it works
| Step | Component |
|---|---|
| Send Allow/Deny on message | Telegram channel emits reply_markup.inline_keyboard |
| Receive callback_query | New telegram-poller.ts long-polls getUpdates |
| Resolve approval | Server handler matches truncated id prefixes against live SessionManager state |
| Respond | SessionManager.respondToApproval |
| Ack | answerCallbackQuery writes "Allowed by @user" toast |
callback_data length is capped at 64 bytes by Telegram — IDs are
truncated to 16-char prefixes (still 2^64 entropy per pair, collision
probability ~10^-15 at realistic load).
Long-polling, not webhook
Self-hosted MVP can't require a public URL. getUpdates with
timeout=30s is the same approach the official Bot SDK uses by default
and works behind NAT.
Setup
No new env var. If POLARIS_TELEGRAM is set the poller starts
automatically alongside the existing channel. No bot config changes
needed — buttons just work on the next approval-needed tick.
Image
docker pull ghcr.io/onestepat4time/polaris:0.35.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(channels): Telegram inline Allow/Deny buttons + callback poller (#86)
- fix(telegram): truncate ids in callback_data to fit 64-byte cap (#86)
Full changelog: v0.34.0...v0.35.0
v0.34.0 — rename projects
Highlights
Phase-6 of the CCMeter parity push. After v0.30.0 (star) and v0.32.0
(hide), this release adds the third of CHARTER §9 M1's project-settings
quartet: rename.
Each project card has a ✎ button next to the name. Click → inline input
swaps in. Enter saves, Esc cancels, blur auto-saves. Empty/whitespace
clears the alias and reverts to the raw folder name.
| Action | Effect |
|---|---|
| ★ | Pin to top (v0.30.0) |
| ✎ | Inline rename — display only |
| ✕ | Hide (v0.32.0) |
Display only
The alias is purely a UI rewrite. The raw project key (e.g. D--aegis)
stays the source of truth server-side for the filter API, Telegram
notifications, log lines, and rule dedup. The card title shows
Alias (raw) so the underlying folder is always visible.
Storage
- localStorage
polaris.projectAliases={ "D--aegis": "Aegis", ... } - Per-browser-local (same convention as starred / hidden / filter).
- Never sent over the wire.
What's left
The settings-panel quartet's only remaining item is merge — that
needs non-trivial server-side resolution semantics and is deferred to
a later PR.
Image
docker pull ghcr.io/onestepat4time/polaris:0.34.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(ui): rename projects via inline editor + alias persistence (#85)
Full changelog: v0.33.0...v0.34.0
v0.33.0 — auto-refresh metrics + Live indicator
Highlights
The Metrics tab now auto-refreshes every 30 s. A pulsing green "Live"
indicator in the toolbar shows the last refresh time. When you switch
tabs, hide the page, or open a different browser tab, the indicator
dims to "paused" — and the refresh interval stops to avoid burning DB
queries while you can't see them.
What's new
| Behaviour | Detail |
|---|---|
| Auto-refresh | 30 s cadence, metrics + projects + heatmap |
| Pause-on-hidden | Page Visibility API — no refreshes while tab is in background |
| Pause-on-other-tab | No refresh while Sessions tab is active (SSE pipeline already handles it) |
| Manual refresh | ↻ button in the toolbar (also shows a spin animation) |
| Keyboard shortcut | r / R triggers an immediate refresh (CCMeter parity) |
| Live counter | "12s ago" / "just now" / "paused" depending on state |
Image
docker pull ghcr.io/onestepat4time/polaris:0.33.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(ui): auto-refresh metrics every 30s + Live indicator + r shortcut (#84)
Full changelog: v0.32.0...v0.33.0
v0.32.0 — hide projects
Highlights
Phase-5 of the CCMeter parity push. After v0.30.0 (star) this release
adds the second half of CHARTER §9 M1's project-settings bundle: hide.
What you get
Each project card has a ✕ button next to the name. Click it → the
project drops out of the main grid into a quiet N hidden · Show
footer. Click the footer toggle to expand the hidden group; each hidden
card has a ↺ to bring it back to the main grid.
| Action | Effect |
|---|---|
| Click ★ | Pin to top (v0.30.0) |
| Click ✕ | Move to hidden footer |
| Click ↺ on hidden card | Move back to main grid |
| Hide a starred project | Star drops automatically (CCMeter parity) |
State
- Hidden set persisted in
localStorage(polaris.hiddenProjects). - Show/hide footer state is session-scoped — collapsed every reload so
hidden projects stay tucked away.
Image
docker pull ghcr.io/onestepat4time/polaris:0.32.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(ui): hide projects + collapsed hidden footer (#83)
Full changelog: v0.31.0...v0.32.0
v0.31.0 — per-project filter
Highlights
Phase-4 of the CCMeter parity push. Click a project name on the Projects
grid → the entire Metrics tab drills into that single project: KPIs,
4-up heatmaps, period-over-period deltas — all filtered. An amber banner
at the top shows the active filter with a ✕ button to clear it.
The filter persists in localStorage (polaris.projectFilter) so a
reload preserves the drill-down. Per-browser-local — same convention as
the starred set in v0.30.0.
API
GET /v1/metrics?range=30d&project=D--aegis ← new
GET /v1/heatmap?days=180&metric=cost&project=D--aegis ← new
Behaviour
- Unfiltered requests keep the v0.24.0 SQL fast-path (no perf regression).
- Filtered requests use a JS-side slow path:
getEventsInRange→
filter byprojectKey()→ per-model rollup. Acceptable cost: drill-
down is an explicit user action, not the hot path. - All 4 heatmaps respect the same filter.
Image
docker pull ghcr.io/onestepat4time/polaris:0.31.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(metrics): per-project filter (?project=X) (#82)
Full changelog: v0.30.0...v0.31.0
v0.30.0 — star/pin projects
Highlights
Phase-3 of the CCMeter parity push. Each project card now has a ★/☆ button
in the header. Click to toggle. Starred projects pin to the top of the
grid (above the cost-desc-ordered rest), and the starred set persists in
localStorage (per-browser-local — never sent over the wire).
Visual
┌─ ★ pinned-project ──────────┐ ← accent border, sticks to top
│ $cost ⏱ │
│ in/out/cache │
│ +X -Y lines │
│ ▓▓▓▓░░░░ tok/ln │
│ stacked sparkline │
└─────────────────────────────┘
┌─ ☆ other-project ───────────┐
│ ... │
└─────────────────────────────┘
Implementation
- One delegated click listener per render (cheaper than per-card).
- Last-loaded
/v1/projectspayload cached inlastProjectsDataso
toggling re-renders instantly with zero extra API calls. - No backend changes. No new env var. No new dep.
Image
docker pull ghcr.io/onestepat4time/polaris:0.30.0
docker pull ghcr.io/onestepat4time/polaris:latestWhat's changed
- feat(ui): star/pin projects (localStorage) (#81)
Full changelog: v0.29.0...v0.30.0