Tag: Ai-Agents

29 posts

Why We Run AI Agents on Suspendable MicroVMs

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.

Vitaly Nikitin
Your AI agent got stuck for five hours. Nobody noticed.

Your AI agent got stuck for five hours. Nobody noticed.

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.

Vitaly Nikitin

The hardest part of AI agents isn't coding anymore. It's the ops.

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.

Vitaly Nikitin

Now Claude Code has workflows too. Here's how Forge's are different.

Two days ago Anthropic shipped Dynamic Workflows in Claude Code — Claude writes an orchestration script that fans out hundreds of subagents, with adversarial verification. It's genuinely good. But it's ephemeral, model-authored, code-centric task orchestration. Forge is a durable, human-governed, audited team workflow. Here's the honest difference.

Vitaly Nikitin