Codifix gives coding agents and developers durable project knowledge: decisions, fixes, evidence and handoffs that the next session can retrieve with citations. It captures and curates work, stores it in PostgreSQL with pgvector, and makes it available through a browser, TUI, CLI and MCP.
Use one local project or route work to separately operated knowledge areas. Configured teams can share reviewed knowledge privately, ask explicit expertise questions, and synchronize selected knowledge for offline use. These workflows require their own setup and permissions; a local query does not automatically search other areas.
Website · Documentation · Codifix v3.0.0-rc.1 prerelease
v3.0.0-rc.1 is available as a prerelease.
This README and the website describe current main, which includes fixes newer
than those package bytes. Use the release inventory for the exact package
commit. Mac and Windows packages are unsigned; stable 3.0.0 is not released.
Windows packages remain a preview of client/operator functionality, not a
complete native server stack. Use codifix urls to inspect the configured
application URLs.
The reproducible demo needs only Docker; it starts PostgreSQL with pgvector, the service, and the web UI. Clone the repository and start the stack:
git clone https://github.com/3vilM33pl3/codifix
cd codifix
docker compose upIn a second terminal, load the demo project and ask one question:
docker compose exec codifix codifix demo
docker compose exec codifix codifix query --project demo --question "How does reinforcement work?"Open http://localhost:4040 for the browser UI, or run
docker compose exec codifix codifix tui for the terminal UI. Follow the
Quickstart for the complete
demo path.
If you are joining an existing company installation, follow Team setup and use the approved company origin and device enrollment. For a new standalone installation, prerequisites, and verification, start with the Install guide or download the v3.0.0-rc.1 prerelease. Upgrading an existing installation? Read the Update guide first: the v3 transition requires a breaking reinstall, not an in-place upgrade. The setup wizard configures the machine once and the project you are working in:
codifix wizard --global
cd /path/to/your-project
codifix wizard --dry-run
codifix wizard
codifix doctorNative installations need a PostgreSQL database with pgvector; the install
guide covers local, hosted, Windows, and package-specific paths. The Windows
x86_64 MSI is per-user, installs under
%LOCALAPPDATA%\Programs\Codifix, and adds its bin directory to the
user PATH.
Capture finished work, query before making a change, resume after an interruption, and inspect or recover when something looks wrong. The Daily workflow gives the commands and the TUI and Web UI make the stored evidence easy to inspect. Before writing, verify the destination using Areas and projects. The Jobs reference explains why embedding or consolidation can still be pending after curation succeeds.
For configured teams, private sharing and expertise and offline synchronization explain what is shared, what remains local, and how to inspect freshness and pending work.
- Codex Desktop plugin — the supported MCP connection and desktop workflow skill.
- Agents — project setup and agent-facing workflows.
- MCP — project-memory retrieval and optional explicitly authorized expertise/control tools over stdio or Streamable HTTP.
Use one Codifix MCP connection per client. The Codex plugin guide explains how to avoid duplicate tool registration and how to verify the active project.
- Cited answers from lexical, semantic, relation, and code-graph retrieval.
- Project memories with provenance, curation, review proposals, and durable re-entry briefings.
- Local TUI and browser UI for memories, activity, review, watchers, and runtime health.
- Knowledge-area routing, reviewed private publications, and explicitly authorized expertise exchange.
- Selective offline knowledge, company project/device onboarding, and durable background jobs with inspection and confirmed retries.
- Coding-agent integration through the CLI, repo-local skills, and MCP.
- Repeatable evaluation with paired ablations, immutable artifacts, gates, and cost/latency reporting.
Evaluation records measure different things; they are not a single release score. The 15 October capture-quality pilot records a synthetic offline rules baseline and transport/replay tests. It made no live Jev calls and establishes no provider quality or cost advantage.
The 6 July memory-quality reference is a historical local run with a red adversarial-stale gate. The 3 May Docker benchmark is separate historical evidence from a different suite. Neither result proves current product-wide coding improvement.
The R3 campaign status records its own frozen inputs, isolation requirements and remaining evidence. Fixture tests and CI recovery are not a new paid campaign or ROI result.
For methodology and commands, see the evaluation guide and CLI reference.
The public site is organised with an essentials-first path and optional deep dives:
- Quickstart
- Install
- Areas and projects
- Team setup
- Daily workflow
- Federation and expertise
- Offline and synchronization
- Help
- Operations
- How it works
- CLI reference
The docs-site/ directory contains the public site;
the docs/ tree contains the detailed in-repository
manual and developer reference.
Start with Contributing, the developer documentation, and the dev-stack guide. The development stack is isolated from packaged installations; its setup and verification steps belong in that guide rather than this README.
Codifix is dual-licensed:
- Open source: GNU Affero General Public License v3.0 or later; see LICENSE.
- Commercial: available under a separate commercial license; see LICENSE-COMMERCIAL.md.
Contributions are accepted under the repository's open-source license unless explicitly agreed otherwise in writing. See Contributing.