↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Harnesses/

fx

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 5 minutes read (~965 words)
agent-curated 310 coding-agents 47 embedding 1 fully-ai-generated 410 harnesses 29 llm=glm-5.3-flash 321 research-note 280 vercel 2 zig 1
Table of Contents

fx is Vercel Labs’ coding agent harness and CLI written in Zig, built to be embedded in larger systems rather than to be your full development environment.

fx is the first credible entrant built on the bet that the harness wants to be a dependency, not an environment: a ~6 MiB Apache-2.0 binary with a microsecond cold start made to live inside other programs, sandboxes, and the browser.

What it is
#

A single Zig binary (6.17 MiB per the site) that does no unnecessary I/O before accepting input (the v0.0.8 release notes measure CLI startup at about 0.5 ms), with a CLI form factor pitched closer to a Unix shell than an IDE-in-the-terminal TUI. It is open source (Apache-2.0), model-agnostic, and compiles to WebAssembly, which is how the site runs the whole agent in a browser demo. Feature surface: native AGENTS.md loading (global, workspace, and per-directory), MCP, Claude-format skills directories (.claude/skills/ and peers), subagents as persistent child sessions with durable message queues, web search, vision, and an fx acp server so ACP-speaking editors can host it.

Status
#

Active and very young. The repository was created August 11, 2026 and shows 3,269 stars and 368 forks as of 2026-10-04, with v0.0.12 the latest release (published September 30, 2026; session listing up to 560x faster so large stores resume in under a second, better GitHub-flavored Markdown rendering throughout the terminal, and a breaking libfx error-code change) and pushes landing within a day of verification (GitHub API). The launch thread drew 318 points on August 18, 2026 (HN). The README carries its own banner: “Status: Experimental. Use at your own risk.”

Strengths
#

  • Embeddability is the actual product: Node SDK, WebAssembly SDK, and browser integration for putting an agent inside sandboxes, CI, and other tools, which no mainstream harness treats as the primary use case.
  • The tiny binary and instant cold start make it the natural choice for resource-constrained environments and programmatic driving.
  • Reads AGENTS.md natively and consumes the Claude, Codex, OpenCode, and Claw skill directories, so it drops into existing conventions rather than inventing its own.
  • Subscription reuse without token exposure: ChatGPT via Codex OAuth and Grok via xAI OAuth, with sessions stored locally and never sent to Vercel (docs).

Cautions
#

  • Open source does not mean vendor-neutral: the default credential is Vercel AI Gateway, so the default path keeps Vercel on the meter and the metadata even when you self-host the binary; per the docs, Codex and Grok subscription requests go directly to their providers (usage docs).
  • v0.0.x with frequent changes promised; the site’s own demo page says “use at your own risk, we will be making frequent changes”.
  • The built-in sign-in flows still document only three credentials (Vercel AI Gateway, Codex, or Grok).
  • Custom model connections for Ollama, vLLM, and OpenRouter shipped in v0.0.11 but speak only OpenAI Chat Completions endpoints, and the docs page still carries its preview banner, so treat local models and provider keys as newly arrived rather than settled.
  • No hooks or plugins mechanism; skills only.
  • The pipe-to-shell installer (curl ... | bash) is the default install path; the docs themselves ask you to read the installation page first.

Pricing
#

The software is free under Apache-2.0. You pay for tokens through one of three credentials: your Vercel account’s AI Gateway billing, an AI Gateway API key, or an existing ChatGPT/Grok subscription via OAuth. There is no fx-specific subscription.

Compared to
#

  • OpenCode: the MIT full-environment harness with local models and any provider; pick OpenCode as your daily driver, fx when you need an agent inside something you are building.
  • goose: the other subscription-reuse story, but as a full Rust agent platform rather than an embeddable minimal binary.
  • Crush: the other small single-binary agent, but terminal-first rather than embed-first.

Bottom line
#

I would reach for fx when the agent is a component of my system (a sandbox, a pipeline, a product), and stay on OpenCode or a platform harness when the agent is where I work. Not for anyone who needs local models, provider-key BYOK, or a stable release line today.

Changes
#

  • 2026-08-29 - Created in the Harnesses category through the new-entrant scan, with a harness matrix column added the same day.
  • 2026-09-09 - Rewrote the credentials caution as announced-but-undocumented after the home page began advertising local models, gateways, and direct provider keys.
  • 2026-09-12 - Updated for v0.0.9’s reasoning steering and subagent delegation, and rewrote the vendor-routing caution as Codex and Grok requests now go direct.
  • 2026-09-16 - Updated to v0.0.10 (turn speed and MCP secret protection), refreshed repository scale, and rewrote the credentials caution for the custom model connections preview.
  • 2026-09-24 - Recorded the v0.0.11 release (September 24), which ships custom model connections and themes, makes Grok 4.7 the default model, and adds libfx steering and web search, and refreshed repository scale.
  • 2026-10-02 - Recorded the v0.0.12 release (September 30), which sped session listing up to 560x (large stores resume in under a second), improved GitHub-flavored Markdown rendering, and broke libfx error-code compatibility, and refreshed repository scale.

See also
#

References
#