Configuration reference
adept config reads and writes project settings. Sets are strict-typed: an invalid value fails
at parse time with the allowed list, so a typo never corrupts the config file.
adept config list # all keys, current values, allowed valuesadept config get mode # print one valueadept config set mode copy # set one value (validated)adept config unset mode # clear back to defaultAdd --json to list for an array of {key, value, allowed, help} objects.
Only the typed scalar keys below (plus the grouped llm.* fields) are exposed through
config get/set. Harness enablement lives under adept harness
and library remotes under adept library; they are stored
in the same file but managed by their own commands.
| Key | Type | Default | Effect |
|---|---|---|---|
mode |
symlink | copy |
symlink |
How canonical skills materialize into each harness: a symlink back to the canonical file, or a copied file. See Layouts. |
scan.onInstall |
true | false |
on when an LLM provider is configured | Run the safety scan and LLM intent pass before skill install. |
scan.blockSeverity |
critical | high | medium |
critical |
Lowest scan severity that aborts an install. |
The llm provider is grouped. config list surfaces its three fields for a complete view, but
you set them through the config llm subcommand, not config set:
| Key | Effect |
|---|---|
llm.provider |
Current provider name (anthropic or ollama), or (unset). |
llm.model |
Model override; provider default when unset. |
llm.endpoint |
Endpoint override, for example a self-hosted Ollama. |
LLM provider config
Section titled “LLM provider config”Safety scans can add an LLM intent pass on top of the static rules. config llm records which
provider to use. API keys are never stored in the config: they are read from the environment at
call time.
export ANTHROPIC_API_KEY=sk-...adept config llm set anthropic # provider: anthropic | ollamaadept config llm test # health-ping the configured provideradept config llm unset # forget the provider
# override the model or endpointadept config llm set anthropic --model claude-3-5-sonnet-latestadept config llm set ollama --endpoint http://localhost:11434Supported providers are anthropic and ollama. Setting a provider flips scan.onInstall on
by default. See Safety scans and LLM config for how the pass is
used.
Scope: project vs global
Section titled “Scope: project vs global”By default config operates on the current project. Pass --global to read or write the
home-level scope instead (the harness config adept applies outside any project):
adept config list --globaladept config set mode copy --globalSee Scopes for when each applies.
Where config lives on disk
Section titled “Where config lives on disk”Project config is a single JSON file at:
<project>/.adeptability/config.jsonIt holds the typed keys above alongside harness state, materialization mode, and adapters.
Writes are atomic. Prefer the config commands over hand-editing so values stay validated.