About MeshPilot.
Coding agents got good faster than the places we run them did. MeshPilot is the workspace built for the way people actually work with them now — several at once, on real folders, with real terminals.
The problem
A modern coding agent is a command-line program. So developers run them the way you run any command-line program: a terminal tab each, one per repository, output scrolling past, context copy-pasted between windows. Add a second agent and you are the integration layer. Add a third and you stop noticing which one is stuck.
The other option — a chat box in an editor — solves the interface but throws away the part that matters: the terminal, the process, the ability to run four of them side by side against the same project.
What we build
MeshConsole is a desktop application that treats coding agents as first-class processes. Persistent terminals that survive navigation, nearly thirty CLI agents in one registry, a spatial board where agents can be wired to pass context to each other, a shared task board, project memory, and an assistant that can operate the app itself. It runs on your machine and works against your folders.
MeshUtility is the smaller half: a free, open-source tray widget for voice dictation and prompt rewriting that works in any text field on your system, MeshPilot or not.
What we believe
- Local-first, not local-only. Your code, terminals and memory stay on your machine; only the things that genuinely need a server — identity, credits, coordination you opt into — leave it.
- Agents should be bounded, not trusted. Explicit permission levels, approval cards for destructive actions, and human-accepted diffs beat a hopeful prompt every time.
- Deterministic where determinism is cheaper. The Crew coordinator is code, not a model, so orchestration costs nothing and behaves the same way twice.
- No lock-in on the agent. Bring Claude Code, Codex, Cursor, OpenCode, Gemini, Copilot or any of the others. MeshConsole is the workspace, not the model.
Who builds it
MeshPilot is designed and built by Jenesh Patel in Chandigarh, India — the desktop runtime, the coordination layer, the orchestration state, and the parts you are reading now. It is a sole proprietorship, which is why support mail is answered by the person who wrote the code you are asking about.
Work in progress is visible in the , and the fastest way to influence what ships next is the Discord.
Get in touch
Questions, bug reports and feature requests all go through .