Tegoby Attention SpanBlogBook a demo

Use the dashboard

Updated

The dashboard shows every run on this machine, lets you answer the requests Tego holds for you, and stops a run. It runs on your own machine, and only you can open it.

On this page

Start it

In a plain terminal, as yourself (never with sudo, and not from inside a tego run):

Terminal
tego serve --open

Output

Tego dashboard: http://127.0.0.1:8484/?t=0ab4c708b2775be17e4d67f247ea774b
  ledger: /home/dana/.tego/runs (from default), 1 run
  chains: checked against /home/dana/.tego/chain.log

It opens your browser, signed in. To open it in another browser, use the printed link with its token, not the bare address. If port 8484 is busy, pass --addr 127.0.0.1:<port>. Ctrl-C stops it.

The Tego dashboard Overview in its light theme: a red banner reading 1 run leaked secrets, the line 0 running, 2 runs, 4 blocked, tiles for Needs you 0, Running now 0, Blocked 4 and Record Verified, 2 runs, and a Detections table of blocked actions by severity and channel. The Tego dashboard Overview in its dark theme: a red banner reading 1 run leaked secrets, the line 0 running, 2 runs, 4 blocked, tiles for Needs you 0, Running now 0, Blocked 4 and Record Verified, 2 runs, and a Detections table of blocked actions by severity and channel.
Overview. What needs you first, then approvals waiting, runs running now, blocked actions and the record check.

What each page shows

  • Overview: what needs you first, then approvals waiting, runs running now, blocked actions and the record check.
  • Detections: every blocked action that matters, High first, filtered by severity and by files, programs or network.
  • Runs: every run, running ones first, with its status, secrets verdict and protection level.
  • A run: its verdict sentence and the tabs Timeline, Blocked, Processes, Receipt, Tighten (the smallest change to its rules) and Unused (rules it was granted and never used).
  • Logs: every line across every run, with search, filters and CSV download.
  • Compare: two runs side by side, for example the same agent watched and enforced.
  • Contracts: a run's rules in plain sentences, and New contract, which writes an agent.yaml from presets or from a finished run.
  • This machine: the protection levels this machine offers.
  • Approvals: requests waiting for your answer.

The product tour walks through the pages.

Answer held requests

The Approvals page in the light theme: 1 approval waiting, a Tego asks you card reading Let release-notes-bot read this file? for ./confidential/plan.md, why it asked, Allow once, Deny and More choices, and below it two earlier requests by supply-chain-claude-code marked Denied. The Approvals page in the dark theme: 1 approval waiting, a Tego asks you card reading Let release-notes-bot read this file? for ./confidential/plan.md, why it asked, Allow once, Deny and More choices, and below it two earlier requests by supply-chain-claude-code marked Denied.
Approvals. A held read waiting for an answer, with the rule that asked and earlier answers below.

When a contract's ask rule holds a file or a connection, the request waits on Approvals and the Overview says something needs you. Each card says what the agent asked for, the rule that asked, and how long the agent waits. Choose:

  • Allow once: this request goes ahead.
  • Deny: this request is refused.
  • Under More choices, Allow for this run or Deny for this run: the answer stands for later requests for the same action and target until the run ends. The contract file does not change.

Nobody answering before the contract's ask.timeout is a refusal. To turn an answer into a rule, open the request's line: after a Deny, Never allow makes the next run refuse it without asking. The dashboard previews the change and applies it from the next run. Write rules shows how to write ask rules.

The same answers from a terminal:

Terminal
tego ask
tego approve <run> <ask_id>
tego deny <run> <ask_id> --always

Stop a run

A live run's page has three buttons:

  • Stop run ends the run, within 10 seconds by default.
  • Pause freezes the agent until you resume it.
  • Block now refuses a program, a destination, or a file or folder from the next action on. The contract file does not change.
The page of a running run, docs-indexer, in the light theme: Running, the buttons Compare, Block now, Pause and Stop run, a green banner reading Protected: 1 secret read blocked, a Highlights card showing ~/.ssh/id_rsa blocked, the tabs Timeline, Blocked, Processes, Receipt, Tighten and Unused, and the newest timeline lines; above it, a banner says release-notes-bot is waiting for you. The page of a running run, docs-indexer, in the dark theme: Running, the buttons Compare, Block now, Pause and Stop run, a green banner reading Protected: 1 secret read blocked, a Highlights card showing ~/.ssh/id_rsa blocked, the tabs Timeline, Blocked, Processes, Receipt, Tighten and Unused, and the newest timeline lines; above it, a banner says release-notes-bot is waiting for you.
A live run. Block now, Pause and Stop run sit beside the run's name.

From a terminal:

Terminal
tego stop <run>
tego pause <run>
tego resume <run>
tego block <run> exec /usr/bin/curl

tego block takes exec, net, path, read or write, then a value, and optionally --for a duration or --until a time.

Open it from a VM or another machine

The dashboard listens on loopback only, so forward the same port over SSH and open the printed link in your local browser. A different local port is refused.

From your machine, then start tego serve in that session:

Terminal
ssh -L 8484:127.0.0.1:8484 <host>

Start tego serve in the Lima VM, then in another terminal on your Mac:

Terminal
ssh -F ~/.lima/tego/ssh.config -N -L 8484:127.0.0.1:8484 lima-tego

Install covers the VM.

Start tego serve inside WSL and open the printed link. A Windows browser may be refused, because WSL forwards the port through a process the dashboard does not trust. Install has more.

If you can't reach it, tego receipt <run> and tego events <run> read the same record in the terminal. Each run page says whether its record checks out; how the record is verified is on the blog.

Runs started with sudo (protection levels 2 and 3) appear once they end; until then, sudo "$(command -v tego)" status shows them. Who can reach the dashboard, and what it trusts, is on Security and limits.

Source: docs/DASHBOARD.md.