Login

u/jazzy8alex

r/BuildWithClaude r/kimi r/opencodeCLI r/PiCodingAgent r/ClaudeCode r/GithubCopilot r/GeminiCLI r/opencode r/codex r/ChatGPTCoding r/Qwen_AI r/opensource
Qwen Code session history in a macOS app — but I can only verify it against 0.14.3, and my free tier is gone
▲ 1 r/Qwen_AI

Qwen Code session history in a macOS app — but I can only verify it against 0.14.3, and my free tier is gone

I maintain Agent Sessions, a macOS app that reads the local session history your coding agents leave on disk — search across every transcript, browse the tool calls and reasoning, resume a session in the CLI it came from. Free, open source, reads files already on your Mac, uploads nothing. It's at 796 stars and covers thirteen agents: Codex, Claude Code, Cursor Agent, GitHub Copilot CLI, OpenCode, Antigravity CLI, Pi, Kimi Code, Grok CLI, OpenClaw, Hermes, Droid, and — as of last week's 5.0 — Qwen Code.

jazzyalex.github.io/agent-sessions
macOS • open source • ⭐️ 796

Qwen is the one I have a problem with.

The support is real: Qwen chats show up in browsing, search, Analytics and the transcript view, with reasoning and tool calls reconstructed along the active parent chain, so rewound branches render the way they actually happened. Active chats resume in the CLI. I built it against real transcripts and it works.

Against 0.14.3 transcripts. The CLI I have installed is 0.21.13, and the Qwen OAuth free tier was discontinued on 2026-04-15 — so I can't generate a single new transcript on this machine without buying a plan for a model I don't otherwise use. Every Qwen build since April is, honestly, unverified. If the journal format moved between 0.14 and 0.21, I'd have no way of knowing until someone's sessions rendered wrong.

I gather from the free-tier threads here that a few of you are stuck at the same wall from the other side.

So that's the ask. I'm looking for one person who runs Qwen Code with a working account to be its steward.

The job is small and I've tried hard to keep it that way:

./scripts/steward_check.py qwen

It compares your own sessions against the recorded format baseline and tells you whether it still matches. If the format moved, it writes a redacted sample you can attach to an issue — the redaction happens on your machine, before anything leaves it, and you decide what to attach. You never send me a real transcript.

About ten minutes, two or three times a year, when I ping you. No commit rights, no code, no Xcode, no review duty, no response deadline. If you get busy or lose interest, say so or say nothing — Qwen drops back to best-effort and nothing bad happens to you. You get your name on the entry in STEWARDS.md and on the support page, with a dated public record of each check.

Details and the signup form: https://github.com/jazzyalex/agent-sessions/blob/main/STEWARDS.md

And if you'd rather just install it and tell me my Qwen rendering is wrong, that works too — the bug report is worth as much to me as the signup: https://jazzyalex.github.io/agent-sessions/?campaign=reddit&ref=r-qwen-steward.

u/jazzy8alex — 1 day ago
▲ 119 r/ClaudeCode

4 days of outages in a row. Zero communication from Anthropic

4 days of outages in a row.

What is even worse — zero communication from Anthropic: no usage resets, no posts in X. Nothing except a claude status updates.

u/jazzy8alex — 1 day ago
▲ 29 r/ChatGPTCoding+1 crossposts

New agentic benchmark: Session-Bench compares what 10 coding harnesses preserve after the work is done

SWE-bench measures whether an agent completed the task. Session-Bench measures what the harness preserved afterward.

Every coding run leaves behind a session record: prompts, decisions, tool calls, command output, costs, failed approaches, reasoning summaries, and subagent work. After hundreds of sessions, that record becomes part of the project's history.

But coding harnesses preserve it in radically different ways.

I built Session-Bench after encountering these differences while developing a local session browser. It compares 10 CLI session formats across 19 practical gates covering completeness, readability, stability, openness, and tooling.

Some findings:

- The same small probe produced a 1.5 KB session in Pi and roughly 101 KB in Kimi Code.

- Only Pi, OpenClaw, and Kimi Code stamped a true session-format or protocol version.

- Some harnesses preserve readable reasoning or summaries. Others store sealed reasoning, signatures, or no rationale.

- Some record estimated dollar cost; others preserve only token counts.

- Several formats are readable today but offer no stable contract for tools that need to read them tomorrow.

Pi currently scores 18/19, OpenClaw 17/18, and Claude Code and Codex tie at 12/18.

This is not a coding-quality ranking or a recommendation to choose one harness over another. It is a report card for an overlooked part of coding-agent infrastructure: whether the resulting work history remains useful, inspectable, and portable.

The benchmark has limitations. It covers CLI session stores, not complete desktop or IDE behavior. Observation windows vary, and some measurements could not be completed. The raw probe artifacts are not publicly archived yet, so v0.3 is documented and mechanically scored but not fully independently reproducible. Copilot's documentation verdict is also marked as disputed.

I created and maintain the benchmark. I'd especially like feedback on the standard itself: what should a responsible coding-agent work record preserve, and which of the 19 gates would you change?

https://jazzyalex.github.io/agent-sessions/bench/?campaign=reddit&ref=r-chatgptcoding-discussion-v03

Moderator note: This standalone informational/discussion post was approved in advance by the r/ChatGPTCoding moderation team.

u/jazzy8alex — 2 days ago
▲ 1 r/kimi

Added Kimi Code CLI history to my macOS app — and a question about quota tracking

I maintain Agent Sessions, a macOS app for browsing and searching local coding-agent history — ~760 stars, and it already reads Codex, Claude Code, Cursor, OpenCode, Copilot and a few more.

I wanted to give K3 a real run, which meant living in Kimi Code CLI. Its sessions land in ~/.kimi-code/sessions/<hash>/<id>/agents/<id>/wire.jsonl, which you are not finding again without grepping JSONL. So I added Kimi Code CLI as a first-class source in the latest release: sessions grouped by project, full-text search across transcripts, a readable timeline with tool calls, and the command to resume a session in its original working directory.

jazzyalex.github.io/agent-sessions
macOS  • open source • ⭐️ 758

For Claude and Codex my app has a menu-bar meter that tracks this passively: burn rate rather than percent used, so it can tell you the 5-hour pool will run out before it resets instead of just showing a number after the fact.

[SCREENSHOT: Quota Meter showing Claude/Codex]

Kimi has the same 5h + weekly shape, and the API key sits in ~/.kimi-code/config.toml, so it looks doable.

Worth building for Kimi? And if yes — what would you actually want on screen: time until the 5-hour window resets, weekly burn rate, a warning before you hit the wall, or something else?

u/jazzy8alex — 15 days ago
▲ 15 r/opencode

I built a local OpenCode history browser for CLI and desktop app sessions. Plus Agent Cockpit for CLI sessions

I built Agent Sessions for OpenCode users who want to find old runs again without digging through opencode.db or terminal tabs.

  • Full-text search and resume: Search local OpenCode sessions with rebuilt readable transcripts (message cards, Markdown, foldable tool calls, clickable file paths, and images). It opens quickly even on very large histories.
  • Agent Cockpit: A live active/waiting view for OpenCode CLI sessions in iTerm2, grouped by project, so you can see which runs are still working and jump back to the right tab/session.
  • Local OpenCode history: Support for the SQLite store at ~/.local/share/opencode/opencode.db plus legacy session storage, read in read-only mode.

It keeps OpenCode alongside Codex, Claude Code, Cursor, and other supported agents.

Privacy: It reads local records only — it cannot recover anything that was never written to disk. It does not upload transcripts or write into OpenCode's database.

jazzyalex.github.io/agent-sessions
macOS • open source • ⭐️ 702 GitHub stars

https://preview.redd.it/aqyxapl19gch1.png?width=3200&format=png&auto=webp&s=44e9a7f5f9afe6ce9837021e8998506b95d518cd

reddit.com
u/jazzy8alex — 1 month ago
▲ 3 r/BuildWithClaude+1 crossposts

A fast local history browser for Claude Code — full-text search, restore archived sessions, and a 5h/weekly burn meter

Terminal scrollback is the wrong place to keep Claude Code sessions — it loses long runs, and the JSONL on disk has the full history. So I built Agent Sessions, a local macOS app that reads that history and makes it usable.

https://preview.redd.it/s4fv4f3zaach1.png?width=3200&format=png&auto=webp&s=094e761087862d775a358e2b04d5297abb7776a4

For Claude Code it gives you:

- Full-text search and resume across your local sessions, and a rebuilt, readable transcript (message cards, Markdown, foldable tool calls, clickable file paths, images) — it opens instantly even on monster histories.

- It surfaces archived Claude Code sessions (an archived pill + filter) and restores them in place, alongside the rest of your searchable history. Claude's own restore exists but is buried; this just makes it easy to find and do. Shows all subagent sessions and /btw sessions. It even highlight Dynamic Workflow threads!

- Quota Meter for your 5h/weekly limits with per-session burn-rate, so you can see which session is eating the window fastest. It's for subscription plans (not API), needs no terminal/iTerm2, and works on the desktop app too.

It reads local records only — it can't recover anything that was never written to disk.

jazzyalex.github.io/agent-sessions
macOS  • open source • ⭐️ 698

reddit.com
u/jazzy8alex — 1 month ago
▲ 5 r/opensource

Stargazer Bar: open-source macOS menu bar app for tracking GitHub star trends (Swift)

Stargazer Bar is a native macOS menu bar app that shows a live trend chart — star and fork history over time — for public GitHub repos you track. It polls in the background (as often as every 10 minutes) and stores the history locally, so you get an actual trend rather than a current-count snapshot.

Design and implementation notes relevant to this sub:

  • No backend, no telemetry. State lives in UserDefaults; optional tokens in Keychain. The app talks directly to GitHub's REST API using ETags to stay within rate limits.
  • No GitHub account required to track any public repo — you can paste owner/repo strings and ignore auth entirely. Sign-in only powers the optional browse-my-repos picker.
  • Native Swift/SwiftUI. No Electron, no bundled JS runtime. Sparkle handles signed auto-updates (EdDSA). Installable via Homebrew cask.
  • BSD-3-Clause.

Scope is deliberately narrow: a hard cap of 5 tracked repos, no private repos, no local git state, and no PRs/issues/CI as first-class UI. It's built for watching a handful of projects, not managing many — RepoBar is the better fit if you need the latter.

Beyond stars: release download totals, and a per-repo "maintainer radar" that summarizes CI status, new PRs, unanswered issues, and recent commits.

Repo: https://github.com/jazzyalex/stargazer-bar

Issues, PRs, and criticism welcome. The maintainer radar is the newest and least-settled part — if you have opinions on what signals a menu-bar utility should surface, I'd like to hear them.

u/jazzy8alex — 2 months ago
▲ 1 r/opencodeCLI

OpenCode app shows my sessions, but I wanted transcript search across OpenCode, Codex, and Claude

OpenCode's app already shows both desktop and CLI sessions, and that is useful when I am staying inside OpenCode. In my testing, though, search is title-level, not full transcript search inside old sessions.

The gap I kept hitting was after the work moved on: I remembered the command, error, file, or decision, but not the session title or even which agent produced it. Sometimes it was OpenCode, sometimes Codex, sometimes Claude.

So I built Agent Sessions as a local history browser across agents. For OpenCode it reads the local session history already on disk, lets me full-text search transcripts, open the full run, and resume where the CLI supports it.

The main value is the unified surface: OpenCode, Codex, Claude Code, Cursor, Copilot, and Pi in one list, with source labels so I know where each result came from instead of guessing which tool I used.

For CLI-heavy OpenCode users, Agent Cockpit is the other piece: it watches active OpenCode/Codex/Claude CLI sessions running in iTerm2, shows active/waiting state, and lets me jump back to the right iTerm2 session instead of hunting through tabs.

https://preview.redd.it/6q2haxsqbiah1.png?width=3200&format=png&auto=webp&s=1269fb5a1954990ba92bf76ae90002dd567b1d98

New in 4.0: if you also run Codex/Claude, the Quota Meter now has per-session burn-rate / Session Runway, so you can see which active session is eating the 5h/weekly window and when the window resets.

Important boundary: it reads local records only. It cannot recover anything that was never written to disk. Free and open source; OpenCode edge cases and bug reports are useful.

https://jazzyalex.github.io/agent-sessions

reddit.com
u/jazzy8alex — 2 months ago
▲ 1 r/codex

Dogfooding a 5h burn-rate cockpit changed how I run parallel Codex/Claude sessions

I added a Limits Cockpit to Agent Sessions because I kept hitting the same operational problem: several coding-agent sessions were running in parallel, and I could not tell early enough which ones were going to burn the 5h pool before reset.

The useful part is not another percentage meter. It is the decision layer.

Limits Cockpit watches fresh visible Codex/Claude usage snapshots, estimates current burn velocity, and predicts whether the 5h pool reaches 100% before the next reset. If the current pace is going to run out before reset, I can pause lower-priority background work and keep the urgent coding session alive.

Example from dogfooding:

- background scraping/promo sessions can wait

- urgent coding sessions keep the remaining 5h time

- Agent Cockpit shows what is active

- Limits Cockpit shows 5h and weekly pressure

Boundary: this does not bypass limits, extend limits, or read hidden model/runtime state. It is a local planning signal from visible usage snapshots.

Agent Sessions is a local-first macOS app for browsing, full-text searching, and analyzing local AI coding-agent session histories across Codex, Claude Code, Cursor Agent Window/CLI, OpenCode, Hermes, Copilot CLI, OpenClaw, and more.

https://jazzyalex.github.io/agent-sessions

macOS • open source • ⭐️ 648

https://preview.redd.it/a14mt2iu758h1.png?width=770&format=png&auto=webp&s=0ff95d0afa9f936bf7b51b8168566e82a3e65776

reddit.com
u/jazzy8alex — 2 months ago
▲ 2 r/GithubCopilot

I built a local session-history browser for Copilot CLI on macOS

I built Agent Sessions because Copilot CLI sessions become useful project history after a while, but the context is easy to lose in old runs or raw local event files.

For Copilot CLI specifically, it can:

- read local Copilot CLI session history on macOS

- browse sessions by project

- full-text search transcripts

- open old runs in a readable timeline

- show Copilot alongside other local agents without mixing the sources

- copy resume commands where the CLI supports it

- show basic analytics for local agent work by project/session

It is not a replacement for Copilot CLI, and it does not sync sessions across machines. It is a local read-only viewer for the history already on your Mac.

Project:

https://jazzyalex.github.io/agent-sessions

macOS • open source • ⭐️ 569

I am especially interested in feedback from Copilot CLI users: is the useful part transcript search, project grouping, resume, export, or seeing where agent work is happening?

https://preview.redd.it/02uju00zcq2h1.png?width=1600&format=png&auto=webp&s=bc69aa27a180bc64b29e49800e16ba440053713c

reddit.com
u/jazzy8alex — 3 months ago
▲ 1 r/GeminiCLI

I built a local session-history browser for Gemini CLI on macOS

I built Agent Sessions because Gemini CLI sessions can become real project state after a while, but the useful context is easy to lose in old runs or raw local JSON/JSONL history.

For Gemini CLI specifically, it can:

- read local Gemini CLI session history on macOS

- browse sessions by project

- full-text search transcripts

- open old runs in a readable timeline

- show Gemini alongside other local agents without mixing the sources

- copy resume commands where the CLI supports it

- show basic analytics for local agent work by project/session

It is not a replacement for Gemini CLI, and it does not sync sessions across machines. It is a local read-only viewer for the history already on your Mac.

Project:

https://jazzyalex.github.io/agent-sessions

macOS • open source • ⭐️ 569

I am especially interested in feedback from Gemini CLI users: do you actually revisit old session transcripts, or do you prefer making Gemini write durable notes into project files before ending a run?

https://preview.redd.it/p0ormkeqcq2h1.png?width=1600&format=png&auto=webp&s=d1e1ef533d8008695eac7c87a5fb005f9fd3d643

reddit.com
u/jazzy8alex — 3 months ago
▲ 0 r/opencodeCLI

I built a local session-history browser for OpenCode on macOS

I built Agent Sessions because OpenCode sessions become real project state after a while, but the useful context is easy to lose in terminal tabs, old runs, or the local SQLite history.

For OpenCode specifically, it can:

- read local OpenCode session history on macOS

- browse sessions by project

- full-text search transcripts

- open old runs in a readable timeline

- show OpenCode alongside other local agents without mixing the sources

- copy resume commands where the CLI supports it

- show basic analytics for local agent work by project/session

- use Agent Cockpit for heavy CLI workflows: see and switch between active OpenCode iTerm2 sessions, plus Codex CLI and Claude Code

It is not a replacement for OpenCode, and it does not sync sessions across machines. It is a local read-only viewer for the history already on your Mac.

Project:

https://jazzyalex.github.io/agent-sessions

macOS • open source • ⭐️ 569

I am especially interested in feedback from heavy OpenCode users: what is the part of session history you actually need later: transcript search, project grouping, resume, log export, or something else?

https://preview.redd.it/pz2g8a7dcq2h1.png?width=1600&format=png&auto=webp&s=f7fa043df529a3514a0311d8059c4abb6b0619f7

reddit.com
u/jazzy8alex — 3 months ago
▲ 13 r/PiCodingAgent

Agent Sessions now supports Pi CLI - macOS session management app for CLI agents

I added **Pi CLI** support to Agent Sessions app.

https://preview.redd.it/wc4y48njkz0h1.png?width=3200&format=png&auto=webp&s=2cf3ef00d660cb8bf3858a9b77056e199a8d5917

For anyone using Pi heavily: Pi already keeps local JSONL session history, but once you have a lot of sessions across projects, it gets hard to remember which run had the useful answer, tool output, or branch of work.

Agent Sessions now indexes Pi sessions locally and lets you browse/search them in the same UI as Codex, Claude, OpenCode, Gemini, Copilot, Cursor, Hermes, etc.

What works for Pi now:

* Browse Pi sessions by project/date

* Full-text search across Pi transcripts (and other agents too)

* Readable transcript view with tool output

* Filter Pi alongside other agents

* Resume / copy resume command via `pi --session`

This is intentionally a companion, not a replacement for Pi's CLI workflow. You still use Pi exactly the same way in the terminal; Agent Sessions just gives you a native macOS place to browse, search, and jump back into the local session history Pi already writes.

Everything stays local: no account, no telemetry, no uploading session history.

Would love feedback from Pi users, especially if you use custom session paths, extensions, or branching-heavy workflows.

jazzyalex.github.io/agent-sessions

macOS • open source • ⭐️ 544

reddit.com
u/jazzy8alex — 3 months ago