config
View and update server configuration and storage credentials.
emend config
Inspect and modify the server-side configuration: extractor settings, LLM models, storage routing, and credentials.
config commands call the backend (GET /api/config, POST /api/set_config, GET /api/my_config). A reachable server is required. In the open-source local setup, all subcommands apply. Use config show to inspect current settings and config set to patch extractor, LLM, playbook, and evaluation settings directly.Command: emend config show
Print the current server configuration.
emend config show [--all]| Prop | Type |
|---|---|
--all | flag |
emend config showemend config show --all | jq '.profile_extractor_config'Command: emend config set
Update the server configuration by sending a JSON patch. Exactly one of --data or --file is required.
emend config set (--data '<json>' | --file <path>)| Prop | Type |
|---|---|
--data | str |
--file | path |
# Inline patchemend config set --data '{"llm_provider": "openai", "llm_model": "gpt-5"}' # Load from a fileemend config set --file configs/production.json # Using @path syntax with --dataemend config set --data @configs/production.jsonCommand: emend config storage
Show the storage credentials the server has on file for your organization. Calls GET /api/my_config.
emend config storage [--reveal]| Prop | Type |
|---|---|
--reveal | flag |
The default output masks secrets so it's safe to paste into bug reports. Pass --reveal when copying credentials to a new machine — you'll be asked to confirm before anything unmasked reaches the terminal.
Command: emend config pull
Pull server-side storage credentials down to a local .env so your machine can talk to the same backing store directly via the local lib. Currently only Supabase credentials can be pulled.
emend config pull [--force] [--env-file <path>]| Prop | Type |
|---|---|
--force | flag |
--env-file | path |
Behavior
- Refuses to pull non-Supabase storage types.
- Refuses to overwrite existing active credential lines unless --force is set.
- Creates the parent directory with 0700 permissions and writes the file with 0600 so the raw credentials never land as world-readable.
- Also writes
EMEND_URL/EMEND_API_KEYso the local lib knows how to identify itself on the next call.
# Pull to the default user-level envemend config pull # Pull to a project-local env, overwriting whatever is thereemend config pull --env-file ./.env --force