Skip to content
Core ConceptsCLI ReferenceAPI Reference
Getting Started
AGH RuntimeGetting Started

Web UI

Open the AGH web UI, inspect the session you already created, and compare the browser view with the same daemon state you saw in the CLI.

Audience
Operators running durable agent work
Focus
Getting Started guidance shaped for scanability, day-two clarity, and operator context.

The web UI is another surface on the same daemon you already used in Quick Start. The goal of this page is not to start a second workflow; it is to inspect the exact same runtime state in a browser.

Before you begin: Complete Quick Start so you already have a real session to inspect.

1. Open the runtime in your browser

By default, AGH serves the UI from the same HTTP address used by the daemon API:

http://localhost:2123

If you changed [http].host or [http].port in ~/.agh/config.toml, use that address instead.

2. Find the session you created in Quick Start

Open the session you already created from the CLI. The browser should show the same durable session state, not a second copy of the work.

The exact UI layout will evolve, but the important point is stable: the browser is reading the same daemon-owned session catalog, event store, and redacted Vault metadata as the CLI.

3. Compare browser state with CLI state

Keep these commands handy while the UI is open:

agh session list
agh session status sess_1234
agh session events sess_1234 --follow

Use them to confirm that the CLI and browser are reflecting the same runtime facts:

  • session identity
  • session state
  • live event activity
  • resume/stop behavior
  • session-scoped Vault metadata when entries exist below vault:sessions/<session_id>/

4. Watch live events

Send one more prompt from the CLI:

agh session prompt sess_1234 "Tell me the last thing you learned about this repository."

Then watch the session in the browser update from the same persisted event stream. This is the fastest way to understand how AGH keeps CLI, API, and UI surfaces aligned.

5. Use the browser as an operator surface

The web UI is the easiest place to inspect runtime state visually. Depending on the current build, you may see surfaces for sessions, tasks, bridges, network state, skills, and settings. Settings > Vault lists redacted metadata for encrypted AGH-managed secrets and supports write-only updates and deletes. Session pages include a Vault tab in the inspector for entries under vault:sessions/<session_id>/.

Treat the CLI as the canonical fallback for any flow that is not yet exposed in the browser.

6. Change the HTTP address if needed

[http]
host = "localhost"
port = 8080

Restart the daemon after changing the address:

agh daemon stop
agh daemon start

Note: Binding to a non-local host exposes the browser and API surfaces to a wider network. Do that only when you understand the trust boundary of the machine running AGH.

Next Steps

  • Sessions explains the lifecycle the UI is visualizing.
  • Event Streaming explains the persisted and live streams behind the browser view.
  • Vault documents the redacted secret metadata surfaces.
  • CLI Reference gives you the exact commands behind the same control surface.

Your First Custom Agent

Create one minimal AGENT.md definition, store it in the correct runtime path, and verify that AGH resolves it for the current workspace.

Sessions

The durable runtime unit AGH creates, resumes, audits, and governs.

On this page

1. Open the runtime in your browser2. Find the session you created in Quick Start3. Compare browser state with CLI state4. Watch live events5. Use the browser as an operator surface6. Change the HTTP address if neededNext Steps