Skip to content

Dashboard and Desktop App

EctoSpace edited this page Nov 13, 2026 · 1 revision

Dashboard and Desktop App

IronVise has two graphical front ends: the Observer dashboard served by ironvise serve, and the desktop app, which bundles the server with its own SQLite ledger. The screen-by-screen guide is docs/guides/desktop-app.md.

Observer dashboard

ironvise serve

serve prints an access token. Open http://localhost:3000?token=<token>. REST calls use Authorization: Bearer <token>. Set your own token with OBSERVER_TOKEN.

  • Listens on 127.0.0.1:3000 by default (ECTO_BIND_HOST, ECTO_BIND_PORT). If you bind to 0.0.0.0, the bearer token is the only access control: put TLS and a reverse proxy in front.
  • ironvise health probes /api/status and exits 0 when it answers 200.
  • Live events stream to the dashboard over SSE. Several serve processes can share one PostgreSQL database; see docs/guides/scaling.md.
  • When it runs with demo-grade settings, startup logs WARN INSECURE DEMO MODE. See Configuration.

Desktop app

The desktop app (Tauri 2) starts an embedded backend on a random local port. Nothing listens beyond 127.0.0.1. Installers are on the releases page; see Getting Started.

First start: the setup wizard

Runs once.

  • Express uses the embedded SQLite ledger and a local Ollama if one is installed or running.
  • Custom asks for:
    1. Database: PostgreSQL (a URL), SQLite (the default for one machine), or in-memory (lost on restart).
    2. Model provider: Ollama (install or connect), Anthropic or OpenAI. Other OpenAI-compatible servers (LM Studio, llama.cpp, vLLM, MLX-LM, LocalAI) are set up afterwards in Settings.
    3. Provisioning: saves the choices and, for Ollama, pulls the model.

Command palette

Cmd+K (macOS) or Ctrl+K opens it anywhere: every reachable screen, every Settings section, and the Appearance theme.

Screens

Screen What it does
Home Type a goal and Run. Each proposed action is checked by tripwire, policy and (if on) the semantic guard before it runs, and every step is signed into the ledger. When a policy needs human approval, the run pauses on an Approval required card.
History Every session, newest first. Verify re-checks the chain and signatures; Certificate exports an .elc and says how it is signed; Report; Verifiable Credential.
Policy Edit TOML policies. Use for new runs applies one to Home runs. The four built-in packs are read-only. ECTO_POLICY_PATH in the environment wins.
Tripwire Allowed paths, allowed HTTP domains, banned command patterns, minimum justification, Require HTTPS. Try a command names the rule that refuses it.
Access API tokens (agent or auditor role, optional expiry, shown once) and webhooks to a SIEM or any HTTPS endpoint.
Settings Ledger, Model, Semantic guard, Agent, Appearance, developer tools. Save and Discard at the bottom; a search field filters sections and fields.

The semantic guard is off by default in the app. Turn it on in Settings and choose its provider and model explicitly. It runs in a separate process and fails closed: if its model cannot be reached, every action is refused. If the environment sets GUARD_REQUIRED, the stricter value applies.

Show developer tools adds Testing, Prometheus, Live Feed and Dev Hub to the sidebar.

Where data is kept

What Where
Ledger ectoledger.db in the app data folder
Settings settings.json in the app data folder
API keys entered in Settings The OS credential store (macOS Keychain, Windows Credential Manager, Secret Service on Linux). Never in settings.json.
Tripwire and policies tripwire.json and policies/*.toml in the app data folder

The app data folder:

OS Folder
macOS ~/Library/Application Support/io.ectoledger.agent-ledger
Windows %APPDATA%\io.ectoledger.agent-ledger
Linux ~/.local/share/io.ectoledger.agent-ledger

These names come from the bundle identifier, which is unchanged since EctoLedger, so upgrades keep your data. Point the CLI at the same folder with ECTO_DATA_DIR to share settings with it.

Troubleshooting

You see What to do
"This provider listed no models" Start the provider (for LM Studio, load a model and start its server), check the address, then Refresh. Hosted providers need an API key first.
Test connection: "refused the request (401)" The API key is wrong or missing. Save it again in Settings, Model.
"Base URL must point at localhost" Addresses typed in the app must be on this machine. Use OLLAMA_BASE_URL or OPENAI_BASE_URL in the environment for a remote server.
Every action is refused with the guard on The guard's model cannot be reached or is not chosen. Check Settings, Semantic guard.
macOS asks whether IronVise may use its keychain item Expected once after installing a new build. Allow it, or enter the key again.
"IronVise could not open its ledger" at start Your data has not been changed. Do not delete the file; keep it and report the message with the version you upgraded from.
A certificate is "unsigned" Expected for audit runs without an issuer key. Run ironvise issuer-key init.

Clone this wiki locally