nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

feat: handle new Elicitation and ElicitationResult hook events #223

New Issue
Closed
opened 2026-03-20 08:25:34 -07:00 by hikari · 0 comments
hikari commented 2026-03-20 08:25:34 -07:00
Owner
Copy Link
Copy Source

Background

CLI v2.1.76 introduced MCP elicitation support. MCP servers can now request structured input from the user mid-task via an interactive dialog. Two new hook types were added to support this:

  • Elicitation — fires when an MCP server requests structured input
  • ElicitationResult — fires after the user responds to an elicitation request

Why It Matters for Hikari Desktop

Hikari Desktop intercepts hook events to drive the character state, the permission modal, and the task display. If an Elicitation event arrives and we do not handle it, the user will see no UI feedback — the session will appear stuck because the MCP server is waiting for input that Hikari Desktop has silently swallowed.

At minimum we need to:

  1. Parse Elicitation events in wsl_bridge.rs and emit them to the frontend
  2. Display a new modal (similar to UserQuestionModal) that lets the user fill in the structured fields and submit a response back via stdin
  3. Switch the character to the permission state whilst waiting for the user to respond
  4. Parse ElicitationResult in wsl_bridge.rs to reset character state once the dialog is dismissed

Acceptance Criteria

  • Elicitation event parsed and emitted as a new Tauri event
  • Frontend modal rendered with the structured fields from the elicitation request
  • User response serialised and written back to stdin
  • ElicitationResult event handled to clear the modal and reset character state
  • Tests for the new event types in types.rs and the Svelte component

✨ This issue was created with help from Hikari~ 🌸

## Background CLI v2.1.76 introduced MCP elicitation support. MCP servers can now request structured input from the user mid-task via an interactive dialog. Two new hook types were added to support this: - `Elicitation` — fires when an MCP server requests structured input - `ElicitationResult` — fires after the user responds to an elicitation request ## Why It Matters for Hikari Desktop Hikari Desktop intercepts hook events to drive the character state, the permission modal, and the task display. If an `Elicitation` event arrives and we do not handle it, the user will see no UI feedback — the session will appear stuck because the MCP server is waiting for input that Hikari Desktop has silently swallowed. At minimum we need to: 1. Parse `Elicitation` events in `wsl_bridge.rs` and emit them to the frontend 2. Display a new modal (similar to `UserQuestionModal`) that lets the user fill in the structured fields and submit a response back via `stdin` 3. Switch the character to the `permission` state whilst waiting for the user to respond 4. Parse `ElicitationResult` in `wsl_bridge.rs` to reset character state once the dialog is dismissed ## Acceptance Criteria - [ ] `Elicitation` event parsed and emitted as a new Tauri event - [ ] Frontend modal rendered with the structured fields from the elicitation request - [ ] User response serialised and written back to `stdin` - [ ] `ElicitationResult` event handled to clear the modal and reset character state - [ ] Tests for the new event types in `types.rs` and the Svelte component ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-23 14:28:09 -07:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#223
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?