Skip to content

Enable sidebar-visible third-party Worker callbacks and binding readback #156

Closed as not planned
2 of 2 issues completed
Closed as not planned

Description

@NOirBRight

Priority and external blocker

Priority: P0 — complete the Host/runtime gate before resuming dependent orchestration work.

This is a hard external blocker for NOirBRight/github-work-orchestrator#16. Keep that Issue stopped and unclaimed until the native sidebar-visible Worker acceptance gate below passes.

Sanitized reproduction

Environment: Codex Desktop 26.707.12708.0, Codex CLI 0.144.5, CodexHub route, Ollama Cloud native Responses, requested glm-5.2 / max.

  1. A native worktree Worker was created from the parent and appeared as a separate sidebar Task.
  2. Parent-to-child continuation worked, and the child had functioning shell/MCP tools.
  3. The child could not access a supported parent-result callback or equivalent result-delivery channel. Exact-name searches returned tools=[].
  4. The child could not prove the effective agent type, model, and reasoning through supported readback.
  5. Without a terminal unsupported result, the failed capability search could repeat. A bounded parent continuation stopped the read-only incident; the child returned BLOCKED and its worktree stayed clean.

Private rollout, Task, callback, local-path, call, and token identifiers remain excluded. Do not edit Codex SQLite or infer evidence from private IDs.

Problem

The Codex Host/runtime does not yet provide a complete supported contract for third-party delegated implementation as a native sidebar-visible Worker Task. The required contract spans Worker materialization, bidirectional parent/Worker communication, result delivery with a confirmable receipt, effective binding readback, explicit unsupported terminalization, and a visible Active → Done lifecycle.

A model-visible callback schema is not sufficient when the child has no registered native handler. Requested settings are not effective binding evidence.

Desired outcome

Native Host/runtime delegation can create a sidebar-visible third-party Worker and prove, before implementation begins, that the supported execution surface and effective binding match the request. The parent and Worker can communicate in both directions, the parent receives a confirmable result receipt, unsupported capabilities stop terminally, and the Worker becomes visibly Active and then Done.

Scope — Host/runtime only

  • Materialize delegated implementation as a separate native sidebar-visible Worker Task with supported discovery/readback.
  • Register a supported parent-result callback in the Worker context, or provide an equivalent durable result-delivery channel whose receipt the parent can confirm.
  • Support parent-to-Worker continuation and Worker-to-parent result return in the same isolated lifecycle.
  • Expose supported effective readback for agent type, model, and reasoning effort before edits begin.
  • Return an explicit, machine-classifiable terminal unsupported result when the requested Worker surface, callback/result channel, or binding cannot be provided.
  • Expose supported lifecycle readback showing the Worker transition from Active to Done.
  • Preserve sanitized Host/runtime evidence for a bounded manual replay.

Non-goals

  • Do not implement CodexHub's repeated identical empty-tool_search bound; Bound repeated empty tool_search misses for external models #159 owns that work.
  • Do not implement CodexHub Worker selector/codec preservation or effective-binding validation; Preserve Worker selector and effective binding validation for external delegation #161 owns that work.
  • Do not inject a callback schema without a registered Host/runtime handler.
  • Do not substitute GPT, Hidden Subagent, Inline execution, Background process, codex exec, or a shell-launched model for the sidebar-visible Worker.
  • Do not edit Codex SQLite, publish private IDs or local paths, synthesize rollout state, or infer binding from requested settings.
  • Do not broaden into unrelated transport, routing, retry, apply-patch, or Task-activity rendering work.

Acceptance criteria

  • A native delegation materializes one separate sidebar-visible third-party Worker Task.
  • Supported readback proves the effective Worker agent type, requested third-party model, and requested reasoning effort before implementation begins.
  • Missing, unknown, contradictory, rejected, unsupported, or GPT-substituted binding evidence stops terminally before edits.
  • Parent-to-Worker continuation and Worker-to-parent result delivery both succeed in the same isolated Worker lifecycle.
  • The parent receives a supported confirmable receipt for the Worker's final result.
  • An unavailable Worker surface, callback/result channel, or selector returns an explicit terminal unsupported result rather than continuing or substituting another surface.
  • Supported Task APIs show the separate Worker as Active and then Done.
  • The real validation performs only a disposable read-only action until surface, binding, and callback/receipt preflight pass.
  • No GPT, Hidden Subagent, Inline, Background, codex exec, or shell-launched substitute appears in the evidence.

Host/runtime verification and evidence

This Issue does not authorize or invent CodexHub product-code verification. Its acceptance is manual Host/runtime evidence from one isolated native Codex Desktop replay using a third-party model and requested reasoning:

  1. create one native sidebar-visible Worker Task;
  2. read back effective Worker agent type, model, and reasoning through supported APIs;
  3. send one parent continuation;
  4. return one Worker result and confirm the parent receipt;
  5. read back Active → Done terminal visibility;
  6. capture only sanitized outcome fields and failure classifications.

Relationships

Expected hotset

Host/runtime-owned, outside this repository:

  • native sidebar-visible Worker Task creation/materialization;
  • child Host tool registration or equivalent result-delivery channel and receipt;
  • supported effective agent/model/reasoning readback;
  • supported Worker lifecycle state and explicit unsupported terminalization.

No CodexHub product-code hotset is owned by this Issue.

Execution contract

Execution-Contract: v2
Verification-Class: strict
Verification-Commands: Host/runtime supported-API readback only; no CodexHub product-code command is claimed
Manual-Evidence: one isolated native third-party sidebar-visible Worker replay proving effective binding, bidirectional communication, confirmed parent receipt, explicit unsupported behavior, and Active → Done visibility
Architecture-Decision: resolved
Review-Owner: orchestrator

Activity

  1. NOirBRight commented on Jul 16, 2026

    @NOirBRight
    OwnerAuthor

    Execution admission decision

    No automated implementation lane is admitted yet.

    • The required final gate needs a native visible/child context and supported effective readback.
    • The known native Worker path is the failing surface: it cannot deliver the required parent callback.
    • The native Subagent surface does not currently expose a supported agent_type=worker selector plus effective agent/model/reasoning readback.
    • Starting another implementation Worker/Subagent would therefore violate this Issue's exact-runtime/fail-closed contract. No GPT fallback or Background/CLI substitute is authorized.

    The Issue remains ready-for-human for the Codex host/runtime change. After the host exposes callback/receipt and selector/readback, route the CodexHub-owned bounded-search and codec work through a single GLM-5.2/max implementation owner, then run the strict native replay before releasing the dependent Orchestrator Issue.

  2. NOirBRight commented on Jul 16, 2026

    @NOirBRight
    OwnerAuthor

    Reporter clarification — sidebar-visible Worker is the required execution surface

    New screenshot-backed evidence clarifies the product outcome and the boundary between the two Codex collaboration surfaces:

    • The user selected a third-party GLM-5.2 model and requested Superpowers Subagent-Driven execution.
    • The attempted spawn_agent call returned unsupported call; no delegated child was created.
    • Subsequent edits ran inline in the parent while still being described as Subagent-Driven.
    • No independent Worker Task appeared in the Codex sidebar.

    Expected behavior is not merely a successful hidden Subagent. Delegated implementation must materialize as a native sidebar-visible Worker Task, with its own discoverable Task/thread lifecycle and effective model/reasoning readback. The parent must be able to send work to it, the Worker must return a result with a confirmable receipt, and the Worker must reach a terminal state visible through the supported Task APIs.

    This evidence is a duplicate of #156's visible-Worker creation/callback outcome and is related to #64's explicit separation of hidden Subagents from sidebar-visible Tasks. It sharpens the acceptance boundary:

    • a hidden entry under a Subagents activity surface does not satisfy the visible-Worker gate;
    • spawn_agent.agent_type=worker, if supported later, cannot substitute for native sidebar Task materialization unless the host proves it creates that same visible Task surface;
    • inline parent execution after a failed delegation must not be reported as Subagent-Driven success;
    • final native evidence must show a separate sidebar Worker Task, supported discovery/readback, bidirectional communication, result receipt, and terminal completion.

    The screenshot itself is not attached to GitHub because it contains incidental local UI context; only the sanitized failure and expected outcome are retained here.

  3. changed the title [-]Restore callback delivery and bound tool discovery for GLM Worker threads[/-] [+]Enable sidebar-visible third-party Worker callbacks and binding readback[/+] on Jul 16, 2026
  4. added
    wontfixWill not be actioned
    and removed on Jul 20, 2026
  5. NOirBRight commented on Jul 20, 2026

    @NOirBRight
    OwnerAuthor

    Explicit maintainer decision: close as wontfix/superseded. Orchestrator V6 now uses Paseo-managed native Workers with exact runtime validation, atomic worktrees, identity readback, and native completion notification; the legacy sidebar-visible callback gate is no longer an admitted CodexHub product requirement. Historical host/runtime evidence remains preserved here.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingwayfinder:grillingWayfinder decision or reconciliation gatewontfixWill not be actioned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions