Bring a device into the team connection

Use a macOS or Linux device. Check for Node.js 22 or later. Check that npm is available from the same terminal.

node --version
npm --version

Obtain the approved setup release from your administrator. A source build does not establish package publication. Use the distribution supplied for your deployment.

Confirm the organization and team named in the invitation. Read existing device status before replacing a connection or entering a new enrollment code.

npx @betterloop/setup status

Turn an invitation into personal enrollment

A reusable team invitation opens without dashboard authentication. Provide your name and work email in the invitation form. Copy the personal setup command it provides.

The setup utility redeems a personal code. It does not redeem the shared invitation code. An administrator can issue a single-use personal code directly.

Keep that code private. Exclude it from repository files and shared terminal records. A valid device connection can add agents without another enrollment.

Start a session in another working repository. Betterloop records that invoking repository at startup. It validates cached policy and resolves the applicable signed knowledge.

Repository facts, selected knowledge, readiness state, and fleet credentials remain separated by repository context. A result from one session cannot establish another session’s coverage.

An unapproved repository uses the organization setting. Report-only behavior omits company resources and bindings. Team-default behavior still omits company project knowledge without a match.

A missing or unresolved remote remains unapproved. Naming a local directory after an approved project does not approve that repository.

Resolve more than one knowledge match

Ask the administrator which configured knowledge project should apply. Supply its exact identifier for the intended repository. The selection is remembered for that repository.

betterloop sync --harness codex --project /path/to/repository --knowledge-project PROJECT_ID

A knowledge reference identifies a source. It does not supply access rights. External Git, HTTPS, and MCP sources retain their own authorization requirements.

Illustrative check: Harbor documentation and service code

A Harbor developer connects both native agents on one device. They complete sign-in separately. They review and trust the Codex hooks.

The developer opens search-api in Codex and checks doctor. They open the documentation repository in Claude Code and inspect that session separately.

Each session resolves its own applicable context. The service result supplies no evidence that the documentation repository has identical knowledge or control coverage.

To add an agent later, rerun setup for that agent. The device connection resumes. A different organization or team requires explicit disconnection and new enrollment.

If the signed runtime variant is unavailable, setup reports the dependency before consuming the personal code. Ask the administrator to resolve release compatibility.