Start

Getting Started

Install Gajae Code, launch it in a repository or worktree, and run your first reviewable loop.

Requirements

Gajae Code (gjc) is distributed as a Bun package. You need Bun installed. tmux is optional but recommended for leader/worker sessions, and git is required to use worktree isolation.

Install

Install the CLI globally with Bun:

bun install -g gajae-code

The scoped package is also published as @gajae-code/coding-agent.

Windows (native install)

On a clean Windows 11 machine, install Bun first, then install gjc with Bun's global installer:

# 1. Install Bun
powershell -c "irm bun.sh/install.ps1|iex"

# 2. Restart the terminal so PATH refreshes, then confirm Bun
bun --version

# 3. Install and verify gjc
bun install -g gajae-code
gjc --version
gjc --smoke-test

bun install -g places the gjc launcher in %USERPROFILE%\.bun\bin. That directory must be on PATH. Bun's installer adds it automatically, but the change only applies to terminals started after installation — restart PowerShell if gjc is "not recognized".

Verify

gjc --version && gjc --smoke-test

Quick start

Run gjc directly in the checkout you want to work in, use a tmux-backed leader session, or create an isolated worktree on a new branch for risky or reviewable work:

# Run directly in the current checkout
gjc

# Use a tmux-backed leader session
gjc --tmux

# Create an isolated worktree on a new branch for risky or reviewable work
gjc --tmux --worktree my-task-branch

Your first loop

Inside a session, use the public workflow surface to go from intent to a proven result:

/skill:deep-interview clarify ambiguous requirements
/skill:ralplan build and critique the implementation plan
gjc ultragoal create-goals --brief-file <approved-plan>
gjc ultragoal complete-goals

Add gjc team ... only when coordinated tmux workers materially help with implementation or verification.

When a Clawhip or chatops router needs a visible pane, use the gjc-session plugin skill plus scripts/gjc-session/{create,prompt,tail} to create the named worktree-backed session, inject the task after readiness, and capture bounded tail output. Keep gjc-session in the plugin/helper category; the bundled workflow surface above remains four skills.

Configuration

Provider retry budgets live in ~/.gjc/config.yml:

retry:
  requestMaxRetries: 4
  streamMaxRetries: 100
  maxRetries: 3
  maxDelayMs: 300000

requestMaxRetries applies before a stream is established. streamMaxRetries applies only to replay-safe transient stream failures. Invalid auth, unsupported models/providers, malformed requests, context overflow, user aborts, and permanent quota failures remain fail-fast.

The default dark theme is the red-claw identity; light-appearance terminals default to the bundled blue-crab theme. Explicit user theme settings always win.