Connect a harness
One command connects a harness:
meshpoint connect <harness>Supported names: claude-code, codex, cursor, antigravity, pi, opencode, openclaw. Run meshpoint connect with no name to see which of them are installed on this machine, whether each is connected, and the command to connect it (--json for agents).
What connect writes
Section titled “What connect writes”Two things, always:
- The integration. Hooks for harnesses that run commands on events (Claude Code, Codex, Cursor, Antigravity, OpenClaw), or an extension or plugin for harnesses that load code in-process (pi, opencode). Every integration drives the same core: recall and presence injected at session start, prompts and replies spooled and sent once a minute, the checkpoint nudge, flush at session end.
- The
meshpointskill. The instructions the agent follows at a checkpoint: which item kinds exist, the rules, and the one command to run. See Items and checkpoints.
Existing hooks and settings are kept; only Meshpoint’s entries are added. Running connect again is safe. The harness picks the files up at its next session start.
User scope or one repository
Section titled “User scope or one repository”Without --project, connect writes to your user-level config directory (~/.claude, ~/.codex, ~/.cursor, ~/.gemini/config, ~/.pi/agent, ~/.config/opencode), so every repository you open is on the mesh. This is the default and what the setup skill does.
meshpoint connect <harness> --project /abs/path/to/repowrites into that repository instead (<repo>/.claude, .codex, .cursor, .agents). The files then travel with the repository in git, which is how a team can ship the connection with the code. Codex needs the repository trusted in ~/.codex/config.toml before project files load; see Codex.
A directory that is not a git repository with an origin remote is not a project. The hooks run and do nothing there.
meshpoint connect <harness> --remove [--project <dir>]removes only Meshpoint’s entries and the skill. meshpoint logout revokes the session and deletes the login file.
Per harness
Section titled “Per harness”| Harness | Mechanism | Verified live | Page |
|---|---|---|---|
| Claude Code | settings.json hooks |
yes | Claude Code |
| Codex | hooks.json + rules |
yes | Codex |
| Cursor | hooks.json |
ported from docs | Cursor |
| Antigravity | hooks.json |
ported from docs | Antigravity |
| pi | extension | yes | pi |
| opencode | plugin | yes | opencode |
| OpenClaw | hook pack | yes | OpenClaw |
“Verified live” means the session-start inject, capture, presence and the checkpoint nudge were each observed against the platform with that harness. “Ported from docs” means the integration follows the harness’s published hook documentation and has not yet been run end to end; the page lists what is unconfirmed.
