An AI coding agent that compounds project knowledge.
CyxCode is an open source developer tool for teams and builders who want an agent that works inside real repositories, remembers useful context, and turns repeated debugging work into reusable behavior.
What it is
Terminal-native, repo-aware, and model-flexible.
CyxCode can inspect code, explain unfamiliar systems, plan changes, edit files, run commands, use language-server context, and keep multiple sessions moving. You can use it from terminal, desktop, IDE, and GitHub workflows.
Why it exists
AI should not keep paying for the same discovery.
Most coding agents are powerful, but they often repeat the same context gathering and error diagnosis. CyxCode adds memory, recall, learned recovery patterns, and auditability so solved work can keep paying forward.
Upstream lineage
Forked from opencode, shaped for CyxCode workflows.
CyxCode is a fork of opencode.
CyxCode docs and releases cover the CyxCode-specific experience, while upstream settings and reference material can also be found in the
opencode docs.
Principles
Built for the boring parts of serious engineering
The goal is not a flashier chat box. The goal is a coding environment where the agent can act, remember, and improve without hiding what it is doing.
A coding agent where engineers already work
CyxCode runs close to your terminal, repository, commands, tests, and logs. It is built for the loop developers repeat all day: inspect, plan, edit, run, review, and continue.
Memory instead of cold starts
Project memory, semantic recall, and behavior versioning help CyxCode reuse decisions and fixes from earlier sessions instead of rediscovering them from scratch.
Deterministic help before model spend
When a known failure appears, CyxCode can match it with local patterns before another model call. When it misses, the handled error can become a reviewed pattern for next time.
Choice without lock-in
Use CyxCode Zen, your own provider keys, local models, GitHub Copilot, ChatGPT Plus/Pro, or other supported providers. The workflow stays yours.
How it feels in use
Ask CyxCode to understand a part of the project or plan a change.
Let it edit files, run commands, and use tools under permissions you control.
Save important project knowledge as memory instead of repeating it every session.
Approve learned recovery patterns when repeated failures are worth making deterministic.
Start with one repo.
Install CyxCode, run it where you already work, and let the project context build from there.