Skip to main content
zmeel configure lets you update specific sections of your Zmeel config interactively, without re-running the full onboarding wizard. Each section has its own set of prompts. After you answer them, the config file is updated immediately.
You must run zmeel onboard at least once before using zmeel configure. If no config file exists, configure exits with an error.

Usage

Without --section, you are prompted to pick a section from a menu. With --section, the named section opens directly and the command exits when that section is saved — no loop.

Options

string
The configuration section to update. When provided, the command opens that section directly and exits after saving. Accepted values: llm, database, logging, server, storage, secrets.
string
Path to the config file. Defaults to ~/.zmeel/instances/default/config.json.
string
Data directory root. Isolates all state from ~/.zmeel.

Sections

section
LLM provider and API key. Supported providers: claude (Anthropic) and openai. You can clear the LLM config to remove an existing provider.
section
Database connection. Choose between embedded PostgreSQL (no external dependency) or an external PostgreSQL connection string.
section
Log level and output mode. Controls where Zmeel writes its server logs.
section
Deployment mode, port, public URL, and allowed hostnames. Also configures the auth base URL mode — use explicit when your instance is behind a reverse proxy with a custom domain.
section
Storage provider. Choose local_disk for single-machine deployments or s3 for S3-compatible object storage. local_disk is the default.
section
Secrets encryption settings. Controls the provider and key file path used to encrypt agent credentials and other sensitive values at rest.

Examples

Config file location

Changes are written to ~/.zmeel/instances/default/config.json. To manage a different instance, pass --data-dir or --config:
After changing configuration, run zmeel doctor to verify that the updated settings are valid and that all services can connect.