TL;DR

The issue with acpx flow run returning empty strings for ACP node outputs may be related to how the acp function handles prompts or the flow configuration, and verifying the prompt function and flow definitions is necessary.

Guidance

• Review the acp function usage in the flow definitions to ensure prompts are correctly defined and passed.
• Verify that the prompt function returns the expected string, considering any potential async operations or context dependencies.
• Check for any updates or known issues in the acpx package version 0.6.1 that might relate to ACP node output handling.
• Test with different prompt types (e.g., static strings vs. dynamic functions) to isolate the issue.

Example

// Example of testing with a static prompt string
nodes: {
  step1: acp({ prompt: "Reply with exactly STATIC_OK" }),
}

Notes

The issue seems specific to the acpx flow run command and does not occur with direct acpx <agent> exec commands, suggesting a potential issue with how flows are executed or outputs are captured.

Recommendation

Apply a workaround by testing with different prompt configurations and flow definitions to identify the root cause, as upgrading to a potentially fixed version is not explicitly implied in the given information.