feat: add local workflow web console

2026-07-20 02:48:08 +08:00
parent 84f1dc589e
commit c1a982a179
11 changed files with 3071 additions and 3 deletions
@@ -108,10 +108,13 @@ Executor has been running for ~2m. Current activity: Editing src/parser.ts (PID
 - Invite the user once after the Run starts to watch live output independently; do not repeat this command in every progress update:
  ```
  Watch live: agent-workflow logs --run <run-id> --follow
+  Or view Web console: agent-workflow web [--port <port>] (defaults to http://127.0.0.1:4317/)
  ```

 Start that `logs --follow` command at most once for a given Run in the current Codex thread. If it reports that a follower is already active, do not retry the same command; use `agent-workflow status --run <run-id> --json` for progress instead.

+The `agent-workflow web` command starts a local read-only web server that reads workflow state files without taking follower locks or interrupting the main execution loop. It only binds to the local loopback interface (127.0.0.1) for safety, as logs can contain sensitive code and environment details. The web interface displays status, execution events, cycle summaries, and live log updates. The console displays the CLI's actual stdout/stderr outputs and parsed structured activity; it cannot reconstruct unlogged private model reasoning.
+
 `timeoutSeconds` is a consecutive inactivity timeout. Observable executor output refreshes the deadline, so do not treat total runtime beyond that value as a timeout while activity continues.

 ### `awaiting_scope_resolution`