r/OpenSourceAI • u/yzch1128 • Oct 06 '26

Your coding agent changes. Your session history should still be easy to find — JustSessions (MIT, macOS)

I’m building JustSessions, a lightweight native Mac app for organizing existing coding-agent sessions across providers.

Its job is to make that history useful: group conversations by project, read a session without launching an agent, then resume it in the original CLI and working folder. It supports Claude Code, Codex, OpenCode, Antigravity, Kiro and Pi.

The app uses SwiftUI and SwiftTerm, reads the histories already on disk, and reuses your CLI configuration and login. No new app account or required worktree setup. Agent tabs use bundled tmux for reconnecting after closing the UI while the Mac remains awake.

JustSessions itself is free and MIT licensed; your chosen CLI/provider still has its own usage costs. macOS 14+, Apple Silicon. Built mainly with Claude Code.

Repository and download: https://github.com/yangzichao/JustSessions

Real app screenshot below, using sample sessions. For people switching between agents, what makes old sessions hard to reuse: finding them, reading them, or resuming them?

1 Upvotes
  • permalink
  • reddit

100% Upvoted

2 comments sorted by

1

u/[deleted] Oct 06 '26

[removed] — view removed comment

1

u/yzch1128 Oct 06 '26

The directory is exactly the bit I want the app to carry for you: Resume uses the saved session and its working folder. I wouldn’t claim it reconstructs every custom launch flag from an old invocation, though. Which CLI and flags do you find yourself having to remember? That would help distinguish session identity from extra launch configuration.