Linzumi
Linzumi is a Y Combinator (Spring 2026) company in San Francisco building a Slack-shaped team chat that runs a fleet of AI coding agents inside every channel. Engineering teams kick off work, watch agent activity in real time, review output, and ship code without leaving the thread. Unlike sandboxed cloud agent products, Linzumi runs agents on the developer's own machine through a local "Commander" runner installed from the @linzumi/cli npm package, so agents work against real environment variables, dotfiles, and branches inside explicitly trusted folders. The product adds a decision inbox that surfaces only the choices needing a human, continuously compiled team context, git safety snapshots taken before each agent turn, and a bundled local MCP server that lets coding agents read scoped Linzumi message, thread, and channel context. It supports OpenAI Codex today with Claude Code announced as coming soon. The service is in beta via a macOS desktop app and a web workspace; there is no public developer API program, documentation portal, or published OpenAPI at this time.
Linzumi publishes 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Developer Tools, Coding Agents, and Team Chat.
Linzumi’s developer surface includes support, CLI, authentication, changelog, and 11 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Linzumi Runner API
The private product API behind the Linzumi web workspace and the local Commander runner, served from serve.linzumi.com under a /api/v2 URI-versioned path. It is not a published ...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
linzumi-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type