Early version v0.1.0 · Native agents, one terminal workflow.Current status

Navigation

Browse documentation

Account configuration

Select a second account by giving a provider entry its own environment.

On this page

Several accounts of one provider

An env entry changes the environment of one provider process only. Which variable selects an account is the provider’s business:

Provider Variable
Claude Code CLAUDE_CONFIG_DIR
Codex CODEX_HOME
json
{
  "providers": [
    { "id": "claude", "label": "claude-work",
      "env": { "CLAUDE_CONFIG_DIR": "D:\\accounts\\work" } },
    { "id": "claude", "label": "claude-personal" },
    { "id": "codex" }
  ]
}

Each entry needs a unique label. It defaults to the id, so give every account of the same provider its own label. Cooldowns are tracked per entry, so one account resting does not rest the other.

A second account has its own settings directory, which means its own plugins and settings too. Switching between accounts of the same provider also switches that account’s plugins.

Authentication

uuldana-cli does not read the credentials stored in those directories, and none of an agent’s own conversation files.

If a login expires, the provider’s own screen asks you to sign in again, inside the uuldana-cli session. Handoff does not migrate authentication: the next provider uses its own account, and approvals granted in one provider are not portable authorization.

Environment values from your configuration are redacted in debug output.

Search documentation

Start typing to search all articles.

↑ ↓ navigate · Enter openEsc close