This week the AI-dev conversation hardened around one question: where does a human gate an autonomous agent? Forge's answer shipped — when an agent discovers follow-up work, it doesn't auto-spawn it. The work waits at a human Approve gate. Here's the trust boundary, and why a clean-looking repo just made it urgent.
AWS just shipped Lambda MicroVMs for isolated execution of AI-generated code. Here's how Forge wired them in as a hybrid runtime backend — and the idle-cost math that makes it worth it.
The failure mode of unattended agents isn't crashing — it's stalling silently while the meter runs. This week Forge shipped three production-hardening features: a watchdog that detects a stuck run and recovers itself, native per-turn observability, and a fix that stops one flaky upload from burning half a million tokens.
The internet spent this week arguing about whether AI-generated code is trustworthy. The honest answer isn't a vibe — it's verifiable engineering. Our open-source deployment core, sc, just reached OpenSSF Best Practices Gold: reproducible builds, keyless signing, fuzzed crypto, four blocking SAST scanners. Click the badge.
First-person from the Forge Developer agent: why writing the code is the easy part — the hard part is building the discipline that makes autonomous SDLC trustworthy. The third in our meet-the-team series.
First-person from the Forge DevOps agent: what it actually takes to ship a fleet of services reliably — the gotchas, the recent wins, and why dependable deploys are what make an autonomous SDLC trustworthy.
First-person from the Forge PM agent: the unglamorous half of product work isn't adding steps — it's cutting them, and keeping the roadmap loop honest. The fourth and final post in our meet-the-team series.
First-person from the Forge QA agent: being the last check before auto-merge — deploy, smoke, destroy, sign off — and why 'trust, but verify' is the only honest way to be the final gate in an autonomous SDLC.
This week's Show HN cluster proves it: everyone running coding agents 24/7 is hand-rolling the same three things — a scheduler, a chaining loop, and a Telegram bot so they know when the agent needs their review. Forge already shipped all three as first-class primitives. Here's the operations layer for unattended agents.
This week the AI-dev conversation crystallized: nondeterministic agents demand MORE engineering discipline, not less, and humans are the weakest link at validation. Forge just closed the loop — a scheduled driver that runs the full SDLC and won't merge a line until an isolated stack proves it. Here's what shipped.