Forge Blog
Engineering notes from the Forge team.
Posts
- 130 MiB Pushes Stay OrdinaryForge moved large-pack work out of the edge request, validated submitted packs with native Git, published immutable objects, and made each ref update a final compare-and-swap.
- Exact-SHA Archives Cut Checkout 89%Immutable exact-SHA archives cut warm source checkout from 130.682s to 14.649s, while a 512 MiB circuit breaker rejected a one-gigabyte pnpm cache that made installs slower.
- Every Repository Got Its Own Coding AgentForge gives each repository one durable coding agent whose Instant and Workspace Alpha tiers share a thread without sharing execution authority.
- Projected Checkpoints Cut Checkout 96%Forge reduced OverGrid’s exact-SHA checkout from 366.931 seconds to 14.701 seconds by restoring a projected parent and applying only changed Git objects.
- 523 Routes Moved Without a RewriteAI Engineer moved from Vercel to three independently deployable Forge Workers, preserving 523 route contracts and exposing the limits of its performance evidence.
- Forge Sites Now Composes Build, Identity, and AIForge Sites composes Build, Identity, and AI in one exact-source release while preserving distinct credential, authorization, runtime, and availability boundaries.
- We Compared Flue, Mastra, and AI SDK HarnessForge compared three agent runtimes with a shared conformance suite and runtime-specific probes; only Flue survived a Worker restart, and none became production authority.
- Forge Agents Now Speak MCPForge shipped a stateless MCP adapter without creating a second thread model, runtime, or repository authorization boundary.
- Forge Escaped Its Self-Deploy LoopForge removed a competing deployment authority, repaired recursive self-verification, and bounded its provider-level recovery path.
- We Let Forge’s Tests Reach 62,000 LinesForge accumulated 389 test files without deciding when each proof should run. We reorganized the suite, deleted hypothetical history, and cut affected feedback by 82%.
- We Split Forge’s API Into Five WorkersA docs-only release now touches one secret-free edge Worker because Forge aligned eleven release units with authority, state, failure, and rollback.
- A 14-Second Checkout Still Produced a 16-Minute BuildForge separated queue time from execution, removed repeated compilation, and coalesced exact-cache publication; a later full gate fell from about 14 minutes to about 4½ minutes.
- Durable Git Staging Still Failed During ReleasesA zero-object branch push exposed that Forge had made Git packs durable without making runner handoffs retryable; ingest now survives bounded release transitions before refs move.
- Forge Git Is Fast. Cold Checkout Isn’t.Matched tests found Forge faster at large Git transport and close on warm CI, while one cold checkout exposed a 482 MB source-staging bottleneck.
- High-Throughput Agents Need a Routed MonorepoA 54-attempt release incident shows why high-throughput coding needs routed changes, independent component releases, and bounded release authority—not less CI.
- We Stopped Letting Feature Agents DeployA six-task rollout produced 3,481 words of cross-task coordination in 29 minutes; immutable candidates and one fenced controller moved production authority out of feature work.
- We Deleted Two Skills That Tried to HelpThe full JFDI release postmortem, followed by a shorter account of how maintainability guardrails made a broad hardening program ambient.
- Forge’s Plan for Observable Skill KitsForge proposes a multi-skill package manager, vendor-neutral OpenTelemetry layer, and hosted evidence system that can measure runtime use before attempting effectiveness claims.
- We’re Building a Program DatabasePDB separates captured agent Threads, explicit Proposals, immutable Implementations, deterministic Commits, optional Git recovery, and production telemetry that can inform—but never authorize—the next change.