You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[feat] Run prompt and agent steps with the local driver #1077
A prompt-only workflow runs through one configured local AI tool.
A named agent is leased only when available in the selected tool environment.
Missing tools, missing agents, invalid output, and child-process failures become stable step failures.
The adapter cannot bypass engine output validation.
Prompts, outputs, and secrets are not logged by default.
A raw model or tool default works without model aliases.
A run at an older revision uses its cached prompt_file content after the source file is changed or deleted.
The same conformance scenarios produce equivalent results through the in-process engine and next/report --json.
Verification
Focused adapter, agent-lookup, result-parsing, diagnostic, prompt-cache, and direct/CLI conformance tests; build/typecheck/lint; one real-CLI E2E with one representative AI executable. Update the bilingual workflow guide for agent steps.
The cache keeps the last valid YAML, but prompt_file is read at run time, so a workflow kept at its old version would run the new prompt, or fail on a deleted one. Maybe pull could check that the file exists and cache it with the definition?
The conformance suite lands here: the same scenarios through the in-process engine and through next/report --json. #1087 reuses it. That also covers parseReport, which currently runs only on the CLI path.
prompt_file is checked when the workflow is pulled and cached with the definition. A run pinned to an older revision uses that cached prompt, even if the source file is later changed or deleted.
Activity
SaulMoro commentedon Oct 13, 2026
Two ideas for this one:
next/report --json) is planned for [feat] Add a Paseo driver adapter #1087, the last ticket. Since the local driver starts growing here, maybe it could land here and [feat] Add a Paseo driver adapter #1087 reuse it? There's already a small gap:parseReportonly runs on the CLI path.prompt_fileis read at run time, so a workflow kept at its old version would run the new prompt, or fail on a deleted one. Maybe pull could check that the file exists and cache it with the definition?hsuchifeng commentedon Oct 14, 2026
The conformance suite lands here: the same scenarios through the in-process engine and through
next/report --json. #1087 reuses it. That also coversparseReport, which currently runs only on the CLI path.prompt_fileis checked when the workflow is pulled and cached with the definition. A run pinned to an older revision uses that cached prompt, even if the source file is later changed or deleted.Remote drivers stay out of scope.