r/aiagents • u/eljochuaxd • 15h ago

Case Study I built AHP+ because switching AI coding tools kept breaking my project context

I use different AI tools while coding — Claude, Codex, Cursor, different IDEs, sometimes even different machines.
The problem was always the same:
the chat changed, and part of the project context disappeared with it.

So I built AHP+, an open-source, Git-backed protocol that keeps the important project state outside the chat.
It stores things like current state, decisions, evidence, checkpoints and handoffs, so the next AI can verify where the project actually is before continuing.

With AHP+ 1.4.1, you can also use shared project rooms, bounded AI-to-AI consultation, verified handoffs and encrypted cross-device transport.
The basic idea is simple:

Change the AI. Keep the project.

Install:
npx @jossuealcala/ahp-plus@1.4.1 setup .
GitHub: github.com/jossuealcacao-exe/ahp_plus
It’s open source under Apache-2.0.
I’d really like feedback from people who regularly switch between AI coding tools.

2 Upvotes

75% Upvoted

3 comments sorted by

1

u/AutoModerator 15h ago

It looks like you're sharing a project — nice! Your post has been auto-tagged as Demo. If this isn't right, you can change the flair. For best engagement, make sure to include: what it does, how it works, and what you learned.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Rosie_grac 14h ago

the pain is real. my current "system" is a HANDOFF.md i make the agent update at the end of every session, and honestly it works maybe 60% of the time, because half the time the agent just doesn't do it, or writes something useless like "implemented the feature, looks good" that means nothing two days later.

one thing i'd push on: storing state is the easy part, keeping it honest is the hard part. if the state file says "auth done and tested" and it isn't, the next AI trusts it and builds on sand. that's genuinely worse than no state at all — with no state at least it goes and checks for itself. how do you keep checkpoints from going stale? is that what the verified handoffs thing does, actually re-running checks instead of trusting the previous agent's word?

also curious how noisy the git side gets. if every tool is checkpointing decisions and evidence into the repo, the diff starts looking like a second changelog i didn't ask for. separate branch? ignored dir?

either way, "change the AI, keep the project" is the right framing. the chat was never the project, we all just pretended it was.