mesh
LiveMesh Core
Terminal companion. Installs Genome packs, runs workspaces, and chats on Kiro, Cursor, Claude Code, and Codex.
SteerMesh Platform
Write agents, skills, and rules once. Mesh runs that workspace on Kiro, Cursor, Claude Code, and Codex.
Steering mesh
Core
Runtimes
Mates
Install
macOS, Linux, or Windows. These commands install Mesh and run mesh setup. No private checkout.
Install
brew tap SteerMesh/tap
brew trust steermesh/tap
brew install steermesh/tap/mesh
mesh setupUse the tap-qualified formula. A bare brew install mesh on macOS can hit an unrelated cask with the same name.
Upgrade
brew upgrade steermesh/tap/mesh
mesh upgradeSynapse ships with Mesh. Add Grid, Pulse, or VaultBreak when you need them. On Homebrew, brew upgrade moves the Mesh binary and mesh upgrade refreshes the mates already on the machine.
synapse
Remembers across sessions
Ships with Mesh. mesh upgrade always refreshes it.
grid
Shares compute with other machines
mesh mates install grid
pulse
Prompt scoring
mesh mates install pulse
vaultbreak
Secrets, handoffs, and an MCP server for agents
mesh mates install vaultbreak
mesh mates
mesh mates updateProblem
Every IDE, agent, and vendor has its own steering syntax. Teams fork configs and lose alignment.
Security and compliance rules get copied by hand and diverge with every update.
You can’t answer who changed steering, when, or which tool is out of date.
Steering becomes inconsistent. AI behavior drifts.
Solution
Genome defines. Core orchestrates. Grid distributes. Synapse remembers. Pulse monitors.
How It Works
mesh setup installs agents, skills, rules, hooks, and MCP bundles from genoma.
mesh chat --ws runs the same workspace on Kiro, Cursor, Claude Code, or Codex.
Synapse ships with Mesh. Install Grid, Pulse, or VaultBreak with mesh mates install.
Custom registry
Genome stays the default registry. A custom registry is a git pack your team owns. Each workspace in that pack can carry specialist agents, their prompts, and the context those agents should read. Mesh applies the workspace on top of Genome, so the shared profiles stay in place.
Point Mesh at the team pack. Workspaces mode keeps Genome as the base and uses your repo for workspaces only.
Init creates workspaces/<name> with workspace.json, plus context/ and rules/ folders you fill in.
Put agent configs and prompts under profiles/, and team notes under context/. Apply the namespaced workspace, then commit the pack.
Create a team workspace
mesh registry add team-pack git@github.com:ORG/team-pack.git --mode workspaces
mesh registry init team-pack --workspace my-team
mesh workspace apply team-pack/my-teamTeammates run mesh registry add with the same URL, then mesh registry sync team-pack. A bare name works when it is unique. Use registry/workspace when the same name exists in Genome.
Open Family
Mesh and genoma are the open family. Grid, Synapse, and Pulse are mesh mates: companion binaries Mesh installs and upgrades. Nexus is the desktop workbench in progress. Cortex and Flow are planned. Install from the Homebrew tap. The product repos stay private.
Mesh Core
Terminal companion. Installs Genome packs, runs workspaces, and chats on Kiro, Cursor, Claude Code, and Codex.
Mesh Genome
Profiles, agents, skills, steering rules, hooks, and MCP bundles that Mesh installs.
Mesh Grid
Shares compute with other machines.
Mesh Synapse
Remembers across sessions.
Mesh Pulse
Scores prompts and sessions alongside Mesh.
Mesh Nexus
Desktop workbench for conversation, artifacts, and visual design.
SteerMesh Cloud (Coming Soon)
We only use your email to share SteerMesh Cloud updates. See our privacy policy for details.
Get early access to governance workflows, sync agents, and platform-level guardrails.