Got a new Shopify app idea. - sent 200 DMs - got 20 positive responses - going to build in 48hrs this weekend and live tweet it #buildinpublic #appchallenge

We got our first customer on Roughcut, zero to 1 ✅ 1 to 10 ⏳

Mat made a video for his startup by hand. then the replies started. "what tool is this" "what'd you use" There was no tool, so he jokingly told me to go build one I took it litterally, say hi to Roughcut 👇 comment "VIDEO" and i'll DM you the beta link

This is just amazing

Claude weekly limit already at 53%, I've been using Fable for a day...

Fable made me the most productive I've ever been in a while. Haven't had this feeling in a long time!

Look at all the cool stuff you can do with grok CLI! Can't wait to use it

Grok CLI just came out, The terminal UI looks sick, what took you guys so long ?

I was wondering when a new model might come out. I know what i’m doing this weekend

Started seeing this: § A lot more in AI generated responses. Is it the new — ?

I got tired of losing sessions when I accidentally closed my terminal. So I created this: Auto-resume claude code sessions. Per-pane isolation, per-project isolation so multiple sessions in the same dir don't clobber each other. gist.github.com/Crunchyman-r…

Sign the Bring Back Buddy petition, i miss Glitchaxl github.com/anthropics/claude…

RIP buddy, bring him back

I like my new buddy, makes me feel like I'm pair programming, drop your buddy in here!

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!

We're so back baby. But for how long ?

Opus on 1M token is really hard to attain, I find myself often finishing at like the 50% mark lol