Make your computer a home for your AI partner. Avibe is the local-first Agent OS: Vibey, its built-in AI partner, works out of the box, and Claude Code, Codex & OpenCode run unchanged beside it — reach them from your browser, phone, or any chat app.
Harness Callback Ownership and Separation
Background
Issues #918 and #922, fixed by PRs #919 and #923, established two contracts:
- one terminal callback per asynchronous Agent Run; and
- terminal callback text comes from the turn-final assistant result, never an Activity label or tool description.
Two incidents on 2026-07-30 exposed one remaining ownership error. A target turn explicitly queued a separate Agent Run back to its caller while finishing with an intentional silent terminal. The callback drainer treated that queued child as if it were the parent's already-delivered callback.
Live Evidence
The affected runtime roles were a Claude-backed coordinator Session and a Codex-backed implementation-lane Session. The exact local Session, Run, Message, and backend-native identifiers were verified during diagnosis but are intentionally omitted from this public plan.
Incident A
- The parent escalation Run targeted the coordinator, finished
succeededwithresult_text="", and recorded an intentional silent terminal Message. - The intermediate coordinator Message remained correctly stored as
author=agent,type=assistant,source=agent. - The coordinator explicitly queued a full ruling Run to the lane. It had
started_at=NULL, but the parent was markedcallback_status=sentwith that directed Run as itscallback_run_id. - The lane did not receive that intermediate Message through callback
delivery. Its native Codex transcript shows it querying the PM Session at
2026-07-30T02:04:41Z, then querying the exact intermediate Message at02:04:47Z; only afterwards did it report a truncated ruling.
Incident B
- The parent escalation Run was created with
--no-callback, so bothcallback_session_idandcallback_run_idare null. - The intermediate coordinator Message remained in its target Session, followed by an intentional silent terminal Message.
- The full directed ruling Run remained queued with
started_at=NULL. - The lane's native transcript shows direct
vibe data querycalls at2026-07-30T03:49:32Zand03:49:36Zreading the PM Session and the exact intermediate row before it described the ruling as truncated.
The incidents therefore do not prove intermediate callback delivery. They do prove that the callback ledger falsely identifies a separate queued child as a sent callback, which makes later inspection and automation unable to distinguish callback ownership from an independent directed Run.
Root Cause
ScheduledTaskService._enqueue_callback_run() calls
find_explicit_session_delivery() before building the terminal callback. Any
agent-authored child Run with the parent id and callback target Session is
returned as the parent's callback, regardless of whether it has started,
completed, or was intended as a separate message.
The callback drainer then writes that child's id into the parent
callback_run_id and marks the callback sent. This conflates two durable
objects and lets an unstarted queue entry satisfy callback delivery.
Required Behavior
- Only a callback Run created from the parent's turn-final
result_textmay satisfy the parent's callback policy. - A successful empty terminal result produces no visible callback Run. Earlier assistant progress remains in the target Session only.
- An explicitly directed Agent Run remains independent, retaining its own id, source, parent lineage, queue position, callback policy, and exact message.
- A busy callback target may queue the terminal callback, but its body and provenance must still come only from the parent terminal result.
- No Harness-generated content is persisted as human-authored input, and no duplicate callback is created.
Implementation
- Remove explicit child-delivery substitution from the shared callback drainer and its store API.
- Keep the change forward-only. Historical
callback_status=sentrows remain inert and are never reset, replayed, or used to create a new callback Run. - Keep the existing terminal-result selection and exactly-once callback identity from #919 and #923.
- Add consuming SQLite-backed tests through the real message dispatcher and
callback drainer for:
- intermediate preamble, tool boundary, intentional silent terminal;
- intermediate preamble followed by a full terminal result;
- separately directed full message while the callback target is busy; and
- callback idempotency and non-user Harness identity.
- Allocate
MESSAGE-DELIVERY-008as contract-level partial coverage. PR #1104 currently ownsMESSAGE-DELIVERY-007;HFR-430is already allocated on master.
Historical Compatibility
The incidents predate this forward contract, but their stored delivery state is
not replayed. An old parent row already marked callback_status=sent remains
sent across upgrade and startup, even when its callback_run_id names a
directed source_kind=agent child. No migration re-arms it and no startup path
creates a replacement callback from its historical terminal text.
Read-only consumers distinguish the two child types from persisted
source_kind: callback identifies an automatic callback Run, while agent
retains directed-Run provenance and graph lineage. This classification never
mutates historical rows and never causes delivery.
Scope
This change does not alter queue supersede, cancellation recovery, #1098, #1072, authentication, authorization, ACL behavior, #1074, or the Markdown silent-literal parser owned by PR #1104.