Your AI forgets your architecture every session. Your team doesn't have to. Every decision you make, every convention you set - automatically delivered to Cursor, Claude, Copilot. Via MCP, IDE Extension, or GitHub App. No more pasting context. No more architectural drift. No more "why was this built this way?" We're live on Hacker News 🚀 news.ycombinator.com/shownew hopsule.com

If your extension does 7 things, it does 2 of them well. Sometimes 1.

A good VS Code extension does one thing: hover any file → see which decisions apply. That's it. That's the entire feature. Anything more is a different product wearing the wrong hat.

Versioning your context with git is so obvious it's embarrassing nobody did it earlier. (We didn't either. We're just the ones who shipped it.)

Capsules are just JSON. git add capsule.json git commit -m 'context' git push Your context is now versioned, diffable, reviewable. Welcome to 2026.

The bot is polite. It links the decision, the rationale, the date. Junior learns once. Senior doesn't have to explain again. Calendar respected.

Junior opens PR with Redux. Hopsule comments: 'Zustand was decided in March. Here's the rationale, the date, the approver.' PR reverted. Junior learns. No drama. No meeting. No 1:1 DM at 11pm.

100ms is the threshold. Above that, your AI 'feels slow.' Below it, it 'just works.' Most context tools live at 800ms. That's why they get uninstalled.

30 seconds of context engineering in plain English: 1. Log a decision in Hopsule. 2. MCP picks it up. 3. Cursor autocomplete respects it. Without being asked. No prompts. No copy-paste. No re-explaining on Tuesday.

Three of these have product-level solutions. Hallucinated APIs are still on you. Sorry.

Most painful AI coding moment: 🔘 Forgot the stack 🔘 Used a deprecated pattern 🔘 Hallucinated an API 🔘 All of the above (legal answer)

The intern is fine. The cycle is the problem.

AI without memory is a brilliant intern who quits every 5 minutes. Then re-applies. With a fresh résumé. Forever.

Drop your current .cursorrules line count below. No judgment. (Light judgment.)

Every .cursorrules eventually has a 'TODO: clean up' comment. The TODO outlives most jobs.

.cursorrules at month 1: 5 rules. .cursorrules at month 6: 47 rules, 12 of them contradict. .cursorrules at month 12: a TODO from a developer who left. This is governance with extra steps. #cursor

Faster autocomplete is local minima. Persistent context is the actual ladder. Most tools are still optimizing the wrong axis.

Every 'AI-powered IDE' is solving the wrong problem. You don't need to type faster. You need it to remember Tuesday.

Your Notion page is paragraphs. Your AI wants structured statements. Both are valid. Neither replaces the other. Pretending otherwise is why your docs are stale.

Notion is for humans reading. Hopsule is for AI reading. Same content can't serve both consumers well. Different tools. Different jobs. Stop forcing it.

The average ARCHITECTURE.md hasn't been touched in 14 months. Yes, yours too. git log -p ARCHITECTURE.md. I'll wait.