Skip to content

v0.44.0

Choose a tag to compare

@github-actions github-actions released this 28 Oct 16:24
8bec304

Stageflow release notes

Release v0.44.0 includes changes since v0.42.0 (0.43.0 and 0.44.0).

0.44.0

Artifact verification, sandbox grants for prior stage outputs, and console improvements for runs and transcripts.

Features

  • On-disk stage artifacts before emit. emit_stage_envelope refuses claims that are not regular files under the attempt’s artifacts directory (closed posture: no symlinks). See Envelopes.
  • Prior envelope artifacts as sandbox grants. Consumer stages get read-only mounts at /workspace/grants/<stageId>/… with an explicit listed→container mapping in the stage prompt. Missing prior files are skipped; duplicate basenames are disambiguated.
  • Honest missing artifact claims in the console. Envelope panels show when a claimed path is absent on disk.
  • Artifact path grammar and closed-posture disk inspect share one module each. Emit, verify, and prior grants compose the same layout/inspect rules instead of hand-rolled twins.
  • Run reopen clock and action eligibility are deep pure modules. Store/finished_at, retention, retry, cancel, abandon, and the Gantt now-marker go through them; UI retry matches runtime (including succeeded stages that are not clone/fork blocked).
  • Guide cards and mutations deepen. cardContract owns wire validate/build for producer and console; GuideToolkit(deps) owns confirm + place over buildToolkit.
  • Grant mounts copy files as files. Host file artifacts bind with shape: "file" at /workspace/grants/<stage>/<filename> instead of creating a directory named after the file.
  • Stage retry reopens cancelled runs. Retry is allowed when the run is failed, succeeded, or cancelled; moving back to running clears finished_at so the timeline “now” marker and Cancel stay coherent.
  • HTTP stage retry returns when the attempt starts. The console Abandon/Cancel busy lock is no longer held for the whole stage.
  • Stage transcript tool results. Tool outputs render as structured cards (including GitHub PR-shaped payloads) in a scrollable transcript pane instead of raw escaped JSON.

0.43.0

Automatic context compaction for long Pi sessions, a working_state tool, and tighter stage emit and tool-budget behavior.

Features

  • Long Pi sessions compact themselves, and compaction keeps what matters. Pipeline stages, project agents and the operator agent now compact their context when the window fills. The summary is written by the same model the stage or agent uses; Stageflow appends pinned facts, verbatim operator/user directives, an index of cleared tool results, and working state. Secrets are scrubbed before and after summarization. If custom summarization fails, Pi's default compaction runs. See Context and compaction.
  • working_state tool. Stages, project agents and the operator agent can keep keyed entries (facts, decisions, progress, to-dos, blockers). Entries survive resume and reappear after every compaction, with secret scrubbing on values.
  • Context size and compactions in the console. The stage inspector shows tokens used of the window; the events list shows Context compacted with before/after tokens, summary size and cost. Compaction is charged to stage usage and agent limits.cost_usd.
  • compaction-stress example. A three-stage incident postmortem that reads about 1 MB of logs through a context window that forces compaction, with evidence generator and result checker (check-run.mjs).

Changes

  • A Pi stage's assignment and envelope contract are in the system prompt. The first user message is now a one-line kickoff instead of the full assignment (which compaction could summarize away).
  • read and bash share a per-turn token cap. The first result of a turn always returns; later parallel results in the same turn may be replaced by a short notice once the turn would exceed 40% of the window or the space left after the reserve.
  • Emit reminders reset on progress. Reminders cap at 20; a tool-call turn resets the count. Stages that end by writing a tool call as plain text now fail with a clear provider error instead of missing emit_stage_envelope.
  • OpenRouter requests that carry tools ask for providers that support them (require_parameters), unless routing is set in models.json. See Providers.
  • The Claude backend pins the SDK's auto-compaction on.