Release v1.0.31: first-class Shell agents - #15
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
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.
What changed
orch run <task-id>subscribed through asynchronous completion so failed commands return a non-zero process exit code.1.0.31and adds complete release notes toCHANGELOG.md.Why
Shell commands previously existed as an adapter-level capability but were not presented as a coherent agent workflow. Users had to understand AI-agent configuration fields that do not apply to command runners, and asynchronous completion or debounced validation could produce misleading results at the edges.
Impact
Users can now create a Shell agent by selecting Shell and entering a command. The command runs from the task workspace; exit code
0completes the run and any non-zero exit fails it. Existing AI-agent workflows remain unchanged.Root causes fixed
Validation
npm run typechecknpm test— 2069 passed, 2 skippednpm run build1.0.31Release note
The
v1.0.31tag is intentionally not pushed by this PR: pushing it triggers npm publication and GitHub Release creation automatically. Tag after merge when ready to publish.