Pi
Terminal-first, MIT licensed, and provider-agnostic with custom OpenAI-compatible endpoints. The next port after OpenCode, with a TypeScript extension API and a much smaller codebase than an IDE fork.
Terminal · MIT · provider-agnosticSame DeepSeek model. Same license. Same sponsor panel. We're porting the Freebuild sponsored plan terminal-first. Pi is next. Crush is in license review. IDE and web ports come later.
Founding beta members get early access to every new port.
Terminal first. Pi is next. Crush is in license review. Kilo Code, Cline, and OpenHands come later. The waitlist tells us where to go after that.
Terminal-first, MIT licensed, and provider-agnostic with custom OpenAI-compatible endpoints. The next port after OpenCode, with a TypeScript extension API and a much smaller codebase than an IDE fork.
Terminal · MIT · provider-agnosticVS Code and CLI, built around an OpenCode-compatible provider model. An IDE-first port for later, after the terminal work.
VS Code · CLI · IDE-firstOpen-source VS Code and JetBrains agent with custom OpenAI-compatible providers. A larger IDE fork, so it comes after the terminal ports.
VS Code · JetBrains · IDE-firstOpen-source web agent with model-agnostic LLM support. A later non-terminal surface.
Web · self-hosted · model-agnosticYour Freebuild license and broker budget should follow you across ports. One account, one plan, no second provider key.
The same model and thinking levels, with the same 50M weighted-token monthly budget and metering.
The sponsor panel stays mandatory, stays beside the agent, and still counts one impression per agent run.
Pick the agents you use. We’ll send a confirmation email now, then one launch email per port. No spam, no sharing, unsubscribe anytime.
One click confirms your notification request.
Crush, Codex CLI, and Claude Code each need more than a config change. Crush needs a commercial license review. Codex needs a Responses frontend. Claude Code is Anthropic-only.
Terminal-native and already in the Freebuild stack, but the FSL license restricts competing commercial use. We are reviewing the terms before a paid port.
Uses the Responses API for custom providers. The broker would need a Responses frontend before the port is useful.
Uses Anthropic Messages and only exposes hooks/statusline for UI. The adapter is possible, but the sponsor panel would be a downgrade.
Google’s consumer access changed in 2026 and the CLI is moving toward Antigravity. Not a first-port target.
If your agent has a custom OpenAI-compatible endpoint and a place to render a persistent panel, it can probably run Freebuild. Send us the name and the extension surface.
That’s the goal: one license, one broker budget, and one sponsor panel across every supported agent. We’ll confirm the details when the first port ships.
No. The Freebuild broker keeps the model key server-side. You connect the same Freebuild license to each supported agent.
Yes. The Sponsored plan is funded by the panel. There is no ad-free tier, and the panel still counts one impression per agent run.
You submit your email, confirm it from the email we send, and choose the agents you care about. We send one launch email per port. Every email includes an unsubscribe link.
Join the launch list. The agents with the most interest move up the queue.