Skip to content

demo-guide.md

Latest commit

 

History

History
80 lines (59 loc) · 2.72 KB

demo-guide.md

File metadata and controls

80 lines (59 loc) · 2.72 KB
Raw

FlowLens AgentOps Demo Guide

Replay Mode

Replay is the recommended first review because it needs no account, backend, model, or API key.

cd frontend
corepack enable
pnpm install --frozen-lockfile
pnpm agentops:demo:dev

Open http://localhost:5173. The static production build is also published by the Pages workflow at https://try1004.github.io/FlowLens-AgentOps/ after the maintainer enables and runs the repository workflow.

Suggested walkthrough

  1. Select Tool Error and compare Metrics with the tool.error Timeline event.
  2. Click the Root Cause evidence item to open event metadata and span links.
  3. Filter Timeline to Tool, MCP, Memory, or Subagent phases.
  4. Switch to MCP Auth Error and verify that authentication is primary rather than the terminal run error.
  5. Switch to Checkpoint Rollback and explain why Timeline survives state rollback.
  6. Use Explain to show the deterministic prewritten Replay explanation.
  7. Use Export to download the redacted diagnostics contract.
  8. Resize to mobile: open Runs as a drawer and switch Timeline/Root Cause tabs.

The seven scenarios are Success, Tool Error, Subagent Timeout, Guardrail Denied, Checkpoint Rollback, MCP Auth Error, and Memory Error. Every fixture is synthetic.

Docker Replay

make flowlens-demo
# open http://localhost:4173
make flowlens-stop

Set FLOWLENS_DEMO_PORT to override port 4173.

Remote (Connected) Mode

Connected mode requires a configured DeerFlow installation:

make setup
make up

Open http://localhost:2026/agentops. The default route selects the Remote data source and displays a Remote status badge. For a local deterministic route inside the Next application, use /agentops?mode=replay&scenario=tool-error.

Keep run_events.backend: db with the SQLite database configuration from config.example.yaml so Timeline events remain available after a Gateway restart. The memory backend is intended only for disposable development runs.

Connected verification should demonstrate:

  1. /health reports healthy;
  2. the authenticated user sees only owned runs;
  3. a real Tool/Subagent/MCP/Memory operation produces correlated Timeline events;
  4. export contains redacted metadata and the same rule result shown in the UI;
  5. a running Run polls, while a terminal Run stops polling.

Do not capture personal prompts, memory content, local paths, browser accounts, tokens, or production run exports in screenshots or issue reports.

Verification Commands

make flowlens-check
make flowlens-benchmark
python scripts/check_flowlens_secrets.py

The Replay Playwright suite covers scenario switching, event details, no page-level horizontal overflow, and 1440x900, 1024x768, and 390x844 viewports.