Workspace settings

Settings in Deckgauge isn't a single hub yet — it's two focused screens. Here's what each one controls and where it takes you.

deckgauge · Settings · Advisor
Deckgauge Hosted
🔑Your own API key
🖥Local Ollama

Provider cards on the Advisor settings screen.

What it does, and where the data comes from

Visiting /settings redirects straight to /settings/timesheet-statuses — there's no settings landing page to browse. Two screens exist behind that redirect today: Timesheet statuses, configured per org tree, and Advisor, configured once for the whole instance.

How to configure workspace settings

  1. Timesheet statuses — pick which board statuses count as active work, per org tree. Switch between org trees with the tabs at the top; the timesheet only counts time spent in the statuses you select here, and hides everything else (Blocked, Code Review, and so on). See In-progress statuses.
  2. Advisor — connect a model so the Advisor can answer questions grounded in a board's real metrics. Choose Your own API key (Anthropic) or Local OllamaDeckgauge Hosted is shown but disabled in the open-source build. Fill in the key/model or base-URL/model, then Test connection before Save. See Advisor, Providers, and Local agent.

Under the hood

Each provider choice shows its own data-handling line before you save: an Anthropic key means board metrics go to Anthropic's API on every question; Local Ollama means nothing leaves your infrastructure. A saved API key is never echoed back — the field shows a placeholder saying a key is already stored, and typing a new value replaces it.

If it looks wrong

SymptomCauseFix
Following a link to "Settings" lands you on Timesheet statuses, not something else/settings always redirects there — there's no general settings pageBookmark /settings/timesheet-statuses or /settings/advisor directly
Timesheet statuses page says "No org trees found"No org tree has been created yetCreate an org tree first — see Org trees
Advisor's "Test connection" fails for Local OllamaThe base URL isn't reachable from where the app server runs (e.g. localhost from inside a container)Point the base URL at a host reachable from the app, such as your machine's LAN address or a Docker-bridge hostname
"Deckgauge Hosted" is greyed outIt's a cloud-only option, disabled in the self-hosted/open-source buildUse your own Anthropic key or a local Ollama instance instead

Related

Last updated