Senior HRBP

Vercel Labs releases fx: A minimalist coding agent written in Zig. Vercel Labs has introduced fx, a tiny, open-source coding agent harness and CLI optimized for performance and embeddability using the Zig programming language. AIDeveloper44 Team fx is designed as a minimalist, Unix-style harness for AI coding agents, prioritizing speed and a small footprint. * Vercel Labs has launched fx, an experimental, open-source coding agent CLI and harness written in Zig. * The tool features a minimal binary size (~6-8 MiB), a 10μs cold start time, and low memory overhead. * It supports WebAssembly (Wasm) for browser embedding and integrates with the Model Context Protocol (MCP). * The interface prioritizes a Unix shell-like experience over complex Terminal User Interfaces (TUIs). Overview of fx: Minimalism in AI Tooling. Vercel Labs has announced the release of fx, described as a "tiny, open, native coding agent." Built as a command-line interface (CLI) and harness, fx is written in the Zig programming language. The project focuses on minimalism, performance, and embeddability, positioning itself as a lightweight alternative to heavier, IDE-like terminal tools. The binary size is remarkably small, ranging from 6.39 MiB to 7.8 MiB depending on the build environment, and it is designed for rapid installation via a single shell script. Design philosophy and performance metrics. The core design of fx adheres to a Unix-like philosophy, emphasizing simplicity and efficient resource usage. According to the technical documentation on GitHub, the tool is optimized for research and for being embedded into larger systems or resource-constrained environments like agent sandboxes. One of its primary technical benchmarks is a "cold start" time of 10 microseconds (μs), achieved by avoiding unnecessary I/O or background processing before the user is prompted for input. Unlike many contemporary AI agents that employ complex Terminal User Interfaces (TUIs) with frequent screen repaints and heavy memory footprints, fx uses a shell-like UI. This approach preserves scroll history and produces minimal output, aiming to feel closer to a standard Unix shell. The memory baseline is reportedly in the single-digit megabyte range, allowing developers to run multiple instances of the agent on a single machine without significant performance degradation. Technical architecture and Zig implementation. The choice of Zig as the primary programming language is central to the project's goals. Zig provides manual memory management and low-level control, which facilitates the creation of small, fast binaries. Furthermore, the Zig toolchain is utilized to produce optimized WebAssembly (fx.wasm) builds. These Wasm builds allow fx to run in browser environments, as demonstrated on the project's official website, where the full CLI runs in-browser with networking delegated to the browser's fetch API. This demo currently supports browsers with WebAssembly JSPI, such as recent versions of Safari and Chrome. Workflow and core features. Users interact with fx through a series of straightforward commands. After installation, the workflow typically begins with fx login to authenticate via Vercel or fx setup to configure an AI Gateway API key. The agent can then be launched within a project directory, which serves as its primary workspace. For one-off queries, the fx ask command allows users to pass a prompt directly from the shell. The agent is model-agnostic, meaning it can be configured to work with various local models, API gateways, or direct provider access. It includes a minimal system prompt and streamlined toolset designed to reduce token costs and improve time-to-first-token (TTFT) performance. For diagnostics, fx includes a /trace command that generates a private Markdown report containing session context, runtime state, and logs, which can be reviewed and redacted before sharing. Extensibility: Skills, MCP, and ACP. Despite its minimal core, fx is designed to be highly extensible. It supports three primary methods of expansion: * Skills: These are reusable sets of instructions that can be linked to specific project scopes. * Model Context Protocol (MCP): fx can connect to external tools and data sources via MCP, a standardized protocol for AI agents. * Subagents: The system can delegate independent tasks to specialized sub-agents. For developers looking to integrate the agent into other software, fx supports the Agent Client Protocol (ACP), which allows the native agent to connect to text editors and other clients. The WebAssembly SDK includes createFxAgent and createFxTerminal functions, enabling the embedding of the core agent or the interactive terminal into JavaScript-based host applications. Security and permissions. Security is managed through a granular permission system. By default, fx starts in auto mode, which requires user review for sensitive actions that have not been previously authorized. The CLI includes commands like /permissions remember to store confirmed rules for specific tools and arguments, and /permissions revoke to remove them. This gives users control over exactly what the agent can modify or access within their local file system. Availability and licensing. Currently in version 0.0.3, fx is explicitly labeled as experimental software. Vercel Labs advises users that frequent changes will be made and the tool should be used "at your own risk." The project is licensed under the Apache-2.0 license, and the source code is publicly available for community contribution and audit. Building the project from source requires Zig version 0.16.0 or higher. References & Sources

Cursor expands beyond its AI editor with origin code hosting. Cursor rolls out origin code hosting service. Image: Cursor Aug 19, 2026 eWeek content and product recommendations are editorially independent. Legal Tech LLC may make money when you click on links to its partners. Learn More Cursor is giving developers another place to put their code as it takes aim at GitHub with its new Origin hosting platform. Origin began rolling out in early beta on Aug. 17 to users on all paid Cursor plans, except enterprise organizations whose administrators opt out. Available through the desktop app's new Codebase tab and a command-line interface, the service lets developers create repositories, browse code, and manage pull requests. The launch was Cursor's first major product release since SpaceX completed its $60 billion acquisition of Anysphere, the company behind Cursor, on Aug. 14. Cursor announced that it is "starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync." Rather than forcing teams to immediately abandon their existing infrastructure, the service uses a bidirectional bridge. "Your GitHub repos can sit alongside the ones Cursor hosts," Cursor wrote in its launch documentation. "Pushes keep going to GitHub, which stays the source of truth for anything started there." To maintain continuous integration and deployment workflows, Cursor debuted integrations with Vercel, Depot, and Buildkite, allowing teams to execute existing GitHub Actions workflows unchanged. Architectural pressure in the agent era. Origin's rollout arrived on the same day GitHub suffered a major service degradation lasting over 7 hours, disrupting pull requests, enterprise authentication, and Copilot. The incident followed eight service disruptions reported by GitHub in July, adding to concerns about the platform's recent reliability. GitHub Chief Technology Officer Vlad Fedorov previously acknowledged in an engineering post that the platform had failed to meet its availability standards, writing that "recent platform instability was primarily driven by rapid load growth." Traditional platforms like GitHub were created around human workflows, but autonomous software tools are altering repository traffic patterns. According to data reported by RuntimeWire, autonomous agents running in cloud virtual machines now generate 35% of all pull requests merged within Cursor. Origin is engineered to handle machine-speed commits and automate merge conflict resolutions when multiple agents edit identical files simultaneously. The transition of AI coding assistants into fully fledged hosting providers signals a structural shift in developer infrastructure: software development environments and version-control backends are consolidating into a single layer. By unifying the code editor, autonomous execution agents, and code storage under SpaceX's corporate umbrella, Cursor is constructing a vertically integrated software supply chain. While this closed feedback loop enables automated code testing and immediate agentic fixes, it also concentrates core developer tooling within one proprietary ecosystem. A chance for new code-hosting players. Origin could create major opportunities for developers and competing code-hosting companies that want to challenge GitHub's dominance. Cursor's biggest advantage is that it already controls the environment where many users write and review code. Bringing hosting into that workflow could reduce the friction between generating code, reviewing it and deploying it. But Origin still faces major hurdles. GitHub has a huge installed base, deep enterprise integrations and years of accumulated developer trust. Early-beta software also carries reliability, security and migration risks that mature infrastructure has already had time to address. For businesses, the sensible approach is to test Origin alongside GitHub rather than immediately replace an established source-control system. Cursor's synchronization model makes that possible while the company proves whether its agent-focused approach can deliver a meaningful advantage. Read more: Cursor 3 turns the editor into a unified workspace for AI coding agents, providing more context on the agent-based workflows that Origin is designed to support. Aminu Abdullahi is a B2C and B2B technology and finance writer with more than six years of experience covering enterprise IT, cybersecurity, cloud computing, artificial intelligence, fintech, business software, and emerging technologies. His work has appeared in publications including TechRepublic, eWEEK, Channel Insider, Geekflare, Enterprise Networking Planet, eSecurity Planet, CIO Insight, and Webopedia. With a technical background in computer science, he specializes in translating complex technology topics into clear, accessible content for business leaders and decision-makers.

Vercel launches v0 API for headless app building. * Daniel Dominguez Software Product Manager | Machine Learning Specialist Follow InfoQ on. Vercel has made the v0 API generally available, providing programmatic access to its AI-powered application-building agent. Developers can send prompts through the API, have v0 generate and modify application files, run the resulting app in a Vercel Sandbox, and receive a preview URL that can be embedded into their own interfaces. The API organizes each application around a chat that maintains the app's current state. Developers can send follow-up messages using the same chat ID, allowing v0 to continue editing the existing application. The API supports synchronous, asynchronous, and streaming requests, with streamed responses exposing individual agent actions such as file reads, edits, searches, Bash commands, and tool calls. Applications can also be created from existing GitHub repositories, ZIP archives, or sets of files. When the app is ready, developers can attach a Vercel project and deploy it through the API. Preview environments use short-lived tokens and can be accessed through a server-side proxy, keeping the v0 API key out of the browser. The API also supports external tools and design systems. Developers can connect MCP servers or load skills from team or user memory, skills.sh, or a connected repository. Up to three skills can be passed to a request. Vercel also provides integrations for using v0 as a tool inside other AI agents through MCP, the AI SDK, or Vercel's eve framework. This positions v0 differently from application-building tools such as Lovable and Bolt, which primarily provide interactive environments for generating applications. The v0 API instead exposes the application-building agent as infrastructure that developers can invoke from their own products, scripts, CI pipelines, or other agents. Vercel's approach also integrates the generated application directly with its Sandbox and deployment APIs. Community reaction has focused on the potential for the API to support fully programmatic application development. AI influencer ZenithAI described the release as: A powerful step toward fully programmatic app development workflows. Vercel developer @EstebanSuarez highlighted the intended agent workflow, explaining that an agent can send a prompt and design system to the v0 API, receive a live preview in a Vercel Sandbox, iterate on the application, and deploy it when ready, posting: Your agent needs an app. It sends a prompt to the v0 API along with your design system. Back comes a preview URL: the app live in a Vercel Sandbox. Your agent iterates on it. When it's ready, it deploys. That's the new v0 API. The new API is available through the v0 SDK, with the v2 API using https://api.v0.dev/v2. Developers can create an API key, install the SDK, and build interfaces that send prompts, stream agent activity, render previews, and deploy generated applications. Daniel Dominguez. Daniel is the Managing Partner at SamXLabs an AWS Partner Network company. He has over 13 years of experience in software product development for startups and Fortune 500 companies. Daniel holds a degree in Engineering and a Machine Learning specialization from the University of Washington. He is passionate about leveraging AI and cloud computing to create innovative solutions. As an AWS Community Builder in the Machine Learning tier, Daniel is committed to sharing knowledge and driving innovation in software products. Related sponsors. A round-up of last week's content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example