A coding agent that ships only what the model needs to work — a tiny system prompt, one carefully-chosen MCP, and a focused tool set. Switch between Anthropic, OpenAI, GLM, Moonshot, MiniMax, Xiaomi, DeepSeek, and OpenRouter mid-conversation. Run it on its own, or let @kenkaiiii/gg-boss drive a fleet of ggcoder workers across many projects from a single chat.

Built on @kenkaiiii/gg-ai and @kenkaiiii/gg-agent. Part of the GG Framework monorepo.

🚀 Run It

npm i -g @kenkaiiii/ggcoder

ggcoder login    # Pick provider, authenticate
ggcoder          # Start coding

OAuth for Anthropic and OpenAI (log in once, auto-refresh, no key to leak). API keys for the rest. Up and running in seconds either way. Auth lives in ~/.gg/auth.json and is shared with gg-boss.

🪶 The system prompt problem

Every token in the system prompt gets processed on every single turn. It's not a one-time cost. It's a tax on every request.

| | Claude Code / Agent SDK | GG Coder | |---|---|---| | System prompt size | ~15,000 tokens | ~1,100 tokens | | Ratio | baseline | ~13x smaller |

Why you should care

• Slower responses. More input tokens = longer time-to-first-token. In a 30-turn session, that wait adds up to minutes.
• Worse instruction following. More rules = more things the model ignores. "Lost in the middle" is well-documented. A 1,100 token prompt gets read. A 15,000 token one gets skimmed.
• Context fills up faster. ~15,000 tokens sitting in your window permanently. That's ~7.5% of a 200K model gone before you say hello. You hit compaction sooner, lose history faster, and the agent forgets what it was doing.
• Higher cost. Input tokens aren't free. Every cache miss charges you for the full bloat. Smaller prompt = smaller bill.

GG Coder sends only what the model needs: how to work, what tools it has, and your project context. No walls of rules. No formatting instructions. Just signal.

🧩 The MCP problem

Same philosophy applies to tools. People collect MCPs like Pokemon. Slack MCP, GitHub MCP, Notion MCP, five different file system MCPs. Every single one injects its tool descriptions into the context. The model now has to figure out which of 40+ tools to use for any given task.

This doesn't help. It confuses the agent. More tool descriptions = more noise = worse tool selection. The model spends tokens reasoning about tools it will never call.

GG Coder ships with one MCP: Grep. That's it. It lets the agent search across 1M+ public GitHub repos to verify implementations against real-world code. Correct API usage, library idioms, production patterns. One tool that actually makes the output better.

You can still add your own MCPs if you need them. But start with less. You'll get better results.

🎛 Eight providers, one agent

Switch mid-conversation with /model. Not locked to anyone.

| Provider | Models | Auth | |---|---|---| | Anthropic | Claude Opus 4.8, Sonnet 5, Haiku 4.5 | OAuth | | OpenAI | GPT-5.5, GPT-5.5 Pro, GPT-5.4, GPT-5.3 Codex | OAuth | | Moonshot | Kimi K2.7 | API key | | Z.AI (GLM) | GLM-5.1, GLM-4.7, GLM-4.7 Flash | API key | | MiniMax | MiniMax M3 (image + video) | API key | | Xiaomi (MiMo) | MiMo-V2.5-Pro, MiMo-V2.5-Pro-UltraSpeed, MiMo-V2.5 (image + video) | API key | | DeepSeek | DeepSeek V4 Pro, V4 Flash | API key | | OpenRouter | Qwen3.6-Plus + multi-provider gateway | API key |

The same conversation, the same tools, the same project context — only the model changes. Use a strong reasoning model when you need it, swap to a fast cheap one for grunt work, never restart your session.

Attachments. Drag, paste, or type a path to attach images and video in the chat input. Video is sent natively to models that support it (Gemini 3.x, Kimi K2.7, MiniMax M3, MiMo-V2.5); for other models the video is saved to a temp file and the model is told to inspect it with ffmpeg or its own tools.

🤝 Pair it with gg-boss

ggcoder is the unit of work. gg-boss is the orchestrator that drives many of them at once.

npm i -g @kenkaiiii/gg-boss
ggboss link    # pick which projects to drive
ggboss         # one chat, N parallel ggcoder workers

Inside gg-boss, every project gets its own ggcoder AgentSession running in that project's directory. The boss dispatches work — prompt_worker(project, "...") — and each worker uses the same focused tool set (read, write, edit, bash, grep, find, ls, web fetch, sub-agents) you'd get running ggcoder solo. Workers reply with a tight Changed / Skipped / Verified / Notes / Status summary the boss reads, cross-checks, and routes off.

Why this works: ggcoder's lean prompt and tight tool set keep each worker cheap and predictable, so the boss can run six or more in parallel without context blow-up. Anything you can do in a single ggcoder session — slash commands, skills, MCPs, custom commands, project CLAUDE.md rules — works inside the boss too.

Run ggcoder directly when you're heads-down on one project. Switch to ggboss when you want a coordinator on top.

⌨️ Keybindings

| Key | What it does | |---|---| | Ctrl+T | Open the Task pane | | Ctrl+S | Open the Skills pane | | Shift+Tab | Cycle extended thinking (off / low / medium / high / max) | | Esc | Interrupt the agent mid-turn | | Ctrl+C ×2 | Exit | | ↑ / ↓ | Recall previous prompts (when input is empty) | | Enter | Send · Shift+Enter newline · / opens the slash menu |

💬 Slash commands

Everything runs through slash commands inside the session. Not CLI flags.

| Command | What it does | |---|---| | /model (/m) | Switch model on the fly | | /compact (/c) | Compress context when it gets long | | /new (/n) | Start a fresh session in this project | | /session (/s) | Resume a prior session | | /branch (/b) | Branch the current conversation | | /branches | List branches of the current session | | /rewind | Restore files and/or conversation to an earlier checkpoint | | /buddy | Spin up a second model to review the current chat | | /settings (/config) | Open settings | | /help (/h, /?) | Show all commands | | /quit (/q, /exit) | Exit |

Plus built-in workflows that ship with the binary:

/expand        # Compare against current alternatives and report gaps
/bullet-proof  # Run a defensive security review
/init          # Generate CLAUDE.md for your project
/setup-commit  # Generate a /commit command with quality checks
/setup-skills  # Audit and recommend reusable skills

🛠 Tools

GG Coder comes with a focused set of tools. Each one is small, well-described, and earns its place in the prompt.

| Tool | What it does | | --------------------------------- | ------------------------------------------------------------------------------------------------------ | | bash | Run shell commands | | read | Read file contents | | write | Write files | | edit | Surgical string replacements | | grep | Search file contents (regex) | | find | Find files by glob pattern | | ls | List directory contents | | web_fetch | Fetch URL content | | screenshot | Open a URL / dev server in a headless browser and capture a PNG so the agent can see the rendered page | | subagent | Run one blocking, isolated child task (backward-compatible) | | spawn_agent / wait_agent | Launch persistent child turns concurrently and collect results | | send_message / followup_task | Steer a running child or reuse an idle child's context | | list_agents / interrupt_agent | Inspect or interrupt persistent children |

The screenshot tool needs the optional playwright dependency plus a one-time npx playwright install chromium. Without it the tool returns an install hint instead of failing the turn. Captured images render inline in graphics-capable terminals (kitty, Ghostty, WezTerm, iTerm2); other terminals show a text line.

Plus the Grep MCP for searching across 1M+ public GitHub repos. Add your own MCPs in settings if you need more — but start lean.

Async subagent lifecycle

subagent remains blocking. The async suite launches persistent NDJSON worker processes, so a parent can start up to four active child turns, keep working, steer them, and wait for any or all results. Up to eight idle workers remain available for follow-up; bounded snapshots retain the latest 20 agents.

Only GPT-5.6 Sol/Terra at Ultra delegates proactively. Lower Sol/Terra levels use async agents only when the user or project/skill instructions request delegation; other models receive no proactive policy.

Children share the parent working directory, not isolated worktrees. Parallel writes must target disjoint files or subsystems. Async fan-out is one level deep, child output is bounded, idle workers reap after 10 minutes, and workers are not resumable after a CLI/app restart.

Parent cancellation interrupts active children. Session disposal shuts down every worker process alongside background commands, LSP servers, and MCP connections.

🪄 Custom commands

Drop a markdown file in .gg/commands/ and it becomes a slash command. Your React app gets /deploy and /storybook. Your API gets /migrate and /seed. Different projects, different commands.

⏪ Checkpoints & /rewind

Before every file the agent writes or edits, GG Coder snapshots the prior on-disk content into a per-session checkpoint (stored under ~/.gg/checkpoints/, never in your repo). Run /rewind to pick an earlier checkpoint and restore code only, conversation only, or both.

Only edits made through ggcoder's write/edit tools are tracked — changes made by bash (e.g. sed, rm, codegen) are not captured.

🎒 Skills

Reusable behaviors across projects. Drop .md files in:

• ~/.gg/skills/ for global skills (available everywhere)
• .gg/skills/ for project-specific skills

They get loaded into the system prompt automatically. The agent knows what it can do without you explaining it each session. Ctrl+S opens a pane to browse and toggle them.

📋 Project guidelines

Drop a CLAUDE.md or AGENTS.md in your repo root (or any parent directory). GG Coder picks it up automatically.

Your rules. Your conventions. The agent follows them.

👥 Community

• YouTube @kenkaidoesai — tutorials and demos
• Skool community — come hang out
• GitHub @KenKaiii

📄 License

MIT