Existing project · new teammate

From invite to first coordinated edit.

Everything you need to join a Naib project that is already running. Allow about five minutes: accept access, connect your agent, approve the device, and restart.

Start the setup How Naib works

The path

Do these in order.

Access comes first. The device approval can only see projects your GitHub account is already allowed to join, so connect the agent after accepting the invite.

Access

Accept the project invite

Open the invite link from your project owner and sign in with GitHub. The invite adds you to the existing team and project; you do not need to create either one.

↳The invite link is private. Treat it like a password and do not forward it.

Local setup

Open the repository you want to work in

The Naib adapter runs on the same machine and in the same project directory as your coding agent. Make sure Node.js 22.5 or newer is installed before you connect.

Check your local machine

cd path/to/your/repository
node -v

↳If the version is lower than 22.5, install a current Node.js release and run the check again.

Connect

Run setup and choose the existing project

Run this from the repository directory. The command installs the published MCP adapter, asks Naib to identify the project, and starts a short device-approval flow.

Run from the repository folder

npx -y keel-coordination-mcp setup \
  --server https://openclaw212onubuntu-s-2vcpu-4gb-amd-nyc3-01.taild4ce34.ts.net \
  --project sync-monorepo \
  --vendor codex

↳Change --vendor to claude_code or gemini if that is the client you use. If your project has another name, replace sync-monorepo with the exact project name from your invite.

Approve

Verify the code in your browser

The terminal prints a browser link and a six-character code, then waits. Open the link, check that the code and project are the ones you expect, and approve the connection while signed in as the invited GitHub account.

↳Approval grants the agent a project-scoped credential. It never gives the agent your GitHub session or repository permissions.

Approve only when these match

Code · GitHub account · project name

Finish

Restart your coding agent

Setup writes the local credential and MCP configuration, then exits after approval. Restart Codex, Claude Code, Cursor, or Gemini so it loads the new server configuration.

↳The credential belongs to this local setup. Repeat the setup flow for another machine or another repository directory.

Working on sync itself?

Use the local build instead of the published adapter.

This repository keeps its MCP configuration pointed at keel/dist. If you are editing the sync codebase, run the repo-specific login flow after cloning:

Inside the sync repository

npm --prefix keel install
npm --prefix keel run login -- \
  --server https://openclaw212onubuntu-s-2vcpu-4gb-amd-nyc3-01.taild4ce34.ts.net \
  --project sync-monorepo \
  --vendor codex

Do not run the published setup command here: it rewrites the tracked .mcp.json and moves the agent away from the local build.

You are ready when

The first session passes these checks.

You do not need to configure anything else before beginning normal work. Naib coordinates the agent; Git, tests, and code review remain part of the usual workflow.

Invite accepted

You can see the team and sync-monorepo project in the Naib dashboard.

Agent connected

Your agent appears in the project activity after its first MCP call.

Rules loaded

The agent can read the project charter before it starts work.

First task ready

The agent can find work, declare an intent, and reserve files before editing.

Optional, for this repo

Run the all-in-one diagnostic

It checks Node, the local build, credentials, server reachability, project visibility, and agent registration.

From the sync repository

npm --prefix keel run doctor

If setup stops

The common fixes.

Most setup problems are either an unaccepted invite, a command run from the wrong directory, or a client that needs restarting.

“No valid Keel credential”

Run setup again in the same directory where the coding agent runs, then restart the client.

“Project not found”

Accept the invite first and verify that the GitHub account in the browser is the invited account. Check the project name for typos.

The terminal is waiting

Open the printed device link and approve the matching code. If the link was closed, press Ctrl+C and run setup again for a fresh code.

Nothing appears on the dashboard

Restart your coding agent. MCP settings are read at startup, not continuously.