> ## Documentation Index
> Fetch the complete documentation index at: https://docs.termyte.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Inspect activity

> Use the local Viewer to see what Termyte captured and processed.

# Inspect Termyte

```bash theme={null}
termyte viewer
```

The Viewer opens at `http://127.0.0.1:7331/` by default. Use `--no-open` if you do not want Termyte to open a browser.

```bash theme={null}
termyte viewer --no-open
```

The Viewer shows:

* sessions and captured events;
* task episodes, evidence, and outcomes;
* memories and where they came from;
* context packets and the items selected for them;
* explicit feedback and measured context effects;
* queue failures, dead jobs, and audit records.

## What the records mean

* A **session** is one agent run.
* An **episode** is one piece of work inside a session.
* An **outcome** records whether an episode succeeded, failed, was partial, was abandoned, or is still unknown.
* A **context packet** is the set of current state and older material Termyte considered for delivery.
* A **context effect** records whether the delivered context appears to have helped, hurt, or had an unknown effect under Termyte's conservative rules.

Open an episode to inspect its traces, evidence, outcomes, context packets, and effects. The Viewer API accepts outcomes at `POST /api/episodes/:id/outcomes` with one of these status values: `succeeded`, `failed`, `partial`, `abandoned`, or `unknown`.

Work Thread task records are available through read-only Viewer endpoints at `/api/tasks` and `/api/tasks/:id`. The current interface does not include screens for creating or editing tasks; use the CLI or MCP tools for that. Recording an episode outcome does not change the task plan.

<Warning>
  The Viewer contains prompts, commands, file paths, and derived records from local work. It binds to the local machine by default. Do not expose it to an untrusted network.
</Warning>