Skip to content

fix(runtime): withdraw only consumed background command notices - #72

Merged
rynfar merged 2 commits into
pylonfrom
fix/background-notice-consumption
Sep 15, 2026
Merged

rynfar merged 2 commits into
pylonfrom
fix/background-notice-consumption

Conversation

@rynfar

@rynfar rynfar commented Sep 15, 2026 •

Copy link
Copy Markdown

Reading a completed background command could leave a queued completion notice that triggered an extra turn. Adopt upstream consumption tracking and withdraw only the matching undelivered notice.

The review adds a per-handle identity and exact host acknowledgment: PID/command reuse cannot remove another handle's unread notice, duplicate withdrawals do nothing, and older hosts keep their notices. A detached reader must be awaited by the active cell before its read counts as consumption. Delivered notices remain immutable.

Hybridizes upstream PrimeIntellect-ai#2159 (ecd60e3cd4313643dede3cb2fcf13b4e2e9a2a75). Fixes #64. This is an additive acknowledged kernel-bridge feature; daemon protocol and capability contracts are unchanged. Native transcript integration and installed-artifact acceptance remain coordinated with pylon-code/pylon#552 and PrimeIntellect-ai#557.

Validation: 109 Python REPL tests and 14 TypeScript/kernel tests passed, including exact-handle withdrawal, detached readers, old-host fallback, Stop/admission and residency. npm run check passed. The maintainer authorized reviewed merges after green checks in the active Pylon conversation. Implemented and reviewed with Codex.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(coding-agent): adopt upstream background-command notice deduplication

1 participant