Interview-first intent
Requirements are clarified up front with deep-interview, so the agent works from a shared, concrete understanding instead of a guess.
Encode intention. Decode software.
An external coding-agent harness for interviews, approved plans, and durable
verification. Run gjc from the repository or worktree you choose,
then integrate direct clients through the SDK WebSocket, Coordinator MCP, or ACP.
Gajae Code (gjc) runs from the repository or worktree you choose,
then gives the agent a deliberately small workflow: clarify before guessing,
plan before mutation, and track every goal to completion with evidence.
It runs beside your existing tools β start it alongside Codex CLI, Claude Code, OpenCode, or Claw Code when you want structured planning, persistent evidence, an SDK integration, or an isolated worktree.
# run gjc in the repository or worktree you want to change
$ gjc
# inside the session: shape -> act -> prove
> /skill:deep-interview # clarify intent
> /skill:ralplan # plan & critique
> gjc ultragoal create-goals --brief-file plan.md
> gjc ultragoal complete-goals
Published 2026-08-09. Release binaries and npm packages are available.
Use the SDK WebSocket for direct control of one session, Coordinator MCP for multi-session automation, and ACP when an editor client is the right front end. Legacy Bridge and RPC modes are not current interfaces.
Build direct session clients on the loopback SDK WebSocket. The preserved route also explains migration away from historical Bridge and RPC ingress modes.
computer β desktop control (experimental)The opt-in computer tool is available on macOS. Its nine actions are screenshot, click, double_click, move, drag, scroll, type, keypress, and wait; Screen Recording and Accessibility permissions are required.
One small loop, done well. No sprawling skill zoo β Gajae Code improves by making this method better.
deep-interview turns vague requests into concrete requirements, boundaries, and explicit non-goals before any code is touched.
ralplan builds and critiques the implementation plan, then ultragoal carries the approved plan through execution, revision, verification, and evidence.
ultragoal tracks goals, revisions, checks, and completion evidence so a finished task ships with a verifiable trail, not a hopeful claim.
The default workflow is intentionally explicit. You always know what stage you are in.
Clarify ambiguous requirements before planning or code changes.
Build and critique an implementation plan before mutation.
Track goals through execution, revision, verification, and evidence.
Coordinate focused workers when parallel execution is worth it.
Everything you need to run an agent you can actually trust with a repository.
Requirements are clarified up front with deep-interview, so the agent works from a shared, concrete understanding instead of a guess.
ralplan drafts and critiques the approach through planner, architect, and critic perspectives before a single file is mutated.
ultragoal records goals, revisions, checks, and completion evidence under .gjc/ β a verifiable trail for every task.
Use the SDK WebSocket to control a direct session, Coordinator MCP to automate multiple sessions, or ACP to connect an editor client.
Create an isolated git worktree from a new branch for risky or reviewable work, keeping the primary checkout clean.
Coordinate multiple sessions with bounded turns, structured questions, durable status, and reports through the Coordinator MCP surface.
Run gjc rlm for a notebook-style research session over a persistent Python kernel, with a hard-gated read-only toolset, a live .ipynb, and a synthesized report on exit.
The opt-in computer tool is available on macOS with nine actions: screenshot, click, double-click, move, drag, scroll, type, keypress, and wait.
From CLI launch to model streams, every layer has a clear responsibility.
gjc binary registers commands (setup, deep-interview, ralplan, ultragoal, team, rlm) and supports interactive sessions, print output, SDK WebSocket clients, Coordinator MCP automation, and ACP editor clients.No Bun required. We detect your platform and link directly to the newest standalone release.
Choose the platform and architecture for this machine.
gjc on your PATH
chmod +x ~/Downloads/gjc-darwin-arm64
sudo install ~/Downloads/gjc-darwin-arm64 /usr/local/bin/gjcgjc --version && gjc --smoke-test && gjcNeed another build? View every latest release asset. Read the full installation guide. Standalone binary source availability remains on GitHub.
A small, fixed surface β no default skill sprawl.
| Skill | What it does |
|---|---|
deep-interview | Clarifies ambiguous requirements before planning or code changes. |
ralplan | Builds and critiques an implementation plan before mutation. |
ultragoal | Tracks goals through execution, revision, verification, and evidence. |
team | Coordinates focused workers when parallel execution is worth it. |
| Agent | What it does |
|---|---|
executor | Bounded implementation, fixes, and refactors. |
architect | Read-only architecture and code-review assessment. |
planner | Read-only sequencing and acceptance criteria. |
critic | Read-only plan critique and actionability review. |
Autonomy is only useful when the result is reviewable. Gajae Code is built to leave a trail.
Approaches are reviewed and critiqued before any file changes, reducing wasted runs and surprise edits.
Goals, revisions, checks, and verification results are recorded as durable artifacts you can read after the fact.
Risky work runs in a dedicated git worktree that gjc creates from a new branch, so your primary checkout stays clean and the diff stays scoped.
The SDK WebSocket, Coordinator MCP, and ACP expose explicit client boundaries rather than historical Bridge or RPC ingress modes.
Guides and references for every layer of Gajae Code.
Install, launch, and run your first shape β act β prove loop.
How the CLI, agent loop, provider boundary, and tools fit together.
Running gjc as an external runner beside your other agents.
Direct session control uses the SDK WebSocket; Coordinator MCP automates multiple sessions; ACP serves editor clients.
The four workflow skills and four role agents in detail.
The evidence model behind durable, verifiable completion.
Install Gajae Code, run it beside the tools you already use, and ship work with a trail you can read.