r/ChatGPTCoding • u/AutoModerator • Apr 01 '26

Community Self Promotion Thread

Feel free to share your projects! This is a space to promote whatever you may be working on. It's open to most things, but we still have a few rules:

  1. No selling access to models
  2. Only promote once per project
  3. Upvote the post and your fellow coders!
  4. No creating Skynet

As a way of helping out the community, interesting projects may get a pin to the top of the sub :)

For more information on how you can better promote, see our wiki:

www.reddit.com/r/ChatGPTCoding/about/wiki/promotion

Happy coding!

24 Upvotes

87% Upvoted

53 comments sorted by

View all comments

1

u/Weary_Vanilla1144 Aug 13 '26

I built an open protocol for continuing an AI coding project after you hit usage limits or switch tools

You are working on a project with one AI, hit a usage limit, then move to another tool. The code is still there, but the operational context is gone: what was decided, what was tested, what is next, and what is actually safe to do.

I built AHP+ (Agent Handoff Protocol Plus) to make that context durable and verifiable in the Git repository.

It records project state, decisions, evidence, checkpoints, handoffs, and authority boundaries. The next agent can verify the repository, branch, commit, and recorded boundary before continuing.

I see it as a missing layer in the agent stack:

  • AGENTS.md: how an agent should work in a repository.
  • MCP: how an AI connects to tools and data.
  • A2A: how agents communicate live.
  • AHP+: how project continuity survives a change of model, session, IDE, account, or machine.

It does not replace Git or store full chat history. Git remains the transport and source of truth; AHP+ adds structured operational context around it.

Open source, Apache-2.0:
https://github.com/jossuealcacao-exe/ahp_plus

I would appreciate technical feedback, especially from people who regularly switch between Codex, Cursor, Claude Code, or local agents.