Jc

jc

  Orchestrate multiple Claude Code sessions across projects.
  Draft, send, and switch — all from one window.

  Why · Getting Started · Keybindings · Design · Architecture

Why

Claude takes minutes per task. If you wait, you get four cycles an hour. If you switch to another session while Claude works, you get twelve — but only if you can come back without losing your place.

jc keeps your place outside your head. Each session's notes live in the project's TODO.md, under a ### WAIT marker: you type the next instruction there whenever you think of it, and Cmd-Enter sends it and files it into the message log. Coming back to a session means reading what you already wrote, not reconstructing it.

Switching is cheap. Cmd-P lists every session in every project; each session keeps its own pane layout, cursor position, and terminal scrollback, restored on switch-back. A red * marks the sessions whose Claude terminal has printed something since you last had it on screen, so the picker tells you where the work moved while you were elsewhere. Desktop notifications stay out of the way — only a blocked session (permission prompt, API error) interrupts you, and only when jc isn't the front app.

See DESIGN.md for the full rationale.

Getting Started

Config and state live in ~/.config/jc/ (config.toml, state.toml, theme.toml).

Core Concepts

Projects and Sessions

A project is a code repository registered with jc. Each project has one or more sessions — ongoing Claude Code conversations. Sessions are defined in the project's TODO.md:

The ### WAIT marker separates what you've sent from what you're drafting. Everything below WAIT is draft text — jc never treats it as log, even if it contains a quoted ### Message N heading. When you send (Cmd-Enter), the draft becomes a numbered…