with all optional extras (incl. memory)
just install-extra # e.g. just install-extra postgres
just install-memory # memory extra (lancedb + sentence-transformers)
just install-local # engine dev: uv sync + build
/gradlew :exposed-r2dbc-tests:test_h2_v2 # R2DBC Tests with H2
```
#### Test with Postgres
```bash
./gradlew test_postgres # All modules with Postgres
./gradlew :exposed-tests:test_postgres # JDBC Tests with
multi-row `SELECT ... FOR UPDATE` MUST carry an explicit `ORDER BY `.** Without it Postgres locks in scan order, which differs per plan, so two writers with overlapping sets can cycle
agents how to create proposals when API access is needed.
- **Dual database backend (SQLite / Postgres)**: By default, all state lives in a single SQLite file (`~/.agent-vault/agent-vault.db` or `/data/.agent-vault/agent-vault.db` in Docker
external extractor plugin (`index.extractor_plugins`) from config — no fork. `gortex db schema --postgres ` ingests a live database's schema.
- **`analyze` is a 61-kind dispatcher** — beyond the structural kinds
used by local dev / the Supabase CLI.
2. **AWS AMIs** — the production Supabase-hosted Postgres image, built via
Nix + Packer + Ansible.
3. **Nix packages** — `nix build .#psql_15.bin` etc., the underlying
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.