Conversation
Contributor
Author
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
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
flow.run.titlerunTitlethrough flow state, manifests, CLI output, and replay-viewer recent-run summariespr-triageto emit descriptive titles likePR-triage-acpx-167Design
The new API is intentionally run-scoped, not flow-name scoped:
flow.namestays stable for IDs, routing, and file namingflow.run.titleis resolved once at run start and used only as display metadata{ input, flowName, flowPath }That keeps the title flexible for future workflows without turning
flow.nameinto a user-visible convention bucket.Validation
pnpm run checkpr-triageflow object with a fast single-node sliceVerified runtime result:
{"repo":"openclaw/acpx","prNumber":167}PR-triage-acpx-167result.state.runTitleandmanifest.json