Writer’s Brief

The Hook

What if you could be mid-conversation with Claude and just say “go start a new session over there with what we just learned” and it actually does it?

Main Points to Cover

  1. The core problem: context is trapped in sessions. You learn something in one conversation that belongs in a different project. The bridge between sessions has always been manual (copy-paste, write a file, start over).
  2. The v1 failure is the interesting part: tried to fork the session (–resume –fork-session), bash quoting became a nightmare, it killed the original session instead of spawning alongside it. The fix was embarrassingly simple: write a shell script to /tmp.
  3. The pattern: when you can’t pass complex stuff between processes inline, write it to a file. The launcher script, the context brief, they’re both the same idea. Files are the universal interface.

The Angle

Building tools for yourself inside the tool you’re building them with. Meta-tooling. The “wait, can I just make this a command?” moment.

Target Reader

Claude Code users who run multiple projects and find themselves wanting to branch conversations. People who use tmux. People who build their own workflows.

Tone Notes

Casual, show the failure. The quoting nightmare screenshot is gold. This is a “I built this in 10 minutes and the first version was hilariously broken” story.

Raw Material / Moments to Write From

These are notes for Alex to write from. Not prose.

  • The initial question: “what’s the best way to spawn a new claude session from an existing one?” and the answer was “write a file, open a new terminal” which Alex correctly identified as sucking
  • “this sorta sucks tho no? like what if i had a command that did that?” - the moment of “wait, I can just build this”
  • v1 failure: it tried –resume –fork-session, the quoting turned into bash inception ('"'"' nested 4 levels deep), it killed the original session instead of spawning alongside it, and the session ID didn’t even exist in the new context
  • The fix was writing a 3-line shell script to /tmp. The whole quoting problem disappeared. Sometimes the answer to “how do I pass complex stuff between processes” is just “write a file”
  • Already had a /handoff skill that generates notes but doesn’t DO anything with them. /spawn is the action version. The progression from “here are notes” to “here are notes AND a running session” is the upgrade
  • The existing skill (/handoff) was written Dec 2024. Took 3 months to think “what if this actually launched the session too?”
  • C4C use case angle: this is a real example of extending Claude Code with a custom command in ~10 minutes