Glossary

Short, citeable definitions for the proprietary terms DevMesh uses across the site, the docs, and the product.

Vibecoding: A fluid, prompt-driven style of building software where the developer stays in flow and orchestrates a kanban, a terminal, and a swarm of AI agents from a single prompt. Vibecoding is the organizing concept that DevMesh is built around.
DevBoard: DevMesh's repo-resident kanban surface. Cards on the board are projections of backlog.md, the markdown file checked into the repository — editing the file is editing the board, and pull requests against it are pull requests against the kanban.
Swarm: A coordinated group of role-focused AI agents — Coordinator, Builder, Scout, Reviewer — that work in parallel on independent slices of a software task. Each agent runs against the same shared workspace and kanban, so progress is visible across the team in real time.
Space: DevMesh's native desktop development workspace. Space fuses a terminal, the kanban, and AI teammates onto one panel layout with shared context, so a single prompt can plan a feature, kick off implementation, and update the board without context switching.
DevShot X: DevMesh's macOS capture, screen-recording, and annotation app, built on Tauri 2. Every shot can deep-link straight into a DevMesh task, so screenshots and recordings flow directly onto kanban cards instead of getting stuck in chat threads.
backlog.md: The file-based source of truth for a DevMesh project's kanban. Plain markdown plus HTML-comment metadata (id, status, source). The hosted board reads from this file, so the repo always carries the canonical task list.
dm (CLI): The DevMesh command-line tool. Drives the kanban from the terminal: add tasks, push backlog.md, move cards, list open tickets in JSON for CI gates. Installable via npm install -g @devmesh/cli.
Group: A shared label (passed via --group <label> on dm task add) that ties sibling tasks together visually on the board. Tasks sharing a group render with a deterministic colored left-border, making batches of work born from the same audit, prompt, or session obvious at a glance.
Repo binding: Auto-attachment of a DevMesh task to a specific repository, driven by a .devmesh.json file at the repo root. Tasks created from inside a bound repo inherit the repoId automatically, so per-repo views on the kanban stay coherent.
MCP (Model Context Protocol): The open Anthropic-defined protocol that lets coding agents (Claude Code, Cursor, Windsurf, Codex, and others) discover tools, call them, and subscribe to resources over stdio. DevMesh MCP exposes the kanban, file claims, inter-agent mailbox, and tiered memory vault through this protocol — so any MCP-speaking client joins the same swarm without bespoke integration work.

Vibecoding

DevBoard

Swarm

Space

DevShot X

backlog.md

dm (CLI)

Group

Repo binding

MCP (Model Context Protocol)