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
@hshah18@linear@karrisaarinen 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!
@BoizHiver91548@tom_doerr AI can USE something like this to get what it needs and what is relevant. It provides a traversable interface for LLMs to discover context. For those of us working heavily in the native AI applications + orchestration space these kinds of techniques are killer
@g_korland@benln Context in Hamster studio lives as a node. There are close relations, and relations that are further away. Where you are and what you're doing within Hamster helps delegate what's relevant to you at that time. Chat grows like a tree, and it's aware of its branches.
This almost felt like a product singularity moment for me building this.
There was a point during development where I had run my n’th iterative tweak on this. I was planning a new feature for Hamster using Hamster and I realized how people build product is going to change
we've unlocked for ai task management what reasoning unlocked for LLMs
the plan quality is orders of magnitude better than anything i've ever seen before. it's in a completely different league and i'm in shock tbh
parsing prds now auto-generates the perfect breakdown of tasks
@danielrakh multiplayer chat is the next great collaborative ui
we use it for teaming up to draft and refine PRDs and briefs that then get executed by background agents
@lgrammel Makes sense! Less options for achieving the same outcome is a good thing. Especially if it aligns with everything else you're building going forward.
know incredible devs?
paying $5K for successful referrals
looking for:
- senior TS engineers to own core pkgs for @usehamster
- lead integration specialist to help me build context graph from tools we use daily
- lead ML specialist w/ exp in custom model dev
dms are open! 🐹
@usehamster's goal isn't merely @taskmasterai 2.0
We'll introduce a next-gen PM approach, Taskmaster-style, for the AI age
We're ditching roadmaps, status updates, sprint planning etc
In exchange for MAX velocity
With AI connecting dots to ship fast
The Hamster Way 🐹
537K Followers 2K FollowingPolyagentmorous ClawFather. Came back from retirement to mess with AI and help a lobster take over the world.
@OpenClaw🦞 + @OpenAI
526K Followers 319 FollowingThe independent award-winning studio behind Baldur's Gate 3 and games in the Divinity universe. Learn more about our upcoming RPG @Divinity.
172K Followers 136 FollowingBuilt by Moonshot AI to empower everyone to be superhuman.
⚡️API: https://t.co/XCrgjXAqMw
@KimiProduct where we share cool use cases.
@Kimidevs built for developers
13K Followers 26 Followingthe typescript framework for building agents
by @calcsam @smthomas3 @abhiaiyer @tonykovanen @wardpeet @tylbar and many others
217K Followers 2K FollowingPractical AI tutorials and interviews to help busy people become AI builders | Join 150K+ readers at https://t.co/XYKTmGVH14
4.9M Followers 4 FollowingOpenAI’s mission is to ensure that artificial general intelligence benefits all of humanity. We’re hiring: https://t.co/dJGr6LgzPA
416K Followers 50 FollowingTypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.