feat(orchestration): executor exposure + Node parallel/resumable (Workflow Phase 5a)#55
Merged
Merged
Conversation
… 5a) The SDK linchpin + the first SDK grammar. core: AgentSession::agent_executor() returns an AgentExecutor backed by the session (its registry, LLM client, workspace, MCP tools, subagent tracker, parallelism cap) — what the orchestration combinators run against; a host can substitute its own for cross-node placement. AgentSession::session_store() exposes the configured store for the resumable combinator. sdk/node: AgentStepSpecObject / StepOutcomeObject (#[napi(object)], with Option<Value> for output_schema/structured) + From conversions, and Session.parallel(specs) / Session.parallelResumable(specs, workflowId) async methods over the executor. parallelResumable rejects when no sessionStore is configured. Pipeline (callback stages across FFI) and the Python SDK land in follow-up sub-PRs. Conversion unit test green; Node SDK fmt + clippy clean; core + combinators unchanged.
This was referenced May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First slice of Phase 5 (SDK ergonomics). The SDK linchpin + the first grammar exposed to Node.
What
AgentSession::agent_executor()→ anAgentExecutorbacked by the session (its registry, LLM client, workspace, MCP tools, subagent tracker, parallelism cap). This is what the orchestration combinators run against; a host can substitute its own for cross-node placement.AgentSession::session_store()exposes the store for the resumable combinator.AgentStepSpecObject/StepOutcomeObject(#[napi(object)],Option<Value>foroutput_schema/structured) +Fromconversions;Session.parallel(specs)andSession.parallelResumable(specs, workflowId)async methods.parallelResumablerejects when nosessionStoreis configured.Scope
This is the spec-list grammar (data in/out — no cross-FFI closures). Callback-based
pipelinestages and the Python SDK land in follow-up sub-PRs (per the agreed "full grammar, both SDKs" plan, built incrementally). The callbackpipelineis the part that must carefully honor #32's no-throw/no-panic FFI constraints, so it gets its own focused PR.Verification
cargo fmt --check+cargo clippy --lib -D warningsclean; core + combinators unchanged (their suites already green on main).