SteerMesh Platform

One mesh for every agent runtime.

Write agents, skills, and rules once. Mesh runs that workspace on Kiro, Cursor, Claude Code, and Codex.

Steering mesh

  • Genome
  • Rules
  • Hooks

Core

Runtimes

  • Kiro
  • Cursor
  • Claude Code
  • Codex

Mates

  • Synapse
  • Grid
  • Pulse

Install

Install Mesh on this machine.

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 setup

Use the tap-qualified formula. A bare brew install mesh on macOS can hit an unrelated cask with the same name.

After you install

Upgrade

brew upgrade steermesh/tap/mesh
mesh upgrade

Synapse 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 update

Problem

Steering breaks when every tool speaks a different language.

Tool config divergence

Every IDE, agent, and vendor has its own steering syntax. Teams fork configs and lose alignment.

Policy duplication + drift

Security and compliance rules get copied by hand and diverge with every update.

No versioning/audit trail

You can’t answer who changed steering, when, or which tool is out of date.

Steering becomes inconsistent. AI behavior drifts.

Solution

A mesh for AI steering.

Genome defines. Core orchestrates. Grid distributes. Synapse remembers. Pulse monitors.

Genome

  • Profiles, agents, skills, and steering rules in one pack.
  • Hooks and MCP bundles install with the profile.
  • Pin a genoma release so every machine matches.
  • Add a custom registry when a team needs its own workspaces.

Core

  • The mesh binary: setup, workspaces, and chat.
  • Same workspace on Kiro, Cursor, Claude Code, and Codex.
  • Check the install, then sync the workspace to this machine.

Mesh mates

  • Mates are companion binaries Mesh installs beside Core.
  • Synapse remembers across sessions. Grid shares compute with other machines. Pulse scores prompts.
  • VaultBreak holds secrets and handoffs. Add it with mesh mates install.

How It Works

From a Genome pack to a running workspace.

01

Load a Genome profile

mesh setup installs agents, skills, rules, hooks, and MCP bundles from genoma.

02

Open a workspace on a runtime

mesh chat --ws runs the same workspace on Kiro, Cursor, Claude Code, or Codex.

03

Add the mates you need

Synapse ships with Mesh. Install Grid, Pulse, or VaultBreak with mesh mates install.

Custom registry

Workspaces for specialist agents and context.

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.

01

Add the registry

Point Mesh at the team pack. Workspaces mode keeps Genome as the base and uses your repo for workspaces only.

02

Scaffold a workspace

Init creates workspaces/<name> with workspace.json, plus context/ and rules/ folders you fill in.

03

Add specialists

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-team

Teammates 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

Five live products, and Nexus in progress.

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

Live

Mesh Core

Terminal companion. Installs Genome packs, runs workspaces, and chats on Kiro, Cursor, Claude Code, and Codex.

genoma

Live

Mesh Genome

Profiles, agents, skills, steering rules, hooks, and MCP bundles that Mesh installs.

grid

Live

Mesh Grid

Shares compute with other machines.

synapse

Live

Mesh Synapse

Remembers across sessions.

pulse

Live

Mesh Pulse

Scores prompts and sessions alongside Mesh.

nexus

Early

Mesh Nexus

Desktop workbench for conversation, artifacts, and visual design.

SteerMesh Cloud (Coming Soon)

Govern steering bundles at org scale.

  • Org steering registry + releases
  • RBAC + audit logs
  • Approvals and policy gates

We only use your email to share SteerMesh Cloud updates. See our privacy policy for details.

Join the waitlist

Get early access to governance workflows, sync agents, and platform-level guardrails.