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
@@ -172,6 +172,19 @@ agent-workflow logs --run <run-id> --follow
 agent-workflow logs --run <run-id> --tail 200
 ```

+### `agent-workflow web`
+
+Start a local read-only web server to monitor agent executions, runs, cycles, and logs in real-time.
+
+```bash
+agent-workflow web [--port <n>]
+```
+
+- **`--port <n>`** — specify a custom port to listen on (default: `4317`).
+- **Security & Scope** — The server binds exclusively to the loopback interface (`127.0.0.1`) for local-only access. It refuses any external or remote listener configurations. Since executor logs can contain sensitive code, configuration details, or tokens/credentials, binding to `127.0.0.1` ensures that the console remains local.
+- **Observability Boundaries & Limits** — The console is completely read-only and provides no endpoints to modify or control workflows. It directly parses and displays the execution progress, cycles, timeline, and stdout/stderr output. It cannot recover or display private reasoning tokens/processes of underlying models that are not output to the console.
+- **Interaction with `logs --follow`** — The web server directly reads the persisted run files without taking any logs follow locks or interfering with the main executor loop, allowing you to use both the CLI `logs --follow` and the web console concurrently.
+
 ### `agent-workflow abort`

 Terminate an active workflow.