Git remembers everything.
Your brain doesn’t.
Resume reconstructs your last coding session so you can instantly continue where you left off.
Your 60-second briefing before you start coding.
pip install resume-cliresumerun inside any git repo// the problem
Every developer knows
this moment.
You open your laptop.
You're not sure which branch was the one that almost worked. Ten minutes later you remember what you were building.
Resume compresses that into ten seconds.
// demo
What it actually looks like.
Raw output, no edits. Thea speaks the same text aloud in parallel.
// the ritual
Your new daily coding ritual.
Two commands bracket the day. The note you leave at wrap becomes the first line of tomorrow's briefing.
you’re coding again before your coffee is cool.
the note is included in tomorrow’s briefing.
// how it works
Three steps, one command.
git log / git diffResume reads your git history.
Commits, diffs, timestamps, file touches. Everything local, nothing uploaded.
inspect → reconstructThea reconstructs your development session.
She infers what you were working on, what changed since, and what’s still open.
briefing · 60sYou get a short technical briefing.
60 seconds, streamed as text, spoken aloud. Then a suggested next step.
// features
Small surface. A lot under it.
Git-native
Works directly from git history. No daemon, no tracker, no plugin.
resumeVoice + text briefing
Hear your context while reading it. Thea speaks in parallel with the stream.
resume --voiceContinue where you left off
Automatically reopens the last file you edited in your editor.
1 ↵Daily context loop
resume wrap creates tomorrow’s briefing. The day stays threaded.
resume wrap// who it's for
If you switch contexts, you lose state.
Resume isn't for everyone. It's for the people who spend most of their day not quite remembering what they were doing an hour ago.
You spent the morning in meetings. By 11:15 you've forgotten which of three branches was the one that almost worked.
You get short windows. Resume makes sure those windows don't start with ten minutes of “wait, where was I”.
Switching repos is a full context flush. Resume runs per-repo, so each one remembers its own thread.
// why this works
Why this works.
When you switch tasks, your brain leaves part of its attention behind. Psychologists call this attention residue.
The next session starts at a deficit. You spend the first ten minutes pulling context back into working memory — not because the work is hard, but because the state is gone.
Resume reconstructs the mental context so you can immediately continue working.
Get the morning briefing.
Drop your email. One message when Thea is ready to talk back.
Early developers will get access first.