Code is cheap.
Show me the talk.
Sessiontail keeps the whole agent session: what you tried first, why you threw it out, how it finally worked. Read how other people got there, carry your own to any device, or pick up from the middle of someone else’s.
This does not create an account or grant product access. We won’t use this address for marketing emails.
01
Learn from the process
What an open-source repo leaves out, Sessiontail fills in.
A good session reads like someone’s working notes. It doesn’t teach the right way; it shows you how one person actually felt their way through. That is more useful than the answer.
- Every step, from the first vague idea to the last edit
- Where they got stuck, what they got wrong, what they threw out
- How different people break down the same problem
What a session usually contains
02
Across devices
A session shouldn’t be stuck on one machine.
Start it on the work laptop, open the home machine, and the whole context is there. No re-explaining the background, no scrolling back through a chat log.
- One link carries the entire context
- Keep talking to the agent — it knows what happened before
- Phone, tablet, another computer: open it and read
The context travels with you
03
Continue
Start from someone else’s halfway point.
Found a session that is going somewhere? Fork it to your own machine and continue from any step. Your branch is its own session; the original is untouched.
- Any public session can be forked and continued locally
- Your branch sits beside the original — neither overwrites the other
- Good ideas do not have to start from nothing
Fork
04
Privacy
Keys never leave your computer.
Redaction runs on your device, not on our servers. Private keys, tokens, local paths, other people’s email addresses — all replaced before anything is uploaded.
- Review every session before it goes out; you decide what stays
- Credentials are stripped before they reach the network
- Nothing is public by default
The same line, before and after
Replaced on your device · only then does it leave
Private projects · end-to-end encrypted
Some sessions are for your eyes only. So we can’t read them either.
A project marked private is encrypted end to end before it leaves your device. The key stays with you; the server holds nothing but ciphertext.
- Encryption happens locally; the key is never uploaded
- We can’t decrypt it, and can’t be asked to
- You choose which sessions become public, one at a time
What actually exists on the server
Also
Not just for people who write code.
Drafting proposals, researching, organising material, running operations, editing copy — if the process was worth something, it is worth keeping.
Two agents, one way to read them
Codex and Claude Code sessions both come in, tidied into the same readable shape.
Search the content, not the filename
Look for “that approach we discussed” — a single line from a tool’s output can bring you back to the session.
Every publish is a version
Change it and publish again; the old one stays. The link says which version someone is reading.
Take it with you
Export a portable file and open it locally any time. If you stop using this tomorrow, the work is still yours.
Team knowledge settles
“How did we land on this approach” stops living in a chat log and becomes something searchable, shareable, continuable.
You review before it goes out
Every session passes your eyes before it is public. Nothing is public by default.
Waitlist open
When it’s ready, you’ll be the first to know.
- What you’ll get
- A confirmation, then a note when it opens
- What won’t happen
- No account · no access granted · no marketing
- How often
- Only when there is progress