@flower-f/afk-web

Local AFK web UI server, API, and browser client for afk-dev.

Most users should start it through @flower-f/afk-cli:

afk web

Features

• dashboard with doctor readiness, workspace config, live jobs, and recent sessions
• run composer with workflow preset selection and advanced runtime/pipeline overrides
• live SSE progress for run stages, checks, tool calls, artifacts, and failures
• persisted run history, event search/filtering, artifact preview, and copyable tool output
• session continuation, run comparison, and pending turn accept/revert actions

Usage

Start the local Web console from a project workspace:

afk
# or
afk web --open

afk web accepts the same workspace/runtime selection inputs as other commands:

afk web \
  --workspace . \
  --runtime codex \
  --model openai/gpt-5.5 \
  --port 4321 \
  --open

By default it binds to 127.0.0.1:4321 and protects the UI/API with a random auth token in the printed URL. The Web server is local-only; stop it with Ctrl-C.

Tests

pnpm --filter @flower-f/afk-web typecheck
pnpm --filter @flower-f/afk-web test
pnpm --filter @flower-f/afk-web test:e2e

test:e2e builds the package, starts the local Web fixture, and runs Playwright coverage for dashboard, run stream, sessions, artifacts, empty states, error states, and responsive layout. If Chromium is missing, run:

pnpm --filter @flower-f/afk-web exec playwright install chromium

To reuse an existing browser binary, set AFK_WEB_E2E_CHROMIUM=/path/to/chromium.

Repository ownership

The source of record is src/, test/, package metadata, and Vite/Playwright configuration. Generated output is intentionally ignored:

• dist/
• client-dist/
• test-results/
• node_modules/

Build the package before local CLI smoke runs that serve the static client:

pnpm --filter @flower-f/afk-web build