What
Typing /wor and pressing Tab correctly completes the command to /workflow , including the trailing space, but the list of /workflow arguments is not displayed. The user has to delete the inserted space and type it again before suggestions such as run, create, list, status, resume, cancel, and delete appear.
Description
- Expected behavior: Accepting
/workflow with Tab should move directly into argument completion and display the available subcommands because the cursor is already positioned after the command separator.
- Actual behavior: Tab applies the command-name completion and closes the autocomplete popup. The text is ready for an argument, but no argument-completion request is made.
- Root cause: This is in the shared PI TUI autocomplete transition, not in the workflow candidate provider.
CombinedAutocompleteProvider.applyCompletion appends a space when it applies a slash-command name. The editor's Tab-selection path then calls cancelAutocomplete() and does not trigger a new completion request for the updated /workflow text. Deleting the space re-triggers command completion; typing the space while that popup is active updates it into argument completion, which explains the reported workaround.
What
Typing
/worand pressing Tab correctly completes the command to/workflow, including the trailing space, but the list of/workflowarguments is not displayed. The user has to delete the inserted space and type it again before suggestions such asrun,create,list,status,resume,cancel, anddeleteappear.Description
/workflowwith Tab should move directly into argument completion and display the available subcommands because the cursor is already positioned after the command separator.CombinedAutocompleteProvider.applyCompletionappends a space when it applies a slash-command name. The editor's Tab-selection path then callscancelAutocomplete()and does not trigger a new completion request for the updated/workflowtext. Deleting the space re-triggers command completion; typing the space while that popup is active updates it into argument completion, which explains the reported workaround.