@rangor/cli

Friendly CLI for Rangor — sign in, connect sources from the terminal, set up MCP for Cursor, Claude Code, VS Code, Windsurf, and print briefings.

# From repo (dev)
cd tools/rangor-cli && npm install && npm run build
node dist/bin.js init

# After npm publish
npx @rangor/cli init

Commands

| Command | Description | |---------|-------------| | rangor init | Wizard: auth, multi-agent MCP, first briefing | | rangor context <source> <ref> | Briefing in terminal (see refs below) | | rangor connect github | OAuth, gh CLI, or PAT + repo scope picker | | rangor connect gitea | Self-hosted PAT + base URL + repo scope | | rangor connect jira | Jira Cloud OAuth or Jira Server PAT + projects | | rangor connect <provider> --reconnect | Disconnect and connect again (rotate tokens) | | rangor status | Account + MCP connection per editor | | rangor doctor | Health checks | | rangor logout | Remove saved credentials |

rangor connect with no provider opens Dashboard → Integrations (warm session).

Context refs

| Source | Example ref | Notes | |--------|-------------|-------| | GitHub | owner/repo or owner/repo#42 | Repo overview or issue | | Gitea | owner/repo or owner/repo#42 | Requires base_url from connect | | Jira | PROJ-123 | Cloud OAuth or Server PAT |

rangor context github ephemeral172/my-app
rangor context gitea IT-Implant/bxMatcher
rangor context jira KAN-9

Connect from terminal

GitHub

rangor connect github
# OAuth in browser, or reuse `gh auth token`, or paste a PAT — then pick repos

Gitea (self-hosted)

rangor connect gitea
# Base URL (e.g. https://gitea.example.com) + PAT with repo read access

Rotate a PAT without Dashboard:

rangor connect gitea --reconnect

Jira

rangor connect jira
# Jira Cloud → browser OAuth; Jira Server → base URL + PAT (+ username if needed)

--reconnect works for GitHub and Jira the same way.

Multi-agent MCP

init detects installed editors and skips agents where Rangor is already connected. Use rangor status to see per-editor state.

Flags

• --yes / -y — non-interactive defaults
• --reconnect — disconnect provider, then run connect flow (github, gitea, jira)
• --dashboard URL — pilot or production
• NO_COLOR, NO_EMOJI, CI=true — plain output

Local pilot

export RANGOR_DASHBOARD_URL=http://127.0.0.1:8081
rangor init

Push context (Team plan)

CLI covers pull briefings. Rangor also pushes context on real workflow events:

Context Guard

When a GitHub PR references a ticket (Fixes KAN-9), Rangor checks the PR diff against decisions and open conflicts in that ticket's UCP. Risks get a PR comment before merge; receipts record warned or warned_but_overridden.

Enable in Dashboard → Project → Context Guard on PRs.

Handoff Brief

When a Jira assignee changes, Rangor posts a structured handoff comment (context_diff, what was tried, open conflicts) for the new owner. Receipt: handoff_delivered.

Handoff cards also appear at the top of Sidebar briefings.

See the root README and stage-27 spec.