Documentation
Gajae Code docs
Everything you need to run gjc — an external coding-agent harness built around a single, reviewable loop: shape intent, act through reviewed plans, and prove the result with durable evidence.
New here? Start with Getting Started, then read Architecture to understand how the pieces fit together.
Getting Started
Install with Bun, launch in your repo, and run your first shape → act → prove loop.
What’s new (v0.11.0)
Read release highlights and upgrade guidance.
Telegram onboarding
Create a BotFather bot, run gjc notify setup, pair a private chat, and troubleshoot the managed daemon.
RLM research mode
Use gjc rlm for notebook-style research with Python, read, and web search tools.
Computer tool
Tell a GJC session to use the computer tool to inspect the screen, click, type, and control a desktop app.
Browser tool
Drive headless Chromium, a CDP-attached app, or a saved Chrome profile — observe, click, type, and script tabs with the browser tool.
Architecture
The CLI, agent loop, provider boundary, tool registry, and native layer.
The Harness
Running gjc as an external runner beside Codex CLI, Claude Code, and others.
Bridge & RPC
The stdio RPC protocol and the fail-closed, TLS-only HTTPS bridge.
Skills & Agents
The four bundled workflow skills, four role agents, and public plugin/helper patterns such as gjc-session.
Receipts & Proof
The evidence model behind durable, verifiable completion.
Hermes / OpenClaw MCP Bridge
Recommended starter: visible tmux routed sessions with the gjc-session plugin helpers. Plus the coordinator MCP bridge, gjc-delegation skill, and RPC boundary.
Gajae Remote
The thin phone steering-wheel design: bounded session views, gateway-only scopes, and one-line submit without becoming a remote shell.
Troubleshooting
Common install, launch, and runtime issues with fixes.
Gajae Code is an experimental, beta-stage project. Expect rough edges and verify outputs before relying on it for important work.