Setting up AI (Providers & Keys)

Last updated 24 days ago

Setting up AI (Providers & Keys) ​

Liza uses AI in two places: the AI assistant (chat/analysis in the project context) and the coding agents (Claude Code tab).

Your own AI access required

There is currently no hosted Liza AI. You use your own AI access – stored as an API key, centrally for the organization or personally per user. The most common choices are Claude and Mistral.

Supported providers ​

  • Claude (Anthropic)
  • Mistral
  • Also possible: ChatGPT (OpenAI), Gemini (Google), Perplexity (research)

Create a key at the respective provider (e.g. console.anthropic.com for Claude, console.mistral.ai for Mistral) and store it in Liza.

Organization: central keys (Admin) ​

Settings → Organization → AI (Einstellungen → Organisation → KI)

  • Store the providers' central API keys (e.g. Claude, Mistral). Assigned members then use AI without a key of their own – the organization's key is used.
    • Either enable it for all members or assign it to specific people (under Settings → Users (Einstellungen → Nutzer)).
  • Provider usage: optional cost tracking per provider.

Personal: your own keys ​

Settings → Personal → AI & Connections (Einstellungen → Persönlich → KI & Verbindungen)

Four tabs:

TabPurpose
My AI Keys (Meine KI-Keys)One key of your own per provider – applies everywhere (assistant + coding agent)
Coding Agent (Coding-Agent)Set up coding agents (Desktop only) – see Agents
Liza Access (Liza-Zugang)API keys & MCP for programmatic access (developers)
Usage (Verbrauch)Your AI token usage

Precedence: Your personal key takes precedence over the org key. On the desktop it is also stored locally, encrypted (Keychain), so the coding agent can use it without a server.

Web vs. Desktop ​

Web (Browser)Desktop app
AI assistant (with your own access)✅✅
Personal/org AI keys✅✅ (+ local Keychain)
Coding agents (Claude Code)❌✅
Edit local files❌✅

The coding agents run only in the desktop app, because they edit files locally.