rai onboard

Unified developer onboarding. Two modes: OIT (invitation) for team-managed setups, or local-first (OSS) for standalone repositories.

Usage

rai onboard [OPTIONS]

Modes

OIT (invitation) path

Pass --from-oit-token with a one-time invitation token (oit_xxx) from raise.sh/onboard:

1. Exchange OIT for credentials
2. Save ~/.rai/server.json
3. Run rai init (if project scoped in token)
4. Sync team knowledge

Local-first (OSS) path

Run without a token:

1. Observe repository state (legacy scan, manifest, skill manifest, grounding)
2. Route deterministically to exactly one action
3. Execute action via strict self-invocation
4. Re-observe postcondition; emit Detected/Action/Next transcript

Options

Flag	Short	Description
--from-oit-token		One-time invitation token (oit_xxx) from raise.sh/onboard
--server	-s	RaiSE server URL (default: https://api.raise.sh)
--no-bootstrap		Skip team knowledge sync after connect (useful in CI)
--force		Overwrite existing credentials without prompting

Examples

# Team onboarding with invitation
rai onboard --from-oit-token oit_abc123

# Local-first onboarding (OSS)
rai onboard

# CI environment (skip knowledge sync)
rai onboard --from-oit-token oit_abc123 --no-bootstrap

See Also

• rai init — project initialization (called by onboard when needed)
• rai self-update — update rai to latest version