I made a small tool for getting back to a coding-assistant conversation by name.

summon carl

The first call creates a record for Carl and opens Claude Code in a new terminal. The next call resumes his most recent Claude session. The record keeps the working directory and persistent notes alongside the session history.

I can add a note when opening it:

summon carl --note "Owns the release checklist"

Or use Codex:

summon carl --using codex

Those are separate provider histories under the same name. Switching to Codex doesn’t move the Claude conversation over. The name and notes carry through; each tool still resumes its own session.

The records live in ~/.agent/ as JSON. A --cwd option changes the working directory, and --same-window keeps the session in the terminal I’m already using.

The awkward part was saving the session identifier. Claude lets the launcher assign one before starting, so summon can write it down immediately. For Codex, this first version captures the identifier after the process exits. The record isn’t complete at the same point in both flows.

That’s about the size of it. Version 0.1.0 opens and resumes named sessions, with the little bit of context I wanted to keep beside them.