config set

What It Does

config set updates one key in .ragit/config.toml using the repository-aware config loader and writer.

When To Use / When Not To Use

When to use it

• You want to change output, ingest, storage, or embedding settings.
• You want a scriptable way to change config without editing TOML by hand.

When not to use it

• You only want to inspect current values. Use status.
• You want to initialize missing defaults. Use init.

Syntax

pnpm ragit config set <key> <value> [--cwd <path>]

Arguments And Options

• <key>: The dotted config key to update.
• <value>: The value to store.
• --cwd <path>: Run against another repository.

Input And Output Contract

• Input is positional only.
• Output is a plain stdout confirmation message. This command does not currently expose a JSON envelope.

Examples

Human terminal flow:

pnpm ragit config set output.format markdown

Agent-oriented flow:

pnpm ragit config set ingest.supported_types '["adr","spec"]'

Failures And Cautions

• Invalid keys or invalid values fail before the config file is written.
• For real providers, use embedding.provider, embedding.model, embedding.base_url, embedding.timeout_ms, embedding.cache_enabled, and embedding.cache_dir as the supported knobs. embedding.dimensions and embedding.version are legacy-only and only remain meaningful for local-placeholder.
• Changing the target embedding provider does not rewrite the persisted store contract by itself. Follow up with migrate embeddings when status reports embedding.needsMigration=true.
• embedding.cache_dir must stay inside the repository root. If it points outside the repo, cache writes are disabled and doctor reports the config as invalid.
• Because output is text-only, agents should validate follow-up state with status.

Related Commands

• status
• doctor
• migrate embeddings
• init