Skip to content

fix(cli): preserve literal execution arguments and exec alias - #108

Open
Simon Liang (AgentWings) wants to merge 1 commit into
scalar-nextfrom
fix/execution-argv
Open

Simon Liang (AgentWings) wants to merge 1 commit into
scalar-nextfrom
fix/execution-argv

Conversation

@AgentWings

Copy link
Copy Markdown
Collaborator

Summary

Restore dedalus machines exec --machine-id <id> -- <command> [args...] and the optional create verb. Literal remote arguments preserve spaces, empty values, flags, and @file text without reading local files. Combining argv with --command, omitting the separator, or using an empty executable fails before making an API request.

The existing machines:executions commands remain available; machines executions and both exec spellings share their API handlers, authentication, and output behavior. Execution management commands and JSON --command input continue working.

Validation

  • npm run build and npm run typecheck passed.

  • node --test tests/*.test.mjs: 42 tests passed, including 3 new HTTP-boundary tests covering resource spellings, implicit/explicit create, literal argv, rejected input, and existing commands.

  • Added the new tests to the default test script and installed-package verifier.

  • pnpm run test:package: clean tarball installation passed all 29 selected tests, including execution HTTP-boundary checks.

The custom registration calls a small literal-value guard in the generated runtime. Hosted regeneration and live machine execution have not been verified.

Repro / Showcase

N/A (no visual surface changed)

dedalus machines exec --machine-id <id> -- printf '%s\n' '@remote-file'

Reviewers

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant