@rauchg — open-agents.dev, a reference platform for cloud coding agents
Today we're open sourcing open-agents.dev, a reference platform for cloud coding agents.
You've heard that companies like Stripe (Minions), Ramp (Inspect), Spotify (Honk), Block (Goose), and others are building their own "AI software factories". Why?
Smart, because the "build your own agent harness" pattern keeps showing up at every serious shop, and none of them want to share the scaffolding. A published reference implementation saves a lot of teams from reinventing the sandboxing, the queue, and the auth layer. The shippable bit here is the code, not the announcement — I'll read the repo before deciding whether it beats just rolling your own.
@realBigBrainAI — Peter Steinberger on why AI agents still produce slop
Peter Steinberger, creator of OpenClaw, on why AI agents still produce "slop" without human taste in the loop:
"You can create code and run all night and then you have like the ultimate slop because what those agents don't really do yet is have taste."
Honestly, this matches my experience. An agent will happily crank out 3,000 lines that pass tests and look plausible, and the whole diff is subtly wrong in ways only a human who's lived in the codebase spots. Taste is still the bottleneck, and I don't see a benchmark for it yet.
@vercel_dev — Claude Managed Agent on Vercel with Workflow SDK
Build a Claude Managed Agent on Vercel that:
- connects to GitHub, Notion, Slack
- securely handles user auth with Vaults
- streams responses via Workflow SDK
Makes sense because the boring parts of shipping an agent — auth to third-party APIs, persisting state across steps, streaming back to the UI — are exactly what Workflow SDK and Vaults handle. Ok… prove it. I'll try the guide against a small internal agent and see how the durable-step model holds up when a tool call hangs.
@ctatedev — adding a terminal to your React app
Adding a terminal to your React app is as easy as
Neat take — in-app terminals are weirdly underused for dev tools and admin dashboards, and most of what's out there is either a heavy xterm.js wrapper or a toy. If the component keeps the PTY semantics sane and streams cleanly over a WebSocket, this is a genuine time-saver. Cool demo — prod is another story, so I want to see how it handles resize, ANSI edge cases, and backpressure.
@pmitu — the actual solo-founder time breakdown
Being a solo-founder:
- 10% coding
- 15% marketing
- 5% operations
- 5% management
- 1% mental control
- 6% UX/UI
- 18% customer support
- 12% sales
- 10% debugging
- 8% product strategy
- 5% finance
- 5% "wtf isn't this working" existential crisis
That's interesting because the coding-to-everything-else ratio is the part no one warns you about. 10% coding plus 10% debugging is 20% of the week — the rest is humans, paperwork, and doubt. Saving this as a pin for the next time I catch myself thinking "I just need to ship the feature."
@hridoyreh — 17 places to launch your startup
Places to launch your startup:
- ProductHunt
- Betalist
- Uneed
- TrustMRR
- Fazier
- OpenAlternative
- Microlaunch
- Peerlist
- TinyLaunch
- SaaSHub
- Indie Hackers
- Hacker News
- Toolfolio
- Tiny Startup
- SideProjectors
- Alternativeto
That's cool because most of these I'd forget exist when a launch week actually rolls around. Keeping the list so next time I ship a side project I don't just drop it on HN and hope. The list cuts off at 17, which is very on-brand for a Twitter post.
