Aeons · warm handover
One tap. The next step already knows.
Get up to lightning speed with your development projects.
One tap turns a finished Claude session into a task that starts from the session's own memory.
- 🧪 Test & Doc
- 🛠 Implement
- 📦 Allocate
The problem
The next step re-decides what the session settled.
Paste a summary into a fresh session and the reasoning behind each decision stays behind. The second half of the job quietly re-decides the first.
How it works
Three routes. One memory.
- 01
🧪 Test & Doc.
Tests and docs for what the session built, from what it already knows.
- 02
🛠 Implement.
A worked-out design goes on as code.
- 03
📦 Allocate.
The work gets a home in a project.
Your call
Cold only on your tap.
- ♻️ A lapsed session asks before it forks.
- 🧊 … anyway (cold) happens only by choice.
- 🕊 Release asks "Yes, release · Keep it".
In the download
What the Aeons do today.
Keep warm.
They watch the Claude Code sessions you run by hand, in a terminal or in Claude Desktop, and keep a waiting session briefed while you're away. 🔥 Extend +3h stretches the hold.
One live card per session.
One Telegram message per session, edited in place. /chooser lists your sessions. 📜 Condense gives you a short version of what one did.
Warm handover.
🧪 Test & Doc, 🛠 Implement or 📦 Allocate. The task carries on from the session's own memory.
Asks before it acts.
🕊 Release asks "Yes, release · Keep it". A cold handover happens only on your tap.
The big question.
Past 100k tokens, one design question per round, kept as a north star.
- Early
New projects, proposed, never created silently.
The Aeons find your repositories and set up only the ones you confirm.
Facts
Four facts about the thread.
- card per session
- 1
- One message, edited in place.
- warning before a lapse
- 20 min
- The card comes to you once.
- per 🔥 Extend
- +3h
- Stretch the hold from the card.
- added to your transcript
- 0 bytes
- Keeping a session warm reads it and never writes to it.
Handed on whole.
Claude Desktop sessions hand over warm too. The task reads the memory instead of rebuilding it.
Tasks run on Theia, the engine the Aeons live on.
For whom
Built for people who keep several sessions going.
For
- Developers who work with Claude Code in long interactive sessions.
- Leads of small AI-heavy teams who run several sessions at once.
- Anyone handing a worked-out design on to the next step.
Not for
- One-off chat use.
- Anyone not on Claude Code.
- Teams that can't use Telegram: the card lives there today.
FAQ
Questions before you download.
Does keeping a session warm change it?
No. The Aeons read the session as it is. Its transcript stays byte-identical.
Will they act behind my back?
They ask first, before letting a session go and before any cold handover. If you don't answer, a session goes cold quietly and nothing is sent.
Another thing pinging me?
One card per session, edited in place. It comes to you once, 20 minutes before a session would lapse.
I already use /compact and notes. Why this?
/compact condenses the reasoning away, and a summary has to be re-read cold. The Aeons keep the session itself alive and hand on its own memory.
What do I need?
Claude Code (terminal or Desktop) and Telegram. The Aeons run on the Theia engine.
Download
Download Aeons
Tell us who you are, and the download starts right away.