Skip to content

Support Paseo 0.15.3 and require Paseo 0.15.0 - #93

Merged
supermomonga merged 2 commits into
mainfrom
humane-lamprey
Nov 9, 2026
Merged

supermomonga merged 2 commits into
mainfrom
humane-lamprey

Conversation

@supermomonga

@supermomonga supermomonga commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

Closes #89
Closes #88
Closes #87
Closes #85
Closes #82
Closes #81
Closes #80
Closes #79
Closes #78
Closes #77
Closes #76
Closes #75
Closes #69

Problem

  • Paseo 0.13.0-beta.1 through 0.15.3 (13 issues) were unreviewed. The development SDKs and CI's upstream checkout were still at 0.12.0.
  • Idle cleanup stops ZCode's background work. Since 0.14.0 (Release idle agent runtimes with work guards and live host controls getpaseo/paseo#7782, on by default as Release idle agents), Paseo closes a session after an idle hour unless the provider vetoes it. The plugin shows ZCode's background Bash and subagents as tool calls, so Paseo's own checks cannot see them. Closing a session stops its Server, so, for example, a dev server started with run_in_background was killed after an hour without Paseo-visible activity.
  • test:upstream no longer ran: Paseo 0.15 compiles and prepares plugins in a worker that a bundled compiler.ts cannot locate, and the adapter now bundles CommonJS which.
  • The plugin still carried fallbacks for Paseo 0.8–0.10 and imported copyText from @getpaseo/plugin/client/react-native, deprecated in 0.13.

Changes

Idle runtime veto (ADR 25)

  • The connection and session.opened advertise session.can_stop_runtime. The answer is a session.can_stop_runtime event, never request.completed; an unknown session gets request.failed, which also keeps the runtime.
  • canStop is true only when, in ZCode's V4 state, there is no Paseo run, no pending admission, an idle conversation, no pending interactions or commands, no running background work, no running subagents, and no active or verifying goal.
  • resultPending is not counted. On 3c5b227, product-projection.ts (onBackgroundTaskLifecycle) never removes the entry, and on the managed runtime it stayed resultPending after the turn that delivered the result. Counting it would keep any session that once used a background command forever. This matches ZCode's own hasBackgroundWork (running only).
  • Reopening after cleanup, and 0.15's opt-in Resume agents after restart (Resume interrupted agents after host restart getpaseo/paseo#8127, #8619), go through session.open with Paseo's saved mode and settings, so ADR 14's guarantee is unchanged.

Minimum Paseo 0.15.0

  • requirements.paseo is >=0.15.0. The SDKs are pinned to 0.15.3, and CI checks out v0.15.3 (d91ae13). The Paseo release monitor reads the SDK version, so it now starts from 0.15.3.
  • The usage source is registered unconditionally. The Account tab uses openExternalUrl, getPaseoClient and copyText from @getpaseo/plugin/client/ui directly.
  • Version qualifiers ("Paseo 0.11 and later" and similar) are removed from the README and the rate-limit message.
  • ADR 25 amends ADR 17 (0.8 fallbacks), ADR 18 (conditional registration) and ADR 24 (minimum).

Checks

  • test:upstream loads the worker's own modules (compiler-build.ts, preparation-build.ts) and compiles with compileDirectoryPlugin, as the daemon does. It also checks that:
    • Paseo's requirement check rejects 0.14.0;
    • the client bundle does not import client/react-native;
    • the real adapter's canStopRuntime() follows a running background work.
  • test:stdio-runtime adds two real-runtime checks:
    • a run_in_background sleep 3 keeps the runtime and releases it after the turn that delivers its result;
    • after the Server is SIGKILLed mid-turn, reopening with the saved settings and sending Resume working. completes.

Reviewed, no change

  • Plugin agent tools (Let plugins give specific agents tools getpaseo/paseo#7938) are registered as Paseo MCP tools.
  • Turn-ended hook timelines (#7477) and worktree hooks (#8117, #8081): the plugin uses no hooks.
  • Rewind fixes (#8368): the plugin does not advertise rewind.
  • Usage fetched only while displayed and the Check usage switch (#8181): the usage source contract is unchanged.
  • Translations, file panels and SVG icons are not adopted.
  • Still true on 0.15.3: plugin provider sessions have no usageSession(), so a ZCode agent's popover shows no usage. Events before session.ready are not re-sent to subscribers.

Verification (Linux x64, Node.js 26.8.1)

  • Local checks. typecheck, npm test (24 files, 234 tests), build, format:check, check:zcode-source (124 files) and check:zcode-patches pass.
    • The new provider test fails when the veto is weakened to foreground idleness only.
  • test:upstream against Paseo v0.15.3. Every check passed, including paseoRequirement and idleRuntimeVeto, for both Git preparations (NODE_ENV unset and production) and the npm installation.
  • Managed runtime 3.16.2-paseo.1 (installed into a temporary XDG_DATA_HOME). test:stdio-runtime passed every check, including the two new ones.
  • CI. Run 42562005991 passed the managed-runtime contract, including both new checks, on darwin-arm64, linux-x64, linux-arm64, win32-x64 and win32-arm64, as well as the real-model E2E.
  • Real daemon. @getpaseo/cli@0.15.3 ran from a temporary prefix with a temporary home, loopback only and relay and MCP disabled.
    • A prepared copy of this tree installed and ran; ZCode is available, and the diagnostic shows Server 3.16.2 / Agent 0.17.0.
    • In headless Chrome, the plugin's Runtime, Account and Timeline tabs render.
    • HOME was not isolated, so the model list and the Account tab read this machine's existing ZCode data. No conversation was created.

Not verified

  • Idle cleanup and restart recovery on a real daemon (needs an hour of idleness and a ZCode session).
  • Whether a finished but undelivered background result is lost when a runtime is released (the V4 state cannot distinguish it).
  • The Account tab's Copy button during a sign-in.
  • A real Paseo 0.15.0 daemon.
  • Users on Paseo 0.9–0.14 can no longer install this version.

Paseo 0.14 releases a session after an idle hour unless the provider
vetoes it. The plugin shows ZCode's background Bash and subagents as tool
calls, so Paseo's own checks cannot see them, and closing a session stops
its Server. Advertise session.can_stop_runtime and keep the runtime while
ZCode's V4 state has foreground work, input, interactions, commands,
running background work or subagents, or an active or verifying goal.
resultPending is not counted: ZCode keeps it after delivering the result.

- Pin the development SDKs to 0.15.3 and CI's upstream checkout to v0.15.3.
- Raise requirements.paseo to >=0.15.0 and drop the fallbacks for older
  daemons; read copyText from @getpaseo/plugin/client/ui.
- test:upstream loads the compiler worker's own modules, checks the
  daemon's requirement check and the veto through the real adapter.
- test:stdio-runtime checks the veto with a background Bash and resuming
  a conversation interrupted by a Server SIGKILL.
@supermomonga
supermomonga merged commit cea90ff into main Nov 9, 2026
14 checks passed
@supermomonga
supermomonga deleted the humane-lamprey branch November 9, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant