FAQ
Short answers about Gajae-Code install, gjc, tmux, providers, workflows, rlm, team, computer-use, and limits.
Start with the section that matches where you are stuck: Install and environment for setup, First use for choosing the first command, and Running and limits for longer sessions.
Install and Environment
What is Gajae-Code?+
Gajae-Code is the gjc coding-agent harness: a small public workflow surface wrapped around sessions, tmux, model routing, tools, and evidence.
How do I install it?+
Use bun install -g gajae-code. The package installs the gjc binary. The scoped package is also available as @gajae-code/coding-agent.
Do I need tmux?+
Not for bare gjc, but the recommended path is gjc --tmux. The team command expects a tmux session.
First Use
Which flow should I learn first?+
Learn the loop: deep-interview for clarity, ralplan for the reviewed plan, and ultragoal for durable execution and evidence.
When should I use rlm?+
Use gjc rlm for exploratory research instead of code mutation. It writes notebook and report artifacts under .gjc/_session-<gjcSessionId>/rlm/<rlmSessionId>/.
Is team required?+
No. team is optional and useful only when parallel tmux workers genuinely help. Single-threaded work can stay in the normal loop.
Running and Limits
How do provider credentials resolve?+
gjc checks CLI API keys, stored API keys, stored OAuth credentials, environment variables, then models.yml apiKey. Keep secrets out of committed files.
What does computer-use require?+
The experimental computer tool is available by default on supported Apple Silicon macOS hosts, supervisor-gated, and can be disabled with computer.alwaysOn=false.
Where should I look for command details?+
Use Commands for the workflow commands and CLI Reference for launch, setup, research, team, and ultragoal command shapes.