feat: add cloud option to support oz agent run-cloud#29
Merged
Conversation
Add a new 'cloud' boolean input to the action that, when set to true, triggers the agent using 'oz agent run-cloud' instead of 'oz agent run'. - Add 'cloud' input to action.yml (default: false) - Use 'run-cloud' subcommand when cloud is true - Skip '--sandboxed' flag for cloud runs (not applicable) - Add tests for cloud and non-cloud code paths Co-Authored-By: Oz <oz-agent@warp.dev>
The previous npm install updated the lock file with newer @emnapi package versions, causing npm ci to fail in CI. Restore the original lock file from main since no new dependencies were added. Co-Authored-By: Oz <oz-agent@warp.dev>
advait-m
approved these changes
Jun 24, 2026
advait-m
left a comment
advait-m
left a comment
Member
There was a problem hiding this comment.
nice! small comment around gating
| if (profile) { | ||
| args.push('--profile', profile) | ||
| } else { | ||
| } else if (!cloud) { |
Member
There was a problem hiding this comment.
if I'm understanding correctly -run-cloud doesn't accept --cwd, --profile, or --share either (run-only flags), so cloud: true + any of them fails with unexpected argument? could make sense to gate those on !cloud too. happy path's fine since they default empty
i.e. if (profile && !cloud) etc
Collaborator
Author
There was a problem hiding this comment.
Good catch — done in 10caa56.
Added tests covering both paths (cloud: flags omitted + warnings emitted; non-cloud: flags passed, --sandboxed skipped when a profile is set) and rebuilt dist/index.js.
…rrors `oz agent run-cloud` does not accept `--cwd`, `--profile`, or `--share` (run-only flags), so passing any of them with `cloud: true` failed with an unexpected-argument error. Gate these on `!cloud`, matching the existing `--sandboxed` gating, and emit a `core.warning` when a caller sets one of them for a cloud run so the dropped input is discoverable instead of silently ignored. Co-Authored-By: Oz <oz-agent@warp.dev>
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
2 participants
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.
Summary
Add a new
cloudboolean input tooz-agent-actionthat allows triggering an agent run withoz agent run-cloudinstead ofoz agent run.Changes
action.yml: Addedcloudinput (default:false). When set totrue, the action usesoz agent run-cloudas the subcommand.src/index.ts: Read thecloudinput viacore.getBooleanInputand selectrun-cloudvsrunaccordingly. Also skips the--sandboxedflag for cloud runs (it doesn't apply to cloud execution).src/index.test.ts: AddedgetBooleanInputmock and two new test cases for cloud/non-cloud behavior.dist/index.js: Rebuilt bundle.Usage
Conversation: https://staging.warp.dev/conversation/0326076a-2a04-4ed0-90ee-4124eea39fb3
Run: https://oz.staging.warp.dev/runs/019ef732-09cd-7800-bb3f-7b54e1ec8727
This PR was generated with Oz.