Quickstart
Two ways in. Hand the setup to the agent you already use, or run four commands yourself.
Let your agent do it
Section titled “Let your agent do it”Paste this into any coding agent that can run shell commands:
Fetch https://meshpoint.dev/skills/meshpoint-setup/SKILL.md and follow it.The skill installs the CLI, signs you in (it prints a code to approve in the console when there is no browser), connects every harness it finds on the machine, and reports what it did. Nothing in it needs sudo and it never asks you for a token.
Do it yourself
Section titled “Do it yourself”1. Install the CLI
Section titled “1. Install the CLI”Needs Node 22 or newer. Hooks call meshpoint from PATH, so a global install is required; npx is not enough.
npm i -g @meshpoint/climeshpoint --versionIf npm i -g fails with a permissions error, set a prefix in your home directory instead of using sudo:
npm config set prefix ~/.npm-globalexport PATH=~/.npm-global/bin:$PATH2. Sign in
Section titled “2. Sign in”meshpoint loginWith a browser available, the CLI opens it and you sign in with Google, Microsoft or an email code. Without one (SSH, a container, a cloud agent) the CLI prints a URL and an 8-character code:
Open https://app.meshpoint.dev/device?code=ABCD-EFGHor go to https://app.meshpoint.dev/device and enter ABCD-EFGHWaiting for approval (expires in 15 min)…Approve it from any signed-in browser. --device or --browser forces one flow. The first sign-in creates a personal organization for you; invites from a teammate are accepted at sign-in by email.
meshpoint whoami3. Connect your harnesses
Section titled “3. Connect your harnesses”meshpoint connectThis lists every harness found on the machine, whether it is connected, and the exact command for each. Then connect them:
meshpoint connect claude-codemeshpoint connect codexmeshpoint connect pimeshpoint connect opencodeEach connect writes hooks or a plugin plus a small skill into that harness’s user-level config directory, so every repository you open is covered. It is safe to run again, and --remove undoes it. Add --project /abs/path/to/repo to keep Meshpoint to one repository instead; the files then land inside that repo. Details per harness are in Connect a harness.
4. Check
Section titled “4. Check”meshpoint doctorEvery line should show a check mark: config present, signed in, repository with an origin remote, harnesses connected, spool writable. “Last capture: never” is expected until a session runs.
First session
Section titled “First session”Start a new session in a connected harness inside a git repository that has an origin remote. Within seconds the console at app.meshpoint.dev shows the project and the live agent. The first items appear when the agent reaches its first checkpoint, or sooner if you ask it to run the meshpoint skill.
Teammates join from the console’s Org page: an owner or admin enters their email, they sign in with that email, done.
