Beyond the Chatbox: Introducing Polypore

~~Agentic coding is just a plugin for VS Code.~~ Agentic coding deserves its own first-class environment.

Polypore is a modular desktop IDE specifically engineered for an era where AI agents are the primary actors in the development process. Rather than bolting a chat interface onto a legacy editor, Polypore treats the agent as the central orchestrator.

🛠️ Technical Foundation

Polypore is built for speed, privacy, and flexibility. It is released under the MIT License and contains zero telemetry.

Component	Technology
Shell	Tauri 2 (Rust)
UI Framework	React 18 & Vite
Layout Engine	Dockview
Code Editor	Monaco
Terminal	xterm.js & portable-pty
Database	SQLite (via `rusqlite`)
Secrets	OS Keyring (`keyring` crate)
Communication	JSON-RPC & JSON Schema

🚀 Getting Started

Installation

Depending on your OS, download the latest release:

Linux: .AppImage (requires fuse2 on Arch), .deb, or .rpm.
macOS: .dmg (Intel or Apple Silicon).
Windows: .msi or .exe (x64).

Linux Execution Tip:

chmod +x Polypore_*_amd64.AppImage
./Polypore_*_amd64.AppImage

Building from Source

Prerequisites: Node 20+ and Rust stable (installed via rustup). Linux users also require: libwebkit2gtk-4.1-dev, libgtk-3-dev, libayatana-appindicator3-dev, and librsvg2-dev.

Common Commands:

npm run app $\rightarrow$ Launch the Tauri desktop app.
npm run dev $\rightarrow$ Start the Vite renderer on 127.0.0.1:1420.
npm run mcp $\rightarrow$ Run the MCP sidecar in the current directory.
cargo test $\rightarrow$ Execute Rust-level tests.

🧩 Modular Architecture

The core philosophy of Polypore is that the AI ecosystem evolves faster than traditional IDE release cycles. Consequently, every component is swappable.

"Any piece of the IDE can be swapped, extended, or dropped without touching the core."

The Panel System

The UI consists of dockable panels that can be split, reordered, or closed. You can access these via the + tab:

Panel	Purpose
`claude`	Claude CLI with slash-command integration.
`codex`	Codex CLI with slash-command integration.
`preview`	Live output (Browser, CLI, or Dev Server).
`editor`	Monaco editor featuring project-specific diagnostics.
`diff-stack`	Side-by-side diffs with a scrubbable history.
`terminal`	A standalone pty terminal.
`debug`	Diagnostics and verification run management.
`memory`	Project knowledge base utilizing `[[wikilinks]]`.
`agent`	The hub for skills, MCP management, and secrets.

Extensibility & Plugins

Third-party panels are implemented as sandboxed iframes. By adhering to the HostRpcServer contract, developers can drop a plugin into .polypore/plugins/[id]/ and have it appear instantly. Agents can interact with these plugins via the MCP server.

🤖 Agentic Orchestration

Polypore provides a Node-based MCP (Model Context Protocol) sidecar that grants agents direct control over the IDE through 22+ specialized tools.

MCP Tool Namespaces

polypore.debug.*: Manage breakpoints, step through code, and capture DOM/Network/Console logs.
polypore.memory.*: Interact with the knowledge base and create handoff docs.
polypore.verify.*: Define and execute verification suites.
polypore.tasks.*: Real-time task creation and updates visible in the UI.
polypore.phase.*: Update the UI on the current workflow phase.
polypore.secrets.*: Perform mediated HTTP requests.
polypore.skills.*: Access the active skill library.
polypore.format.*: Trigger in-editor formatting.

The Secret Broker

To ensure security, Polypore prevents agents from seeing plaintext secrets. The process follows this logic: $\text{Environment Secret} \implies \text{POLYPORE\_SECRET\_HANDLE\_KEY}$

When an agent needs a secret, it calls polypore.secrets.use. Polypore injects the value into the HTTP request and masks the response, ensuring the agent never "sees" the raw credential.

Polyflow Skills

Polypore includes 15 built-in slash commands in packages/polyflow/ to handle the full dev lifecycle:

/polyflow, /polyflow-go
/polyflow-brainstorming, /polyflow-writing-plans, /polyflow-executing-plans
/polyflow-tdd, /polyflow-iterate, /polyflow-debug, /polyflow-review
/polyflow-design-interface, /polyflow-prd, /polyflow-improve-architecture
/polyflow-qa, /polyflow-glossary, /polyflow-compact

🏗️ System Design

The following diagram illustrates the flow of data and control within the Polypore ecosystem: