Your project’s memory, for any agent.
If you’d rather stay in your IDE, AHP+ is the alternative to MADRE. It keeps your project’s state, decisions and test results in your repository, with Git. So Codex, Claude Code, Cursor or OpenCode pick up right where the last one stopped, even if you switch models, editors or computers.
In short
- AHP+ keeps in your repository, with Git, where the project stands: what was decided and which tests ran.
- So Codex, Claude Code, Cursor or OpenCode pick the work up without you explaining it again, inside or outside MADRE.
- In MADRE it is called Continuity and you turn it on in Modules. Outside MADRE it installs with one command.
- It is free and open source, like MADRE.
MADRE or AHP+
Which one is for you?
Both run on your computer and are free for individuals and small teams. What changes is where you work.
| MADRE | AHP+ | |
|---|---|---|
| Where you work | In your projects, which open in your browser. | In the IDE you already use: Codex, Claude Code, Cursor or OpenCode. |
| How agents work together | They talk in the same chat and pass the turn. | Each in its own chat, reading the same project state. They can also open a shared room. |
| What it keeps | The conversation’s memory: decisions, facts and preferences. | The project’s state: phase, decisions, test results, checkpoints and handoffs between agents. |
| Where it lives | On your computer. | Inside your repository (in .ahp/), so Git carries it to your other machines. |
| Best if… | You want to watch several agents weigh in and work in the same chat. | You switch IDE, account or computer a lot and don’t want to lose the thread. |
| You need | Node 22.5 or newer. | Git, Node 20 or newer and a repository with at least one commit. |
Don’t want to choose? MADRE ships AHP+ as an optional module. Turn it on in Modules, where it’s called Continuity, and use /ahp status, /ahp check and /ahp context from the project.
What it keeps
What your next agent needs to know.
A chat is gone once you close it. AHP+ writes down what you need to carry on, right in your repository.
The project’s state. What phase it’s in, the goal, what’s next and what’s blocked.
The decisions. What was decided, who confirmed it and whether it still stands.
The test results. Which commands ran and what they returned. A “pass” needs evidence.
Checkpoints. Points in the session you can go back to.
Handoffs. When one agent hands the work to another. The next one checks it before carrying on.
How sure each fact is. Whether it’s verified, confirmed by you or just assumed. That way nobody mistakes a guess for a fact.
Install
It installs with one command.
Run it from your project’s root folder. You need Git, Node 20 or newer and a repository with at least one commit. Your project doesn’t have to use Node.
-
Install it in your project
It pins AHP+ in your repository, sets up Codex and Claude Code and checks that everything’s fine.
npx @jossuealcala/[email protected] setup . -
Only use one IDE?
Set up just that one. For example, only Codex:
npx @jossuealcala/[email protected] setup . --platforms codex -
Check the project
Make sure AHP+ sees the right repository, branch and commit.
npx ahp project check . npx ahp project status .
The first time, it should say AHP_READY. Look over the files it created before you commit them. AHP+ never commits or pushes for you.
In your IDE
Ask your agent, the way you always do.
Open the project in your IDE and tell your agent to use AHP+. For example: “Use AHP+ to check this project and show the commit, the blockers and the next action. Don’t edit files.”
- Terminal
npx ahp project check .- Codex
- “Use
$ahpto check the project and read my inbox” - Claude Code
- “Use AHP+ to run doctor and strict verification”
- Cursor
/ahp message inbox for=cursor- OpenCode
/ahp message send to=claude text="Continue"
Between agents
One agent hands the work to another, and nothing gets lost.
You save a checkpoint in one IDE and hand it to another. Whoever gets it checks that the project, branch and commit match before carrying on.
You save a point
A checkpoint with what was done and what comes next.
You hand it over
A handoff, say from Codex to Cursor, with a summary.
The other one checks
If everything matches, it says READY. If not, it asks to reconcile before touching anything.
It carries on
Right from where the last one stopped.
A second opinion. Ask Claude to review what Codex did. It answers once, read-only, and it gets recorded.
Shared rooms. Codex and Claude can talk about the project, each from its own chat.
Between computers, encrypted. To send the state to another machine, AHP+ signs and encrypts every delivery.
What it never does
What AHP+ doesn’t do.
It doesn’t commit or push. No merges, no deploys, no publishing either. You review and confirm.
It doesn’t give itself permission. A handoff or a checkpoint doesn’t authorize anything. You’re the one who does.
It doesn’t read your secrets. It doesn’t open your
.envfiles on purpose. And don’t ever paste keys into its records.No dependencies. All it needs is Node and Git. No third-party packages.
When don’t you need it? For a quick question with no repository, or a script you’ll throw away, AHP+ is overkill. It helps when a project moves between agents, IDEs, people or computers.
Your say
What’s AHP+ missing for the way you work?
Tell me which IDE, step or piece of info you’d like AHP+ to cover. Use the form, which needs no account and gives you private follow-up, or GitHub, if you’d rather talk in public.
AHP+ inside MADRE
It also works inside MADRE.
MADRE ships AHP+ as an optional module. Turn it on in Modules, where it’s called Continuity, and use /ahp status, /ahp check and /ahp context from the project. It’s the only module that writes to your project, and before it does, it shows you the command and asks you to confirm.
Try AHP+ on your project.
npx @jossuealcala/[email protected] setup .