
Builder of https://xitter.cf/t.co/VcqRWpR5yf @Vercel
Vercel
Joined January 2025
- Tweets416
- Following166
- Followers2K
- Likes391
I’ve spent the past four months building fx. We’re open sourcing it today.
I cared most about making it fast, small, and easy to embed:
10µs cold start
6.3 MiB native binary
single-digit megabytes of memory at baseline
structured output, ACP, and WebAssembly
Getting fx to this point has been a great experience, especially working closely with @EstebanSuarez and @rauchg and being mentored directly by both of them.
Try it and give us feedback. Join the X group chat for updates and a closer look at how we’re approaching fx and where it’s headed:
fx.sh/xchat
fx.sh/
Introducing fx, a tiny, open, native coding agent from Vercel Labs.
Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it.
fx is built on three principles:
1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?"
2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes.
3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP.
Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms.
You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: fx.sh/try).
Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic.
fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X (fx.sh/xchat) or file issues (fx.sh/issues).
𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑
fx.sh/
Last week we made fx durable. Today we're giving you the sauce.
`durable-harness` makes any harness durable: Pi, Claude Code, Codex, OpenCode, or one you built yourself.
Kill the function mid-turn and the agent picks up where it left off.
vercel.com/blog/making-every…
Introducing 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜. Run Pi, OpenCode, Codex, Claude Code, eve, fx, or your own harness durably on Vercel.
With 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜, agents automatically resume work after failures and run for hours, days, or months. vercel.com/blog/making-every…
Last week we introduced libfx durability. This week we put it into a template to show what it can do.
fx0 is fast and durable out of the box.
Give it a try for free, on us.
fx0.vercel.dev
We built a 'mini v0' on libfx to showcase its speed and durability:
• Design or prototype anything in seconds
• 200+ models from Vercel AI Gateway
• Outputs are pure HTML artifacts
• Fork it & make it your own
Try it free ↓ fx0.vercel.dev
fx v0.0.14
libfx is now durable out of the box. Same API on local, Vercel and DIY.
- Sessions survive crashes, redeploys & timeouts
- Power cloud agents with ChatGPT & Grok subscriptions
- Custom providers & local model support in libfx
- Run multiple libfx agents in one app
- More control over each libfx session
- TypeScript types for libfx's public APIs
- Ported to Zig 0.17
- Multiple bug fixes & security improvements
fx.sh/changelog#v0.0.14
wanted this since we started fx but oh well 🎨
fx.sh now supports themes.
Bring any VS Code theme or make your own, drop it in ~/.fx/themes and pick it in your settings.
fx.sh/docs/configure-fx/conf…
Simpler the better.
Coding CLIs keep getting more complicated. Daemons, 3 layers of TUIs, client-server architectures.
The whole point of a CLI is to deliver intelligence with zero friction, and be unix-like.
💾 Try fx.sh. It's 6mb, starts in milliseconds, model-agnostic. It's tastefully minimal: MCP, Skills, Subagents and ACP built-in.
So good 🤌🏻
fx v0.0.13
Ultrafast support. Faster launch, shell calls & exits.
• Ultrafast for supported OpenAI models
• Launch up to 23× faster
• Shell calls up to 8.6× faster
• Exits up to 44× faster
• Configurable automatic compaction
• Multiple bug fixes & security improvements
fx.sh/changelog#v0.0.13
fx v0.0.12
Faster sessions. Better Markdown. More reliable long running work.
• Session listing up to 560× faster
• Large session stores resume instantly
• Better GitHub-flavored Markdown
• Better scrollback, steering & session recovery
• Improved MCP reliability & security
• Multiple bug fixes & QoL improvements
fx.sh/changelog#v0.0.12
fx v0.0.11
Local models. Custom themes. Faster sessions. libfx improvements.
• Connect local models and OpenAI-compatible gateways
• Load custom TUI themes from theme.json
• Resume, file lookup & request handling up to 100× faster
• Long tool-heavy turns use 17× less memory
• libfx adds steering, images, web search & model controls
fx.sh/changelog#v0.0.11
🚀@vercel's’ fx is a tiny open-source coding agent built to take action directly in a developer’s workspace. This demo extends that idea by giving fx access to the security policies, requirements, and release docs stored in Box.
Using the Box CLI, fx retrieves an approved policy, compares it with local code, edits the files, adds missing test coverage, and prepares release evidence without being told which lines to change. It asks for human approval before uploading anything, then verifies every file after it lands in Box.
Git stays where the code lives. Box stays where the approved docs and release proof live. fx connects the work across both.
Demo below ↓
Pranit retweeted
New experiment: json-render + jev
The future Generative UI is instant
Your components, your actions, your design system
Rendered in milliseconds










