Quickstart

This is a single reproducible demo: start the bundled stack, load the demo project, and ask one question. It uses Docker only, so you do not need PostgreSQL, pgvector, or any API keys to see it work.

The first run builds the current source, including Rust and the browser UI, so allow time for the build. It is separate from the published native candidate. The Compose file uses fixed demo credentials and publishes port 4040; use a trusted local machine and keep production data out of this disposable demo.

1. Start the stack

From a clone of the repository:

git clone https://github.com/3vilM33pl3/codifix
cd codifix
docker compose up --build

That starts PostgreSQL with pgvector, the Codifix service, and the web UI. When it settles, the service is listening on http://localhost:4040.

2. Load the demo project

In another terminal:

docker compose exec codifix codifix demo

This seeds a project called demo with a small, curated set of memories about Codifix itself.

3. Ask it something

docker compose exec codifix codifix query --project demo --question "How does reinforcement work?"

The keyless stack retrieves cited demo memories. Generated prose and semantic retrieval depend on configured providers; insufficient evidence is reported explicitly.

4. Explore

docker compose exec codifix codifix tui

The terminal UI lets you browse and search every memory, inspect where each came from, and open the codifix graph. The web UI at http://localhost:4040 shows the same data with wider panes and a 3D graph view.

Next steps

  • Install - native install, prerequisites, configuration, and verification.
  • Daily workflow - capture, query, resume, inspect, and recover.
  • Areas and projects - verify the destination for knowledge.
  • Team setup - join an existing company installation.
  • How it works - memories, retrieval, reinforcement, and the code graph.

© 2026 Olivier Van Acker (3vilM33pl3). Codifix is AGPL-3.0-or-later with commercial licensing available.