Start

Getting Started

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

Requirements

The standalone gjc binary is self-contained. Bun is not required. Git is needed only when you choose worktree isolation; a direct local TUI session does not require tmux.

Install the latest binary

The installer below detects your current platform and downloads the matching asset from the latest stable GitHub release. Change the selection when downloading for another machine.

# 1 · choose your platform Standalone binary

View latest downloads

Choose the platform and architecture for this machine.

On Windows, run the generated setup commands in PowerShell, then open a new terminal so the updated user PATH is loaded. Downloads always use GitHub’s releases/latest/download route, so this page does not need a version-specific binary link.

Supported standalone binaries

Platform	Architecture	Release asset
macOS	arm64	`gjc-darwin-arm64`
macOS	x64	`gjc-darwin-x64`
Linux	x64	`gjc-linux-x64`
Linux	arm64	`gjc-linux-arm64`
Windows	x64	`gjc-windows-x64.exe`

Quick start

Start the interactive TUI directly from the checkout you want to work in. For isolated work, create or enter a worktree yourself, then launch the same direct session there.

# Run directly in the current checkout
gjc

# Or, from a worktree you created or selected
cd ../my-task-worktree
gjc

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

Use /skill:autoresearch when the next step is evidence, not code: landscape research before an interview, or a verdict after a spec. Parallel coordination is IRC, not a fifth workflow skill. Machine controllers should use the SDK WebSocket for direct session control, Coordinator MCP for multi-session automation, or ACP for editor clients—never terminal prompt injection, tail helpers, or pane scraping.

SDK discovery

A running top-level session writes its loopback SDK discovery record to <repo>/.gjc/state/sdk/<sessionId>.json. Read its url and token with an SDK client such as @gajae-code/bridge-client; use Coordinator MCP for multi-session orchestration.

Updates

Startup checks report when a newer version is available without changing your installation. Return to the installer above, download the latest standalone binary, and rerun its PATH command to replace the existing executable.

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

Configuration

Provider retry budgets live in the global agent configuration at ~/.gjc/agent/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. The ouroboros theme joins the built-ins alongside the claude-code, codex, and opencode migration themes — browse them all with /theme, and pick a terminal mascot with /pet. Explicit user theme settings always win.