Problem statement
Typing / in an existing session completes skills and project commands. Typing / in the new-session composer does not, even with a machine selected, connected, and a folder picked.
So the first message of a session is the one place where a long skill name has to be typed from memory, exactly, with no completion. That is the hardest place to get it right and the easiest place to give up and type something vaguer.
Proposed solution
No strong opinion on the design, and this may well be a bad suggestion. Some kind of cache, or an optional request to the relay asking what slash commands exist for the selected machine and folder. Whatever fits the architecture.
The need is just that the new-session composer completes skill names the same way an active session does.
Acceptance criteria
Non-goals (optional)
No response
Priority (optional)
No response
Additional context (optional)
Happier CLI 0.2.10-dev.74, self-hosted server.
Problem statement
Typing
/in an existing session completes skills and project commands. Typing/in the new-session composer does not, even with a machine selected, connected, and a folder picked.So the first message of a session is the one place where a long skill name has to be typed from memory, exactly, with no completion. That is the hardest place to get it right and the easiest place to give up and type something vaguer.
Proposed solution
No strong opinion on the design, and this may well be a bad suggestion. Some kind of cache, or an optional request to the relay asking what slash commands exist for the selected machine and folder. Whatever fits the architecture.
The need is just that the new-session composer completes skill names the same way an active session does.
Acceptance criteria
/in the new-session composer lists the skills available in the selected machine and folderNon-goals (optional)
No response
Priority (optional)
No response
Additional context (optional)
Happier CLI 0.2.10-dev.74, self-hosted server.