For developers who spend 2+ hours daily coding with AI and need sessions that don't start from scratch every time.
The real problem isn't memory
You've probably set up project-level context for your AI — rules files, system prompts, documentation. And they work for teaching the AI your conventions.
But there are three problems they don't solve:
1. Cross-session continuity
You're building a feature with AI. Three hours in, you've split it into 8 tasks and finished 5. Then you close your laptop.
Next morning, new session, blank slate. You paste yesterday's conversation back in. The AI says "got it" and starts from task 3, silently rewriting task 4's logic along the way.
2. Scope creep without consent
You ask the AI to fix a button style. It refactors the component structure. You ask it to fix a bug. It "optimizes" a database query. These changes are mixed in with your intended work, and you might not notice.
3. No decision trail
Three days later you're looking at the code: why was this designed this way? What alternatives were considered? If you relied on chat history, you'd scroll through dozens of turns. If the session expired, that context is gone forever.
What if context lived in your file system?
Feedback via issues is welcome. PRs for new host adapters even more so.
SOCIAL SHARE CARD GENERATOR