LatentWork

Settings & modes

Nearly everything is configurable from the in-app Settings. This page covers the settings that matter most, the config file behind them, and how host vs client mode works.

Settings you'll use most

Setting	What it controls
AI	Gateway URL and LatentStack API key, with a Test Connection button
Skills	Install and manage Skills
Extensions	MCP servers and engine plugins
Appearance	Theme and interface preferences
Usage	Cost and token usage over time
Debug	Export a runtime report and developer logs

The config file

Most people never touch this — the Settings UI writes it for you — but LatentWork stores its configuration at ~/.latentwork/config.json. The keys you might see:

json

{
  "selected_model": "anthropic/claude-sonnet-4-5",
  "latentrouter_url": "https://latentstack.dev/v1",
  "api_key": "ls-your-key",
  "selected_project_id": "your-project-id"
}

Prefer the UI

Editing this file by hand is rarely needed. Use Settings → AI to change the gateway and key so the app can validate the connection for you.

Host mode vs client mode

Host mode (default) — the app runs the agent engine locally on your machine. This is what most people use.
Client mode — instead of running the engine locally, connect to a remote LatentWork server from the Cloud settings, to use a shared or hosted instance.