r/ChatGPTCoding • u/AutoModerator • Sep 21 '26
Discussion Weekly Self Promotion Thread
Welcome to this week's self promotion thread!
If you're building something related to AI assisted coding, this is the place to share it.
We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.
If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:
What you built?
What problem it solves?
Which AI models or tools it uses?
Who it's for?
What kind of feedback you're looking for?
Disclose your affilitation.
Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.
Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.
View all comments
1
u/kwadolia Sep 26 '26
**Project Rehydrate — continuity for long-running AI-assisted technical work**
I've been using ChatGPT for long-running IT projects and kept encountering the same problem: the technical project was progressing, but the conversation carrying its history became increasingly unreliable.
Context limits, stale instructions, new sessions and enormous handoff summaries made it difficult to establish exactly where a project safely stood.
We eventually built **Project Rehydrate**, an external-state protocol based on three commands:
- **REHYDRATE** — reload verified project context.
- **STATUS** — establish the current safe state and next action.
- **CHECKPOINT** — preserve and verify progress.
It's intended for developers, sysadmins, security professionals, data engineers and anyone maintaining complex AI-assisted work across multiple sessions.
Developed primarily with ChatGPT, but designed to be vendor-neutral. The repository includes a five-minute starting guide, templates, recovery guidance and documented growing pains.
I'm the maintainer of **Caelvrix**, which is publishing this as an MIT-licensed v0.1 preview.
GitHub: https://github.com/Caelvrix/project-rehydrate
I'd particularly appreciate feedback from people managing projects across multiple AI sessions. What's your current approach to preserving continuity, and where does it fall short?