dispatch open <id> and dispatch export <id> require the full session ID. IDs are long, so resolving one means copying it from search --ids or the TUI first. Git solved this years ago with short SHAs.
Accept a unique prefix of a session ID anywhere a full <id> is taken (open, export). Resolution mirrors git: an exact full-ID match always wins, a unique prefix expands to its full ID, and an ambiguous prefix is rejected with a list of the matching sessions so you can add a few more characters.
Acceptance criteria
open <prefix> and export <prefix> resolve a unique prefix to the full session ID.- An exact full-ID match takes priority over any prefix collision.
- An ambiguous prefix returns an error naming the matching session IDs.
- A prefix with no match returns the same not-found result as an unknown full ID.
- Prefix matching treats
_ and % as literal characters, not wildcards.
dispatch help documents that <id> accepts a unique prefix.
dispatch open <id>anddispatch export <id>require the full session ID. IDs are long, so resolving one means copying it fromsearch --idsor the TUI first. Git solved this years ago with short SHAs.Accept a unique prefix of a session ID anywhere a full
<id>is taken (open,export). Resolution mirrors git: an exact full-ID match always wins, a unique prefix expands to its full ID, and an ambiguous prefix is rejected with a list of the matching sessions so you can add a few more characters.Acceptance criteria
open <prefix>andexport <prefix>resolve a unique prefix to the full session ID._and%as literal characters, not wildcards.dispatch helpdocuments that<id>accepts a unique prefix.