Tour
What it does
The more you hand to an AI, the more there is to keep track of. Amenbo has the AI keep that record.
Youjust ask
AIworks, and writes
The recordon your device
The only thing you write is the first sentence.
You don't write the tasks
Before
Implement saving
Write the tests
Tidy the meeting notes
You raise them, you clear them. Eventually you can't keep up.
Amenbo
- Decided the designdone
- Implemented savingdone
- Writing the testsin progress
Raised and cleared by the AI. You only asked.
Opening them and closing them out both happen on the AI's side.
Switch AIs, pick up where you left off
Claude Codeworks partway
The recordon your device
Codexpicks up from there
The context isn't inside the AI — it's in the record on your device.
The AI runs inside Amenbo
Amenbo
Extend search to the body text
Working
Check the README
Working
src/autosave.ts
A job per pane — and the code it touches is open in the next column.
Run them at once — the same work never gets done twice
session Areserve task 696✓ starts
session Breserve task 696✗ taken already
session Creserve task 701✓ starts
The one turned away doesn't duplicate in silence — it moves to other work.
Your data stays on your device
Nothing leaves your device but what you export. (It does check whether a newer version is out — and you can turn that off too.)