Keep the output with the run.
Use Bash for a worker, a build or a test command your team already runs. Reflow retains stdout, stderr and the exit code, with selected output files when you need them.
- Stdout and stderr
- Exit code
- Selected output files
Run your application’s own commands and keep their output for comparison. An exit code tells you the command finished; its result tells you what happened.
worker.bash
command="./bin/fulfill order-1042" Your application command. Its result becomes a snapshot.
order: 1042 status: dispatched tracking_number:
TRK-1042 order: 1042 status: dispatched Both commands succeeded. The saved output differs.
“The worker still reports ‘dispatched’, but no longer returns a tracking number. Can the shipment notification still include a tracking link?”
Evidence: before + after / stdout.txtUse Bash for a worker, a build or a test command your team already runs. Reflow retains stdout, stderr and the exit code, with selected output files when you need them.
Compare the retained command results and captured files from two runs. Your agent can inspect an output change even when both commands exited successfully.
A fulfillment worker still reports success, but the tracking number has disappeared from its output. Your agent can relate that difference to the customer’s delivery updates and flag it in the PR review.
Bring the evidence into PR reviewPoint the private LocalBash connection at your application’s working directory. The example uses the application’s fulfillment command; replace it with the command you want to exercise.
Your agent can inspect the installed plugin’s commands and write the flow using your application knowledge. Select the plugin version in the flow’s requirements.
---
providers:
worker: LocalBash
---
worker.bash command="./bin/fulfill order-1042"Plugin requirements and private connection settings are configured separately.