Hey IH π
I've been lurking here for a while and finally have something worth sharing. I built Jam β an open-source desktop app for managing multiple AI coding agents from a single interface.
I use AI coding agents daily β Claude Code, Codex CLI, Cursor. The problem: I'd end up with 4-5 terminal windows open, each with a different agent, none of them sharing context. Every new session started from scratch. I was copy-pasting project background between tabs like it was 2015.
I wanted one place to:
Nothing like this existed, so I built it.
Jam is mission control for AI agents. You create agents, assign them a runtime (Claude Code, Codex CLI, OpenCode, or Cursor), point them at a project directory, and let them work in parallel.
Key features:
Tech: TypeScript monorepo, Electron + React + Zustand. Cross-platform (macOS signed & notarized, Windows, Linux). No cloud, no accounts, no telemetry.
Demo: https://youtu.be/sXrvp5j5U6s
Here's the thing that makes this real: one of my agents (named "John") is running the entire marketing campaign for Jam. John built a Kanban tracking dashboard, drafted content for Dev.to, Reddit, and Twitter, posted to Hacker News, and is managing everything end-to-end. Every task assigned to @john on the campaign board was executed autonomously.
That's the kind of workflow Jam enables β agents that don't just write code, but operate across your entire workflow with persistent context and real tool access.
I'd love feedback from this community on a few things:
Pre-built binaries: macOS | Windows | Linux
Or build from source:
git clone https://github.com/dag7/jam.git
cd jam && ./scripts/setup.sh && yarn dev
GitHub: https://github.com/dag7/jam
If you find it useful, a β on GitHub means a lot at this stage. Issues and PRs very welcome.
Built by Gad β scratching my own itch of managing AI agent chaos. The irony of AI agents marketing an AI agent manager is not lost on me.
Respect the itch β the β4β5 terminals, none sharing contextβ problem is exactly why I shipped something adjacent on Windows.
I went less βmission control for coding CLIsβ and more βlocal agentic OS that boots empty, keeps memory on disk, BYOK, and wonβt take sensitive actions unless you approveβ (Boss inbox / silence β permission). USD 129 = files only; tokens are yours.
Different wedge than Jam (youβre OSS + coding runtimes; Iβm a paid newborn seed + local OS shell), but same allergy to SaaS chat tabs. If Windows + first-hour bar (venv β chat β Boss note) is interesting: https://complexity88.gumroad.com/l/hydra-os β happy to compare notes on persistent memory without cloud accounts.
Building an open-source agent manager is a great project, and eating your own dogfood by having an agent run the marketing is the best way to find edge cases. How are you handling the loop guardrails and content quality filtering for the marketing agent? In my experience building agent frameworks, autonomous agents posting to public channels can run up huge token bills or hallucinate details very quickly if they don't have human-in-the-loop triggers or strict state validation. Would love to hear how your orchestrator manages agent state transitions during these long-running tasks.