Repository navigation
[feat] Add a Paseo driver adapter #1087
Description
Parent: #818
Goal
Validate the experimental pull-based contract with a second runtime without leaking Paseo concepts into TeamAI’s workflow model.
Scope
- Implement a Paseo adapter that starts or attaches to a run and loops over public
next/report. - Map leases to Paseo tasks, sessions, and workspaces.
- Run
teamai initandteamai pullin the adapter environment before requesting work. - Declare actual capabilities, channels, machine identity, and workspace identity.
- Map completion, failure, timeout, cancellation, and usage exhaustion to TeamAI outcomes.
- Return
releasedand stop polling when usage limits prevent progress. - Return pushed branch and optional PR metadata.
- Support eligible gate-response channels.
- Reuse the shared conformance scenarios added in [feat] Run prompt and agent steps with the local driver #1077 through direct engine and CLI JSON paths.
- Keep Paseo installation and version guidance separate from portable workflow syntax.
Out of scope
Paseo-specific workflow fields, pushed stdio execution, remote secret transport design, concurrent multi-machine leases, triggers, event waits, and OpenTelemetry.
Dependencies
- Blocked by: [feat] Deliver workflow branches as pull requests #1090, [feat] Add manual run controls and human gates #1081, [feat] Enforce workflow requirements and execution limits #1082, [feat] Add the session skill driver and invocable workflows #1086, [feat] Close the #1080 gaps that #1175 leaves open #1246
- Unblocks: none
Acceptance criteria
- A local-driver workflow runs unchanged through Paseo.
- The adapter receives leases, gates, acknowledgements, and outcomes—not the graph.
- TeamAI schemas contain no Paseo fields.
- Released or retried attempts cannot later report successfully.
- Paseo may return its own valid PR URL.
- Conformance failures identify CLI/direct-operation drift.
Verification
Focused adapter and reused conformance tests with a fake Paseo boundary; build/typecheck/lint; one real Paseo run when available, otherwise one real-CLI conformance E2E with the limitation recorded. Update runtime integration documentation.
Activity
SaulMoro commentedon Oct 13, 2026
next/report <run>find the run through the TeamAI scope of the current directory. A driver whose workspace is outside the product repo, like a Paseo or remote workspace, resolves another scope and getsrun_not_foundfor a run that exists. Maybe the lookup shouldn't depend on the cwd, or the acceptance criteria could include "next and report find the run from the driver's workspace"?hsuchifeng commentedon Oct 14, 2026
nextandreportfind the run by id. They do not resolve it through the TeamAI scope of the current directory. A driver whose workspace is outside the product repo, including Paseo, can address an existing run.This issue reuses the conformance suite added in #1077.
SaulMoro commentedon Oct 14, 2026
Notes from #1078 (#1129) on the driver contract:
envon command steps, a map of already-rendered strings. A driver must set these variables for the command and never put them into the command string. Inputs reach a command only this way.stepis a path, such asship.check.classify. Treat it as an opaque id.env, sub-workflow paths and recovery after a failure. An adapter that passes it handles graph runs.The engine rules that span files are in
docs/dev/workflow-engine.md, added by #1129.SaulMoro commentedon Oct 16, 2026
A lease for a prompt step will carry two model fields (#1177):
model, the step's own, anddefaultModel, the workflow'sdefaults.modelin effect for the step. Each is an alias or a model name, resolved per tool with the member's aliases.The driver picks the model, first match wins: the step's
model, the model set by the definition deployed for its tool,defaultModel, the tool's default. A default fills a gap and never replaces a model a definition sets for its role. Only the driver can read the deployed definition, so this order cannot be applied before the lease.When the first match is the step's
modelordefaultModeland that model cannot run, the driver fails the step withmodel_unavailable. That covers an alias with no model for the tool, and a driver that cannot switch models, such as a session that runs every step on its own model. It does not run the tool's default, which would record a result for a model the step did not ask for. It does not release the lease either, sincenexthands a released step straight back to the same driver. No capability says which models a driver can run, so this lease does not stay available to another driver the way a declined requirement does. How a driver applies a model that only the definition sets does not change.SaulMoro commentedon Oct 20, 2026
Run lookup by id moved to #1086, per the decision there. F2, F3, F4 and F5 in #1246 change the contract this adapter meets, and the fetch rule proposed on #1084 belongs to the same driver contract. If #1085 adopts
can.judge, the same applies here: never take a scorer lease without a judge profile #1085 verifies.