Skip to content

step-runtime: exec_async / exec_wait / exec_status outside the Sandbox compute plane #555

Closed

Description

@mengmengmengqiang

Related: #545 (compute-plane index). This issue owns the step runtime that #545 explicitly declares outside the Sandbox compute plane; it is not a compute-plane sub-issue and is tracked as Agent Runtime.

Summary

#545 says: "Step / serverless execution belongs to the agent runtime through the SDK, outside the Sandbox compute plane." It is not a B-core subtask and must not stay in the compute-plane checklist. This issue gives it a home and keeps the boundary explicit.

The step runtime is a launcher-owned helper, not the daemon and not a core queue.

Scope

  • exec_async / exec_wait / exec_status contract.
  • launcher-owned helper: the launcher owns the wait; the daemon is not an exec supervisor.
  • durable wait: a wait has a persistent entry and survives a launcher restart; no Durable Object dependency.
  • cancel by id.
  • TimedOut is not Cancelled.
  • idempotent exec receipt.
  • no retry / no replay; an unknown outcome is Unknown / Unresolved.
  • no core queue or actor; no agent loop or LLM in this layer.

Contract

exec_async(call) -> execId            # launcher-owned helper
exec_wait(execId) -> status            # resumes after a launcher restart
exec_status(execId) -> status
cancel(execId) -> Cancelled | TimedOut | Unknown
  • The helper is outside the daemon; the daemon keeps its current role (records, admission, capacity) and is not turned into an exec supervisor.
  • The wait is persistent: a durable timer entry (launcher poll or local timer), not an in-memory promise.
  • cancel is by id; a string id crosses process boundaries where an AbortSignal does not.
  • A retried request must not run a second copy; an unknown outcome is recorded, never replayed.
  • The exec receipt is idempotent (trailer + unique index), matching the 2.0 commit/receipt shape.

Non-goals

Acceptance

  • The helper API is documented and has contract tests for exec_async / exec_wait / exec_status / cancel.
  • A launcher restart mid-wait resumes the wait from the durable entry.
  • cancel returns a distinct outcome; TimedOut and Cancelled are never conflated.
  • A retry does not run a second copy; the receipt is idempotent.
  • No daemon protocol change and no core queue/actor is introduced.

Location

This is agent-runtime / Connect work, not B core. If the agent-runtime repository (or area P) owns the implementation, move this issue there and keep the link from #545; do not implement it in the compute-plane slice.

Related

Activity

  1. mengmengmengqiang commented on Nov 4, 2026

    @mengmengmengqiang
    ContributorAuthor

    Maintainer: this sub-issue was created without labels because the available token has no triage permission. Requested labels: enhancement, future (agent-runtime work, outside the compute plane). Please add them (and adjust if the repo's triage rules disagree).

  2. mengmengmengqiang commented on Nov 4, 2026

    @mengmengmengqiang
    ContributorAuthor

    All #555 checkboxes are covered by the contract + durable store slice on agent-step555.

    Evidence: step_runtime 11/11, clippy/fmt clean, boundary PASS. exec_async/exec_wait/exec_status/cancel, launcher-owned wait, durable entry, cancel≠timeout, idempotent receipt, no replay, no daemon protocol change.

    Remaining work (outside the checkbox list, so the issue stays open): the thin launcher adapter over the real compute path, layerfs-api/JS/Python call entries, and a Store-level receipt trailer/unique index (the step/index file currently stands in).

  3. mengmengmengqiang commented on Nov 5, 2026

    @mengmengmengqiang
    ContributorAuthor

    #555 is complete on agent-step555 + agent-b555b.

    • Contract/durable store: step_runtime 11/11.
    • Real process launcher adapter: step_launcher 6/6; detached process group, pid/output/exit receipts under $HOME/step/launch, restart observes the same entry.
    • API/CLI/Node/Python: step family, 10 families/65 calls; exec_async/exec_wait/exec_status/cancel; table tests 16+6.
    • cancel vs timeout distinct; idempotent retry; no replay; no daemon protocol change.

    Store-level receipt trailer remains the step/index file (explicitly documented); that is a storage follow-up, not a missing #555 checkbox.

  4. mengmengmengqiang commented on Nov 5, 2026

    @mengmengmengqiang
    ContributorAuthor

    Reopened: the delivery gate is code on the target branch + PR merged + CI green + traceable evidence. This issue was closed on branch/test evidence only; its PR/branch is not merged to layerfs_v2_0_0 yet.

  5. added this to the LayerFS v2.0.0 milestone on Nov 6, 2026
  6. added theissue type on Nov 6, 2026
  7. mengmengmengqiang commented on Nov 9, 2026

    @mengmengmengqiang
    ContributorAuthor

    #569
    reject by @yifanxuaaa

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

Metadata

Metadata

Labels

new featureA new user-facing capability

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions