Team and Project Config

Global vs project-local config

Docmancer supports two config scopes:

The global config is created automatically on first use. A project config is created explicitly with docmancer init.

How config resolution works

When you run any docmancer command, it checks for config in this order:

1. --config <path> flag (explicit, highest priority)
2. ./docmancer.yaml in the current working directory
3. ~/.docmancer/docmancer.yaml (global fallback)

This means if you create a docmancer.yaml in a project directory, all commands run from that directory will use it automatically, including a separate SQLite database.

Create a project config

cd my-project
docmancer init

This creates docmancer.yaml in the current directory with default settings pointing to a local .docmancer/ directory:

index:
  db_path: .docmancer/docmancer.db
  extracted_dir: .docmancer/extracted/

Add a vector_store: block to opt the project into hybrid retrieval. Without one, the project stays lexical-only:

index:
  db_path: .docmancer/docmancer.db
  extracted_dir: .docmancer/extracted/

vector_store:
  provider: qdrant
  collection: docmancer-myproject
  managed: true

The managed Qdrant binary is shared across configs, but each project's collection is isolated.

When to use project config

Use a project-local config when:

• You want project-specific docs that do not mix with your global index
• Multiple team members share the same project and you want a consistent docs setup
• You want to commit the config (but not the database) to version control

Shared index across agents

All agents on the same machine share the same SQLite index. If you add docs using Claude Code, Cursor can query them, and vice versa. This works because all agents call the same docmancer binary and read the same config file.

When using a project-local config, the shared index only applies to agents running from that project directory. Agents running from other directories will use the global config and its separate index.

Project-local skill installation

Some agents support project-level skill installation. This installs the skill file inside the project directory instead of globally:

docmancer install claude-code --project
docmancer install gemini --project
docmancer install cline --project

Project-level skills are useful when you want the docmancer skill to be available only within a specific project, or when you want to commit the skill file to version control so team members get it automatically.

Currently supported for: Claude Code, Gemini, and Cline.

Version control

Add to your .gitignore:

.docmancer/docmancer.db
.docmancer/extracted/
.docmancer/qdrant/
.docmancer/embeddings-cache/

Commit docmancer.yaml so team members share the same config. Each person runs docmancer add <url-or-path> or docmancer ingest ./docs to build their own local index.