Skip to content

fix(cli): support file payload args for step and eval run#27

Merged
jt-poolside merged 2 commits intomainfrom
jt/file-input
Mar 30, 2026
Merged

fix(cli): support file payload args for step and eval run#27
jt-poolside merged 2 commits intomainfrom
jt/file-input

Conversation

@jt-poolside
Copy link
Copy Markdown
Contributor

Summary

  • fix bridge run --results-file so file-provided results are used for actual step invocation
  • add file payload args for step run:
    • --input-file
    • --results-file
  • add file payload arg for eval run:
    • --context-file
  • keep existing inline args and --context @path behavior for compatibility
  • add explicit argument validation for mutually exclusive / missing payload sources
  • add CLI tests covering step and eval file-argument paths

Why

Forge now supports sandbox file payload transport to avoid argv size limits; SDK CLI needs reliable file-arg support for the execution path.

Test Plan

  • uv run pytest tests/test_cli.py tests/test_invoke_step.py tests/test_eval.py

Cross-repo

Companion Forge PR switches step/eval runtime payload transport to sandbox files with compatibility fallback.

@jt-poolside jt-poolside requested a review from tkpoolside March 26, 2026 13:18
Copy link
Copy Markdown
Collaborator

@tkpoolside tkpoolside left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's update readme but otherwise LGTM!

@jt-poolside
Copy link
Copy Markdown
Contributor Author

Let's update readme but otherwise LGTM!

good catch. done

@jt-poolside jt-poolside merged commit d61d70a into main Mar 30, 2026
6 checks passed
@jt-poolside jt-poolside deleted the jt/file-input branch March 30, 2026 15:18
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.

2 participants