Config

The rensei config command reads and writes ~/.config/rensei/config.json - the file that stores your active auth context, default org and project, and the platform base URL. It does not store secrets (those live in the secret backend; see auth).

Config file location

Platform	Path
All	`~/.config/rensei/config.json`

The file is created automatically on first run. You can also set individual fields via global flags (--url, --org, --project) for a single command without touching this file.

Commands

`config show`

Display the current configuration:

rensei config show

Example output:

Context:   mark (user)
Org:       acme-corp
Project:   api-backend
URL:       https://app.rensei.ai

For machine-readable output:

rensei config show --json

{
  "activeContext": "mark",
  "org": "acme-corp",
  "project": "api-backend",
  "url": "https://app.rensei.ai"
}

`config set`

Set a specific config field:

rensei config set url https://app.rensei.ai

Field	Description
`url`	Platform base URL. Overrides `RENSEI_API_URL`. Default: `https://app.rensei.ai`

Org and project defaults are set by the setup wizard (rensei setup) and by --org/--project global flags, not by config set. Use rensei setup --project <slug> to change your default project.

`config reset`

Reset the config file to defaults. This clears the active context, org, project, and URL:

rensei config reset

config reset does not remove stored auth contexts or their tokens from the secret backend. Those persist in ~/.config/rensei/config.json under the contexts key. To fully remove a context and its token, use rensei auth remove.

Config file schema

The raw JSON structure of config.json:

{
  "activeContext": "mark",
  "org": "acme-corp",
  "project": "api-backend",
  "url": "https://app.rensei.ai",
  "contexts": [
    {
      "name": "mark",
      "kind": "user",
      "org": "acme-corp",
      "secretBackend": "keychain",
      "keychainService": "rensei-mark"
    },
    {
      "name": "ci-deploy",
      "kind": "org_token",
      "org": "acme-corp",
      "secretBackend": "encrypted_file",
      "encryptedFilePath": "~/.config/rensei/contexts/ci-deploy.enc"
    }
  ]
}

The contexts array is managed exclusively by rensei auth subcommands - do not edit it manually.

Precedence

Config values are resolved in this order (highest priority first):

Per-command flags: --url, --auth, --org, --project
Environment variables: RENSEI_API_URL, RENSEI_AUTH_TOKEN
~/.config/rensei/config.json (url, activeContext, org, project)
Compiled-in defaults (https://app.rensei.ai)

Daemon config

The daemon has a separate config file at ~/.rensei/daemon.yaml that is managed by rensei host install and rensei host capacity commands. See Host daemon for details.

Auth - managing auth contexts (auth add, auth activate)
Global flags - per-command overrides for URL, org, and project
Environment variables - RENSEI_API_URL, RENSEI_AUTH_TOKEN
Quick start - initial setup workflow

On this page