Configuration reference
The most-used environment variables for both services. Each repo’s README and settings module is the
authoritative, current list — this is the working subset. Nested settings use __ (double
underscore).
rvmc (research workbench)
| Variable | Meaning |
|---|---|
RVMC_AUTH_MODE | local (single-user, no IdP) or forward (multi-tenant behind Traefik+Authentik). See Auth modes. |
RVMC_AUTOPSY_URL | Base URL of the autopsy service rvmc dispatches to / reads reports from. |
| (golden storage, libvirt connection, ports) | Per the rvmc README — the controller needs libvirt/KVM and a golden-image store. |
The rvmc chat agent’s LLM is configured per the rvmc README (an OpenAI-compatible endpoint + key, same “bring your own” rule as autopsy).
artwork-autopsy
LLM (AUTOPSY_LLM__*)
| Variable | Meaning |
|---|---|
AUTOPSY_LLM__API_KEY | Your key. Empty or sk-nokey → stub reasoner (deterministic-only). Never logged. |
AUTOPSY_LLM__BASE_URL | OpenAI-compatible endpoint (https://api.openai.com/v1, a gateway, or a local Ollama/vLLM …/v1). |
AUTOPSY_LLM__ALIAS_AGENT | The model the analyst (agent) drives. |
The analyst runs with no token/step caps — your provider’s budget is the limit. See AI configuration and Bring your own AI.
Storage (AUTOPSY_STORAGE__*)
| Variable | Meaning |
|---|---|
AUTOPSY_STORAGE__BACKEND | local, drive (an artwork drive), or s3. |
AUTOPSY_STORAGE__ROOT | Root path for local/drive backends. |
| (S3 endpoint/bucket/keys) | For the s3 backend — per the autopsy README. |
Jobs (AUTOPSY_JOBSTORE__*)
| Variable | Meaning |
|---|---|
AUTOPSY_JOBSTORE__DATABASE_URL | PostgreSQL URL for the job store (the SKIP LOCKED claim loop). |
AUTOPSY_JOBSTORE__MAX_ATTEMPTS | Retries before a job is failed. |
Investigation (AUTOPSY_INVESTIGATE__*) & logging
| Variable | Meaning |
|---|---|
AUTOPSY_INVESTIGATE__MAX_SESSIONS | Max analyst sessions per run (the loop retries on an incomplete picture). |
AUTOPSY_INVESTIGATE__PROMPT | Which analyst prompt to use. |
AUTOPSY_LOG_LEVEL / --log-level | error/warning/info/debug. At debug the analyst emits its full tool transcript (every read-slice/grep/deep-read) — useful for dev. |
CLI vs. service
Autopsy can analyze a single bundle directly from the CLI (no queue) or run as an API + runner over
the Postgres job store. The CLI supports --yes (auto-confirm the preflight checkpoint in
non-interactive use) and a graceful cancel (SIGINT/SIGTERM → partial report). See the autopsy README.
Precedence
Environment variables override defaults; per-project settings (in a hosted deployment) override the
server defaults — notably the per-project bring-your-own-AI endpoint, which overrides
AUTOPSY_LLM__* for that project’s runs.