Sam Cui

Trellis just crossed 10,000 stars! For most of last year, our team ran Claude Code hard and tried just about every workflow the community shipped — OpenSpec, plan-with-files, Superpowers — and none of them held up in real development. They're PRD-driven at heart: every new task, you rewrite the same architecture rules, naming conventions, and error handling from scratch. They struggle with anything project-specific, and even the custom rules you do define often never fire, lost to hallucination. So we built Trellis. The name comes from a garden trellis: we wanted to give code a structure — something that lets it grow fast while keeping its direction under control. We believe the better paradigm is Spec-Driven: using hooks to lock your hard-won engineering standards and workflows into every session, so parallel development and team collaboration finally feel smooth. From the first release, to the architecture overhaul in 0.5, to 20 back-to-back betas in 0.6 — across more than a thousand commits, we've reached this milestone hand in hand with you. Thank you to everyone who sat down with us for interviews, sent feedback, opened PRs, and helped answer other people's questions in the community. Thank you for backing us this early, while the product is still far from finished. Next, we're going after a new paradigm for how AI-native teams build software together — and on everything we've learned from Trellis, we intend to craft a product that truly earns the trust you've placed in us. Our story is just getting started.

the divide at work isn't senior vs junior anymore. - who trusts the agent with real work - who still reviews every line out of fear - who ships 5 things, reviews 5 things - who's "too experienced" to pick up the new tools seniority used to be the moat. now it's adaptability. agree?

nobody tells you this about AI at work: the reward for doing your job in half the time isn't half the hours. it's twice the scope.

@pmitu competition keeps you sharp, nothing wrong with that

Don't be scared of competition. Get inspired instead.

signs you're quietly turning into a loop engineer: - you spend more time on the prompt than the diff - you're debugging how it decides, not what it wrote - you wrote a prompt whose whole job is writing prompts - you haven't hand-typed real logic in days - your "code review" became "process review" promotion, or trap?

@VladtTysia fun challenge! curious what stack you're using

@35Kapc Building an ultra-low latency jam room right in the browser

Hey founders, Looking to connect with people building in: - Saas - Tech - Automation - Ai tools - Web apps - Developer tools What are you building?

@zdogmode Done!

@35Kapc Let’s do it

@sdotboro hey! always down to connect with fellow builders

@35Kapc Hey Sam! Lovely to meet you. Let’s connect!

@TTrimoreau resilience. everything else can be learned or hired.

What's the #1 skill every entrepreneur need to have ?

This is your sign to never give up.

@sflorimm maybe they're just not telling you

Haven’t met anyone working less after adopting the AI.

@elonmusk @teortaxesTex won’t take that long

@mobailabs the real tax is when both agents think they're right and you're stuck reconciling two valid but incompatible futures

@35Kapc git worktrees per agent solves the file overlap. but the sneakier tax is divergent decisions — two agents refactor the same module differently and now you're merging two futures into one

Running five Claude Code sessions at once feels like five times the output. The tax nobody mentions: every time you switch back, you reload the context in your own head, not the model's. That's where the speedup quietly leaks.

@0xSero curious how much headroom is left in compression with more compute. feels like we're hitting diminishing returns but hope you prove otherwise

I'm spending 7k USD to make the best GLM-5.2 compression there ever was. Let's see how much better extra compute can make it. I am a huge believer in REAP / REAM / Ternary models and quantisation. If we're going to have an equal playing field compression has to get better.

🛠️ Agent Reach — give your agent internet access without the API-key tax Your agent can write code, edit docs, run your project. Then you ask it to look something up online and it just whiffs. Reading a tweet, a Reddit thread, a YouTube transcript used to mean picking your poison: pay for each platform's API, fight the rate limits and logins, and babysit the scrapers every time they break — or paste it all in by hand. Agent Reach turns that into one command. One CLI, no API keys, no billing. It ships with whatever access method actually works for each platform right now and swaps it when things change — so you're not the one patching scrapers at midnight. What your agent can suddenly do: > pull YouTube + Bilibili transcripts and summarize them > search Twitter, Reddit, and GitHub — no keys, no bill > open a page and get clean text back, not raw HTML Trending on GitHub at 34.9k stars, MIT. An agent that can't see the internet is half an agent. github.com/Panniantong/Ag…

things that quietly kill your "five agents at once" speedup - forgetting what agent #3 was even doing - re-reading scrollback to find your own decision - two sessions that both edited the same file - the one you left "almost done" two hours ago - switching faster than any of them actually finish what's your real ceiling?

@theohandsh all of the above, but distribution is the one that's hardest to fake

AI is rapidly reducing the barrier to building software So what will separate the winners from everyone else? Product? Distribution? Brand? Community? Data?

@Dwriteway it compounds way faster than any title ever will

One digital skill can take you further than any job title ever could.

Enjoy $200 coding plans while they still exist. These subsidies from model providers likely won't last forever. Thoughts?

@DanielSmidstrup network effects + a team that genuinely loves the problem

what actually makes a startup impossible to copy?