Repository navigation
v0.35.0
Stageflow v0.35.0
This release ships the operator console as the primary UI, separates credential storage from run data, and tightens how stage skill: bindings are authored.
[0.35.0]
Features
- Operator console. Inbox, pipelines list, pipeline editor (live DAG, inspector, YAML, Problems, session history), catalog, tasks, triggers, Workshop, and run detail (timeline / graph / list). Single dark console UI; no separate theme picker.
- Workspace catalog as default write root. Omitted
project_rootresolves to a Host-provisioned writable workspace under$STAGEFLOW_HOME, so Workshop and catalog saves work without a git checkout or multi-root picker. - Catalog paste-install for skills. Install a skill tree into the workspace
.pi/skillsroot from the Catalog UI (npx skills addwrapper), without requiringproject_rootwhen the Host has multiple roots. - Stage-file editor from Catalog. Edit a single external stage file in the full pipeline editor chrome (graph + inspector + YAML).
- Triggers readiness catalog.
examples/triggers-readiness/ships one trigger per kind (manual, schedule, GitHub pull request, webhook, email, dynamic manual) and is registered in the local Docker image.
Changes
- Breaking: stage
skill:is body-only.skill:on a pipelineuses:wrapper is rejected (pipeline.stage_wrapper_skill_rejected). Putskill:on the external stage file or inline stage body. The console inspector and draft overwrite strip wrapperskill. In-repo examples (archify-on-pr,oss-issue-contribution) were migrated. See Skill binding. - Credential root separate from run data. Stage workers and Workshop resolve provider auth from
STAGEFLOW_CREDENTIAL_HOME(default~/.stageflow); run SQLite stays under$STAGEFLOW_HOME. Cursor models use the credential-root key; other models still require a usableauth.jsonthere and fail closed. - Docker console image. The image does not bake the full
examples/tree. Compose registers/opt/stageflow/catalog/triggers-readinessso the readiness triggers are listed on a local Host.
Fixes
- Workshop saves use
.pipeline.yaml/.task.yaml, re-pin build ties to the catalog save root, and stop claiming paths under a stale image-root examples tree. createStagepersistsskillon the stage file; draft load/overwrite hoists legacy wrapperskillonto the stage body so save cannot drop the binding.- Workshop mutation cards survive a reload because the transcript stores the draft, not only the summary.
- Run detail header and the stage inspector share one rule for showing Retry, Resume, and Abandon.
[0.34.0]
Live browser login from the operator console when the Host has no local window the operator can see.
Features
- Live view for human login gates. When a Host has no window an operator can see, the console shows the stage's browser inside the login gate and forwards mouse, keyboard, paste, and touch input, so a person can log in (password, two-factor, popup sign-ins) from the console. Uses agent-browser's built-in stream relayed by the Host. See
docs/browser.md(Live view) anddocs/browser-internals.md.- Capability-driven gate handoff:
local_windowon a desktop,live_view(stable path, never a credential) on a Host with a virtual display or headless-only with the relay. A Host with no screen and no live view still fails the login stage early. - Console API under
/api/runs/:run/stages/:stage/live-view: single-use, short-lived tickets (vieworcontrol) redeemed into a path-scoped cookie, an event stream, ordered input, and a dialog answer route. Control works only while the stage waits at a live view gate and is revoked when the gate is answered, abandoned, or cancelled. Input and frames are never logged or stored. - Popups and new tabs are followed automatically;
confirmandpromptdialogs can be answered in the viewer;alertandbeforeunloadare handled by agent-browser. Unanswered dialogs are dismissed afterbrowser.dialog_timeout_seconds(default 60). - "Reopen browser tab" fallback in the viewer's "Page seems stuck?" section (
POST .../live-view/reopen-tab, relayreopenTab()): replaces a tab that stopped accepting input with a fresh one at the same URL in the same browser, moves the stage session and stream to it, then closes the old tab. - Virtual display support: a Linux Host without a display but with
Xvfbruns the browser headed. Host config keysbrowser.launch_argsandbrowser.executable_path(never in YAML) for launch options and distribution Chromium on ARM. docker/Dockerfile.browserrecipe extending the runtime image with Chromium, Xvfb, and agent-browser (docs/docker.md).- Provider-neutral ports with in-tree fakes (browser host capabilities, sandbox orchestrator, live view relay, live view source) as seams for container and provider browser hosts.
- Opt-in smokes:
STAGEFLOW_BROWSER_SMOKE=1(real Chrome, console API, popups, dialogs) andSTAGEFLOW_DOCKER_SMOKE=1(browser recipe image).
- Capability-driven gate handoff:
Changes
- Browser permission prompts (camera, microphone, location, notifications, clipboard) are denied by default for every browser session the Host launches (
--deny-permission-prompts). - Browser teardown first closes any live view for the stage or run (bounded wait), then runs the existing tab, session, and anchor order.