--- title: "Dashboard" description: "Tour the local agent-qa dashboard: the Runs, Tests, Hooks, Suites, Memory, Insights, and Config routes, plus live run views and the queue-aware execution workflow." canonical_url: "https://vostride.com/docs/agent-qa/dashboard" md_url: "https://vostride.com/docs/agent-qa/dashboard.md" last_updated: "2026-08-17T02:33:16+05:30" --- # Dashboard > Tour the local agent-qa dashboard: the Runs, Tests, Hooks, Suites, Memory, Insights, and Config routes, plus live run views and the queue-aware execution workflow. The dashboard is the local web UI for inspecting agent-qa runs, editing test assets, reviewing memory, and managing the workspace surfaces that back CLI execution. Launch it with: ```bash agent-qa dashboard --port 3470 --open ``` The dashboard command also supports `--db ` for the dashboard database and `--open` to open the browser after startup. The `serve` command starts the same dashboard-backed local services from configuration. ## Navigation The current dashboard sidebar exposes these labels: Runs, Tests, Hooks, Suites, Memory, Insights, and Config. ![agent-qa dashboard sidebar showing Runs, Tests, Hooks, Suites, Memory, Insights, and Config](/docs/dashboard/dashboard-runs-sidebar.png) ## Runs Runs open at `/runs`. A run detail page uses `/runs/:id`, and live in-progress execution uses `/runs/:id/live`. The route helper sends active runs to live view when the status should be watched in real time. Use Runs when you need to inspect recent execution, jump into a specific run, or follow a live run while an agent is acting. ![Runs table with search, filters, queue slots, statuses, targets, attributes, duration, and start time](/docs/dashboard/dashboard-runs-table.png) Run details keep the step timeline next to the captured browser state, tabs for Overview, Variables, Network, Console, ARIA Tree, and A11y, and per-action timing and model usage metadata. ![Run detail view showing setup hooks, passed steps, browser screenshot, and action breakdown panels](/docs/dashboard/dashboard-run-detail.png) Live execution uses the same split-view model while the run is active. The progress bar, cancel control, elapsed timer, current step selection, and verifier/action feedback update as the agent works. ![Live execution view showing active run progress, step timeline, and action feedback panels](/docs/dashboard/dashboard-live-execution.png) ## Tests Tests open at `/tests`. New tests use `/tests/new`. Existing tests can be viewed at `/test/:testId`, edited at `/test/:testId/edit`, and opened in live editing mode with `/test/:testId/edit?live=1`. Use Tests when you are authoring YAML journeys, reviewing generated test ids, or switching between view and edit modes for a test. The test builder includes Builder, YAML, and Memory tabs. From the builder you can edit the test name, target, context, setup or teardown hooks, and ordered steps, then validate, save, run, or connect a live session. ![Test builder showing target selection, setup hooks, ordered steps, validate, save, run, and live session controls](/docs/dashboard/dashboard-test-builder.png) ### Live Mode Live Mode connects the editor to a real browser session. The left side stays focused on test structure and step status, while the right side shows the browser surface plus inspection tabs such as Reasoning, Env, Network, Console, and ARIA Tree. ![Live test editor showing a connected browser session, step status, and the network inspection panel](/docs/dashboard/dashboard-live-test-editor.png) ## Hooks Hooks open at `/hooks`. New hooks use `/hooks/new`. Existing hooks can be viewed at `/hook/:hookId` and edited at `/hook/:hookId/edit`. Use Hooks to review setup and teardown automation that agent-qa can call before or after a run. Hook references also appear inside test and suite builders. Setup and teardown hook cards show the stable hook id that is saved back to YAML, so a dashboard edit remains reviewable in source control. ## Suites Suites open at `/suites`. New suites use `/suites/new`. Existing suites can be viewed at `/suite/:suiteId` and edited at `/suite/:suiteId/edit`. Use Suites to collect related tests into repeatable workflows and review suite-level setup, teardown, targets, and test references. ![Suite builder showing target selection, setup and teardown hooks, included tests, run suite, and live session controls](/docs/dashboard/dashboard-suite-builder.png) ## Memory Memory opens at `/memory`. Product-specific memory opens at `/memory/:product`. Test-level memory observation panels show observations, invalid memory files, refresh, delete, and empty states such as "No observations yet." Use Memory to inspect what the agent has learned about products, suites, and tests before trusting future runs that use runtime memory injection. ![Memory detail page showing product observations, suite and test sections, filters, and copy page control](/docs/dashboard/dashboard-memory-detail.png) ## Insights Insights opens at `/insights`. The dashboard also redirects older `/analytics` and `/trends` routes into Insights. Use Insights to review chart-oriented views that summarize run and quality signals. ![Insights dashboard showing pass rate, duration, token usage, memory curator, and observation charts](/docs/dashboard/dashboard-insights.png) ## Config Config opens at `/config`. Item-focused config links use `/config?bucket=...&item=...`. The dashboard configuration section includes Dashboard settings for Port, Database Path, Artifacts Directory, and Save Changes. Use Config to inspect and edit workspace-backed settings for dashboard services and other agent-qa configuration buckets. ![Configuration page showing execution defaults, default LLM selection, parallel execution, and save runtime defaults](/docs/dashboard/dashboard-config-execution-defaults.png) ## Queue and run management Queue management is source-backed through the CLI rather than a separate sidebar view. Use `agent-qa queue list --server http://localhost:3470` to inspect pending, running, and optionally completed jobs, and `agent-qa queue cancel --server http://localhost:3470` to cancel a pending or running job. Use this with Runs and live run routes when you need to decide whether to watch, inspect, or cancel work that is already in progress.