Introducing Hamster 🐹 Multiplayer AI for product teams. Hunch in, PR out. Design, engineering, product, & business reason on the same work, and your agents deliver it. Your team makes a hundred decisions a week. Now your AI remembers all of them. tryhamster.com

our context graph came to life today - full decision lineage - self-healing, self-updating team state - graph expanding as the team works - knows why we did what did when we did it AS WE DO IT, across the whole team everyone’s building infrastructure to read organizational knowledge. we’re building where it gets created. it’s what happens when alignment generates context as exhaust instead of losing it to slack threads holy shit we are never going back

You're describing @usehamster, the AI-native workspace for product teams, where context compounds, and your whole team refines and aligns. The age of the product wiki that nobody keeps up to date has passed. And Hamster two-way syncs with Linear (who we love).

every time you start a new claude code session you spend the first 10 minutes re-explaining your project "here's the stack. here's what we're building. here's what was decided last week. here's the file structure. DON'T TOUCH THIS PART WE JUST REBUILT IT" but it's not just your own context. your teammates shipped 3 new things since yesterday, two architectural decisions changed and a dependency got swapped out. you need to capture all of that too, or claude is building from a stale snapshot you won't remember everything. so claude compiles context from scratch, misses things, and pulls in a direction that might completely miss the point. now multiply that by every dev on your team, every session, all day literal coordinated drift what we do instead: the .hamster folder syncs decisions, plans, and context to the filesystem automatically. claude reads it and just knows. no re-explaining. no stale snapshots. everyone's always got a fresh .hamster folder which updates in real-time as the rest of the team (or you) ship decisions, tasks, briefs, methods, skills, etc try it. you'll love it → @usehamster

everyone on your team maintaining their own CLAUDE.md is a symptom, not a solution. the root cause is that shared context has nowhere to live and evolve as your team makes decisions. you can't fix it with naming conventions or a better folder structure. decisions need a home. not a static file someone remembers to update. a workspace that accumulates as the team works. when a decision changes, it changes once, and every agent on the team pulls from that. there's no need to keep the markdown files up to date or copy-paste anything anywhere. claude just knows. your PRDs, your tasks, your skill files, your CLAUDE.md are all projections of the same underlying decisions. if the decisions live somewhere real, everything else stays aligned. if they stay up to date automatically, the rate of progress can explode because the synchronization overhead disappears. that's what we've been building into hamster. decisions get a home. blueprint holds your product's current state. methods encode how agents should work. the projections stay aligned because the source of truth is real. dm if you want to try it GA reeealllly soon!

haha yeah i am very surprised to hear you’re using mean vc! that’s not what it’s for - but curious what aspect of it got you to use it for this. task master is built for this

we've shipped huge features in taskmaster v0.37 🚀 → real-time PRDs, team plans, synced tasks 🐹 → GPT-5, @lmstudio, @Zai_org GLM → @claudeai plugin @aisdk v5 → smaller MCP tool footprint → redesigned init ux → enterprise proxy more follow retweet bookmark 👀👇

we’ve built the core of @usehamster around multiplayer chat to power real-time collaboration between product eng this leads to consolidated thinking, refinement, and team alignment for PRDs which produce flawless production-ready plans delivered in minutes with taskmaster