Vibe coded UI CI runner for your agent ActUI, a local GitHub Actions workbench for humans and coding agents, has been released, providing a browser dashboard that discovers workflows, delegates execution to nektos/act, and presents jobs, logs, and approvals in one view. The tool requires Node.js 22+, Docker Engine or Docker Desktop, and Act on PATH, and includes a JSON CLI and local MCP server for agent integration. ActUI's explicit --trust flag is required to execute workflow code, and it supports custom job lists, bookmarkable views, and process-level log isolation. ActUI is a local GitHub Actions workbench for humans and coding agents. It discovers workflows in a repository, delegates their execution to nektos/act https://github.com/nektos/act , and presents jobs, dependency state, logs, agent notes, approvals, and cancellation in one browser dashboard. The dashboard, JSON CLI, and local MCP server use one shared run manager. A human and an agent can therefore watch and operate the same run instead of creating disconnected CI processes. Prerequisites: Node.js 22+, Docker Engine or Docker Desktop, and Act https://nektosact.com/installation/index.html on PATH . npm install npm run build npm link actui /path/to/repository --trust ActUI binds to 127.0.0.1 , chooses an available port, and opens the dashboard. The explicit --trust flag is required to execute workflow code; without it, the session is read-only. If Act is missing when a run is requested, ActUI detects the host operating system and shows a copyable installation command in both the terminal and dashboard. After installing, verify with act --version and restart ActUI. If the executable is installed outside PATH , use --act-path /absolute/path/to/act . See the official Act installation guide https://nektosact.com/installation/index.html for package-manager alternatives and prerequisites. Workflow cards group each job with its ordered steps. Select individual jobs, name the selection, and save it as a custom job list. Lists and the last active list are stored locally under the repository’s absolute path, so opening another repository loads its own presets automatically. Targeted runs pass the selected job IDs to Act; required job dependencies are retained in the shared run view. The run console can expand to the entire viewport and closes with its button or Escape . The dashboard has separate Workflows, Run history, and Environment views. Their URL hashes are bookmarkable. Press Command-K on macOS or Control-K elsewhere—or select the repository switcher—to open the command palette and move between views without leaving the current session. Inside a run console, jobs are accessible tabs. Selecting a job opens one panel containing that job’s ordered step states and its filtered live logs, keeping job, steps, and output together. Process-level Act messages are isolated in a separate Run output tab instead of being repeated in every job. ActUI parses both JSON and logfmt Act records to preserve job attribution. Each Act workflow process uses an operating-system-assigned artifact-server port, avoiding collisions when several workflows run together. Before execution, ActUI checks selected jobs for runner labels Act does not provide by default. Custom Ubuntu labels such as ubuntu-latest-low produce a visible mapping prompt and can be mapped in one click to catthehacker/ubuntu:act-latest . Multiple mappings are passed as repeated --platform arguments. ActUI blocks the run until every detected custom label is mapped, preventing silently skipped jobs. Useful launch options: actui . --no-open actui . --port 4040 --trust actui . --act-path /custom/path/to/act --trust actui discover . --json actui run --workflow ci.yml --event pull request --json actui wait