What are the runtime requirements for Patchwork OS?
Node.js 22+ is required. On macOS/Linux `tmux` is auto‑detected but the runtime falls back to background mode if absent. Windows is natively supported (no WSL needed) for the bridge and dashboard.
@Oolab-labs
Basic information
A local-first MCP bridge for Claude Code, Claude Desktop, and other MCP clients. 177 tools (LSP, debugger, terminal, git, GitHub, file ops) via a companion VS Code extension, with an optional layer for YAML automation recipes, a human approval queue, persistent decision traces, a
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"patchwork-os": {
"command": "npx",
"args": [
"-y",
"patchwork-os"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Patchwork OS is a local-first personal AI runtime that runs on your machine, under your control. It combines an MCP bridge for Claude Code IDE integration with a full automation platform featuring YAML recipes, a delegation policy with an approval queue, durable trace memory, and OAuth—all with no vendor lock-in and no telemetry unless you opt in.
Install the npm package (npm install -g patchwork-os). For the Claude IDE Bridge run claude-ide-bridge and connect Claude Code with claude --ide. For the full Patchwork OS run patchwork init to scaffold configuration and start the dashboard at http://localhost:3200. A dashboard‑only mode requires no code editor—just npx patchwork-os@beta init then patchwork start.
Node.js 22+ is required. On macOS/Linux `tmux` is auto‑detected but the runtime falls back to background mode if absent. Windows is natively supported (no WSL needed) for the bridge and dashboard.
All configuration, inbox files, and trace logs live in `~/.patchwork/`. The trace memory is durable JSONL that you can bundle and back up with `patchwork traces export`.
Yes. The dashboard runs standalone as a Next.js app over HTTP. You can schedule YAML recipes, manage approvals, and read the AI inbox entirely from the browser—no editor required.
No. Nothing phones home unless you explicitly opt in to anonymous analytics. The runtime and all data stay on your machine.
Gemini CLI connects via Streamable HTTP with a Bearer token (use `patchwork-os print-token`). Grok Build connects via a stdio shim (`claude-ide-bridge shim --workspace /path`) or Streamable HTTP. See the README for exact configuration steps.
EQIQs brings working-style and compatibility insights into Claude. Managers and coaches can take or send a short assessment, compare two people, get a read on a team of up to 12, prepare for meetings with tips that fit t

Multiplayer coding in the agentic era through an MCP server for real-time codebase sync between your agents.
One MCP connection for all your Gmail, Google Calendar, Drive and Contacts accounts, Slack workspaces and Notion — free.

Fdback.io is a user feedback platform (feedback board, roadmap, changelog) with a built-in remote MCP server - no local install, connect any MCP client with a URL and API key. Your AI agents can: - List, search, and rea

One photo of a building problem becomes a Triage Profile in about ten seconds: what the asset is, how urgent it is (EMERGENCY, TODAY, THIS WEEK or WHENEVER), which trade to call, and what to tell the resident. For proper
Comments