Add a headless workflow CLI and console executable - #112
Merged
Merged
Conversation
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
1 participant
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.
Add a headless workflow CLI that shares the desktop database and execution engine. It can initialize a workspace, validate/create/update/patch workflows, run them synchronously, and inspect versions, run status and results without opening the GUI.
The CLI emits UTF-8 JSON, supports isolated workspaces and external per-process model settings, preserves metadata on updates, and avoids hidden model calls for tool descriptions. Model nodes gain bounded output/concurrency settings, fixed-endpoint selection and actionable schema diagnostics. Rate-limit cleanup timers no longer delay command exit.
Desktop packages include a console-mode VectorVeinCLI executable sharing the existing bundle. Release jobs smoke-test the packaged entry point.
Validation: 60 backend tests pass, including real CLI subprocess lifecycle and credential-error cases; backend lint and changed-file type checks pass. The CLI has also created and run real model workflows using external configuration. Packaged executable smoke checks run during release builds.