quint-code

Migrating from 5.0 to 5.1

Version 5.1 moves the database out of your repository into your home directory. This is a one-time migration — your data is preserved automatically.

What changed and why

In 5.0, the SQLite database lived at .quint/quint.db inside your repo. This caused problems:

  • Binary SQLite files can't be merged in git — team collaboration was impossible
  • Each project was isolated — no cross-project decision recall
  • The database cluttered git status and diffs

In 5.1:

  • Database moves to ~/.quint-code/projects/<project-id>/quint.db
  • Only markdown projections stay in .quint/ — human-readable, git-friendly, designed for code review
  • A new .quint/project.yaml identifies your project with a stable ID
  • Cross-project decision recall works automatically via a shared index

How to migrate

Update the binary, then re-run init in each project:

# Update quint-code
curl -fsSL https://quint.codes/install.sh | bash

# In each project directory
cd your-project
quint-code init

Init will:

  1. Generate .quint/project.yaml with a unique project ID
  2. Copy your existing .quint/quint.db to ~/.quint-code/projects/<id>/quint.db
  3. Add quint.db to .quint/.gitignore
  4. Populate the cross-project index with your existing decisions

All your decisions, problems, notes, and evidence are preserved.

After migration

Verify it works: 

/q-status

You should see your existing decisions and problems. If the MCP connection fails, make sure the new binary is in your PATH and restart your AI tool.

Delete the old database

Once you've confirmed everything works, delete the old database from your repo: 

rm .quint/quint.db
git add .quint/.gitignore
git commit -m "chore: remove old quint database, now in ~/.quint-code/"

Commit .quint/ as your knowledge base

The .quint/ directory now contains only markdown files and project.yaml. These are your project's engineering knowledge base — commit them: 

git add .quint/
git commit -m "chore: add quint knowledge base — decisions, problems, notes"

This is intentional. Decision records, problem cards, and notes in .quint/ are designed for code review. When you create a decision, a markdown file appears in your PR diff. Reviewers can see and comment on engineering decisions alongside code changes.

What if I don't migrate?

The 5.1 MCP server detects old .quint/quint.db files and blocks all tool calls with a message asking you to run quint-code init. Your data is safe — it just won't work until you migrate.

Multiple projects

Each project gets its own database in ~/.quint-code/projects/, identified by the ID in .quint/project.yaml. Run quint-code init in each project separately.

After migrating multiple projects, cross-project recall kicks in: when you frame a new problem in one project, related decisions from other projects surface automatically.