Install R.Code for Claude Code

One line gets you a complete, portable Claude Code setup on macOS, Linux, or Windows. The installer never touches credentials — Claude Code handles its own login on first launch.

One-liner (Mac/Linux)

bash <(curl -fsSL https://raw.githubusercontent.com/emanuelrechsteiner/claude-rcode/main/install.sh)

install.sh auto-detects the right mode for your machine:

Detected state	Mode	What happens
No `~/.claude`, or empty	fresh	Clones straight into `~/.claude`, copies templates to `.local.` overlays, makes hooks executable
`~/.claude` already tracks this repo	fresh (self-update)	`git pull` — safe, your `.local.*` files are gitignored and untouched
`~/.claude` has unrelated content	asks you	Prompts `overwrite \| augment \| abort` with a recommendation based on what it finds

You can also force a mode explicitly: ./install.sh --mode {auto|fresh|overwrite|augment} (default auto).

fresh — clone (or self-update) straight into ~/.claude.
overwrite — backs up your entire existing ~/.claude to ~/.claude.backup-<timestamp> (nothing is deleted, only moved), then does a fresh install. Because moving your whole config is a state-changing operation, this always asks for a one-time confirmation, including when --mode overwrite is passed directly (skip with --yes once you’re sure).
augment — scans your existing ~/.claude unit-by-unit (every rule, hook, skill, agent, command, plus your settings.json), classifies each unit against what you already have as new (safe to add), identical (skipped), or conflicting (shown as a diff, your call: keep yours / take this repo’s / skip). It prints a recommendation based on how much new value would be added versus how much would collide. Nothing is written without your say-so per conflicting file, settings.json is never replaced wholesale (only its hooks registrations are merged via jq, your env/model/permissions stay untouched), and --dry-run prints the full report and changes nothing on disk.

One-liner (Windows PowerShell)

iwr -useb https://raw.githubusercontent.com/emanuelrechsteiner/claude-rcode/main/install.ps1 | iex

install.ps1 is a minimal, community-maintained installer: clone/backup only (no augment scan-and-merge — that logic is bash-only). The hooks themselves need WSL or Git Bash to execute; PowerShell alone gets you the files, not the automation.

Manual (works everywhere with git)

# Mac/Linux:
git clone https://github.com/emanuelrechsteiner/claude-rcode.git ~/.claude

# Windows (PowerShell):
git clone https://github.com/emanuelrechsteiner/claude-rcode.git $HOME\.claude

# Then copy templates to personalize (both platforms):
cp ~/.claude/templates/CLAUDE.local.md.template ~/.claude/CLAUDE.local.md
cp ~/.claude/templates/identity.local.md.template ~/.claude/rules/identity.local.md

Logging in

The installer never touches credentials. On first claude launch after install, Claude Code runs its own login flow:

Setup complete. Start Claude Code with:  claude
On first launch, Claude Code runs its OWN login flow — choose either:
  • Pro/Max subscription  → browser OAuth (claude.ai)
  • Anthropic API key      → paste when prompted, or export ANTHROPIC_API_KEY
R.Code never stores or reads your credentials.

First command

Once installed and logged in, start any development task with /team-lead "<what you want>" — the entrance point that picks the right stage, loads its playbook, and dispatches. See How it works for what happens after that.

Optional: the Cockpit

The Cockpit is a tmux sidebar that shows a session live — context, cost, running subagents, workflow progress. It installs separately, from its own repo, with its own one-liner:

bash <(curl -fsSL https://raw.githubusercontent.com/emanuelrechsteiner/claude-cockpit/main/install.sh)

See what it installs, step by step, and the requirements before running it.