Skip to content

lore config

Manage API credentials and view configuration.

Synopsis

lore config <set-key|delete-key|list-keys>

What Does This Do?

lore config manages the API keys that power Angela's AI features. It stores keys securely in your OS keychain so they never end up in a file that could be accidentally committed.

Analogy: It's like the settings page of an app. You don't use it every day, but when you need to connect a new service, this is where you go.

Real World Scenario

You just got your Anthropic API key. Time to unlock Angela:

lore config set-key anthropic
# Enter API key: [hidden]
# ✓ Key stored securely

Now lore angela polish works. Your key is in the OS keychain — never in a plaintext file.

lore config

Subcommands

Subcommand Description
set-key <provider> Store an API key securely
delete-key <provider> Remove a stored API key
list-keys Show status of all providers

Known providers: anthropic, openai, ollama

Flags

This command has no flags. Provider is specified as an argument.

How Key Storage Works

Lore tries the most secure option first, then falls back:

graph TD
    A[lore config set-key] --> B{OS Keychain available?}
    B -->|Yes, macOS| C[Keychain Access]
    B -->|Yes, Linux| D[secret-service / libsecret]
    B -->|Yes, Windows| E[Credential Manager]
    B -->|No| F[.lorerc.local fallback]
    F --> G[File mode 0600 — owner-only read]
  • macOS: Keychain Access (the same system that stores your WiFi passwords)
  • Linux: secret-service via D-Bus (GNOME Keyring, KDE Wallet)
  • Windows: Windows Credential Manager
  • Fallback: .lorerc.local with chmod 600 (readable only by you)

Examples

Set up Anthropic (Claude)

lore config set-key anthropic
# → Enter API key: [hidden — no echo]
# → ✓ Key stored for anthropic

# Verify
lore config list-keys
# anthropic     stored
# openai        not set
# ollama        stored

Set up OpenAI (GPT)

lore config set-key openai
# → Enter API key: [hidden]
# → ✓ Key stored for openai

Set up Ollama (Local — No Key Needed)

# Ollama runs locally, no API key required
# Just configure the endpoint in .lorerc:

# .lorerc
ai:
  provider: "ollama"
  model: "llama3"
  endpoint: "http://localhost:11434"

Remove a key

lore config delete-key anthropic
# → ✓ Key removed for anthropic

Check all providers

lore config list-keys
# anthropic     stored
# openai        not set
# ollama        not set

CI/CD (No Keychain)

In CI, use environment variables instead:

export LORE_AI_API_KEY="sk-ant-..."
export LORE_AI_PROVIDER="anthropic"
# Angela commands will use these automatically

Common Questions

"Where exactly is my key stored?"

Run lore config list-keys. If the status shows "stored," the key is in your OS keychain. If you're on the fallback, it's in .lorerc.local (gitignored, chmod 600).

Keychain backend by platform:

Platform Backend Tool used
macOS System Keychain security add-generic-password / find-generic-password
Linux GNOME Keyring / KWallet secret-tool store / secret-tool lookup
Windows Credential Manager Fallback to .lorerc.local (native keychain planned)

"I set the key but Angela still says 'no provider configured'"

Two things are required: 1. The key (via lore config set-key) 2. The provider name in .lorerc:

ai:
  provider: "anthropic"   # tells Angela which provider to use
  model: "claude-sonnet-4-20250514"

The key alone is not enough — Lore also needs to know which provider to route it to.

"Can I have different keys per project?"

Yes. .lorerc.local is per-project (it lives in your project root, not globally). Different projects can use different providers and keys.

"Is it safe?"

  • OS keychain: same security as your saved passwords
  • .lorerc.local fallback: file mode 0600 (only you can read)
  • .lorerc.local is in .gitignore — never committed
  • Keys are scrubbed from error messages (Angela never leaks your key in output)

Tips & Tricks

  • Prefer lore config set-key over editing .lorerc.local manually — the keychain is more secure.
  • CI/CD: Use the LORE_AI_API_KEY env var — no keychain needed in CI.
  • Ollama = free: No API key, no cost. Ideal for experimenting before committing to a paid provider.
  • Rotate keys: Run delete-key then set-key to replace an expired or compromised key.
  • Validate after setup: Run lore angela draft on any document to confirm the provider is working.

Exit Codes

Code Meaning
0 Success
1 Error (invalid provider, keychain unavailable)
3 Invalid arguments (unknown provider name)

See Also