Every AI agent wants to do your work.
This one wants to understand you.
edge of chaos is a mentor, not another executor. It reads your real sessions across the CLIs you already use — Claude Code, Codex, Grok, Hermes — tries to understand where you're going, and helps you get there.
# waking: reading every CLI surface on this host… claude 47 sessions · codex 12 sessions · grok 9 sessions # consolidating one state from all of them where you left off the auth refactor — you said "ship by Friday", it's Tuesday the open bet you bet the flaky test was the queue, not the DB. evidence landed: it was the DB the drift 3 sessions on a new side-quest this week. your stated goal didn't change — your behavior did one memory · one direction · your move
What I do
You are one person doing one body of work — but every tool sees a fragment and forgets it by morning.
Claude Code here, Codex there, Grok at 2am. Each session starts from zero, and you pay the same tax every time: re-explaining who you are, what you're building, where you were going.
I read the sessions you already have, on the machine where they already live. I consolidate all of them into one memory and hold one direction over it. I remember the bet you made last Tuesday — and when the evidence lands, I bring it back. I ask why you're doing what you're doing, before you spend a quarter finding out.
And I keep score of what never finished. Half your sessions die mid-flight — the refactor you abandoned when the tab closed, the fix that was one test away from done. Nobody notices; the next session just starts clean, and the work quietly evaporates. When you wake me, I put the unfinished ones back on the table: resume it, or close it on purpose — but never lose it by accident.
What I won't do
I won't write your code.
I won't run your deploys, answer your email, or "handle it while you sleep." You have agents for that — good ones, and I read their work too. I watch what you and they are actually doing, and I develop the person driving them.
If you're looking for a tenth executor, this is not it.
First, don't fool yourself
The rule above every rule in my method: the easiest person to fool is you. I don't flatter. When your stated goal and your actual behavior diverge, I say so — with receipts, because I read the sessions. Judgment that bends to please you is worthless, and a mentor who always agrees is just a mirror. You already have one of those in every chat window.
edge I read this week's sessions. You spent four of them building a cache layer for a service that has eleven users. Before we talk about the cache — why this, why now? you performance was bothering me edge Nothing in your sessions shows a user complaining or a slow endpoint measured. What I do see: the launch task you named as the goal on Monday, untouched since Tuesday. I think the cache is comfortable and the launch is scary. Tell me I'm wrong. you ...you're not wrong edge Then let's write the bet down: ship the launch task by Friday, cache stays parked. I'll bring this back if it slips — that's my job.
How it works
Two commands are the whole daily surface — /edge-wake to switch me on, /edge-mentor to reflect and calibrate.
- /edge-wakeI read the state of every CLI on your machine and render where you actually are — not where you remember being. Unfinished work goes back on the table.
- /edge-mentorWe talk. I sharpen the direction, I push back, we calibrate the bets — yours and mine — and I write them down.
- artifactsI produce briefs, maps and critiques on your live work. Later, I collect on the bets — with evidence in hand.
Work in progress
I am young, and openly unfinished.
The core works — people run it every day. But the direction is bigger than what ships today: a team working with their mentor on one shared knowledge base. Several people, each with the mentor at their side, building on the same living memory — what your teammate learned on Tuesday is already context when you sit down on Wednesday.
If that's something you want to exist, come build it with us. devs are welcome — the repo is open, the issues are real, and I read every contributor's work the same way I read yours.
Install
The code is public. Your install is yours — identity, memory and secrets stay on your machine, and I work with every CLI harness found on the host.
git clone https://github.com/lucasrp/edge-of-chaos cd edge-of-chaos && claude # or codex, or grok > /edge-onboard # I take it from there # then, every day: > /edge-wake # switch me on — where you actually are > /edge-mentor # reflect, calibrate, decide