Configuration
The server and the client keep separate configuration with different resolution rules. Read the section for the binary you are configuring; they do not share a precedence chain.
The server’s configuration
Section titled “The server’s configuration”Tapes stores configuration and credentials in a .tapes/ directory. Resolution order is:
--config-dir <directory>;.tapes/in the current directory;~/.tapes/;- built-in defaults if none exists.
Create a project-local directory with defaults or a provider preset:
tapes inittapes init --preset anthropic# presets: openai, anthropic, ollamaA project-local .tapes/ takes precedence over the home directory. This is useful for per-project provider and database settings, but is also the first place to check when an expected global setting appears ignored.
Precedence
Section titled “Precedence”For commands that bind a setting, precedence is:
- CLI flag;
TAPES_...environment variable;config.tomlvalue;- built-in default.
Dots become underscores in environment names, for example TAPES_PROXY_LISTEN and TAPES_STORAGE_POSTGRES_DSN.
Manage settings
Section titled “Manage settings”tapes config listtapes config get proxy.providertapes config set proxy.provider anthropictapes config set proxy.upstream https://api.anthropic.comUseful supported keys include:
| Key | Purpose | Default |
|---|---|---|
storage.postgres_dsn |
Capture and derived PostgreSQL database | unset |
proxy.provider |
anthropic, openai, or ollama |
ollama |
proxy.upstream |
Upstream provider base URL | http://localhost:11434 |
proxy.listen |
Proxy listen address | :8080 |
proxy.project |
Session project tag | auto-detected from Git when unset |
api.listen |
Read API listen address | :8081 |
api.web_ui |
Minimal browser UI at / |
false |
ingest.listen |
Private ingest listen address | :8082 |
client.proxy_target |
Proxy URL used by clients | http://localhost:8080 |
client.api_target |
API URL used by clients | http://localhost:8081 |
vector_store.target |
pgvector PostgreSQL DSN | primary PostgreSQL DSN when unset |
embedding.provider |
ollama or openai |
ollama |
embedding.target |
Embedding service URL | http://localhost:11434 |
embedding.model |
Embedding model | embeddinggemma |
embedding.dimensions |
Vector dimensions | 768 |
opencode.provider / opencode.model |
Saved OpenCode choice | unset |
telemetry.disabled |
Disable CLI usage telemetry | false |
update.disabled |
Disable update checks | false |
cassettes = ["https://host/openapi"] is a top-level array for operator-managed cassette OpenAPI URLs; it is not a dotted config set field. See Cassettes for the manifest, deployment responsibilities, and runtime behavior.
Example
Section titled “Example”version = 0
[storage]postgres_dsn = "postgres://tapes:tapes@localhost:5432/tapes?sslmode=disable"
[proxy]provider = "anthropic"upstream = "https://api.anthropic.com"listen = ":8080"
[api]listen = ":8081"
[client]proxy_target = "http://localhost:8080"api_target = "http://localhost:8081"
[vector_store]target = "postgres://tapes:tapes@localhost:5432/tapes?sslmode=disable"
[embedding]provider = "ollama"target = "http://localhost:11434"model = "embeddinggemma"dimensions = 768Store provider secrets with tapes auth openai or tapes auth anthropic, or use the provider’s environment variable. Do not put API keys in config.toml.
The client’s configuration
Section titled “The client’s configuration”tapesctl keeps one file, ~/.tapes/config.toml, and reads exactly one key
from it:
tapes-url = "http://localhost:8081"Write it with:
tapesctl config set tapes-url http://localhost:8081tapesctl config get tapes-urltapesctl config pathThree differences from the server’s rules are worth stating outright:
- There is no project-local layer. The client always reads
~/.tapes/config.toml, whatever directory you run it from. A.tapes/in the current directory configures the server and is invisible to the client. - The chain has three links, not four. A
--tapes-urlflag beats theTAPES_URLenvironment variable, which beats the configured value. With none of the three, a command that needs a server fails and names all three sources rather than guessing a host. - One URL covers two servers. The read commands want the read API and the
capture commands want the ingest API, so whichever you configure, the other
needs
--tapes-urlon the command line. See Two ports, two jobs.
config set edits the file in place, so comments, ordering, and keys the client
does not know about survive it. config get lists only keys it knows and that
are set, so empty output does not mean an empty file.
The file sits beside ~/.tapes/logs, ~/.tapes/skills, and ~/.tapes/codex-app
rather than under $XDG_CONFIG_HOME, so one directory holds everything the
client writes.