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

feat: handle --channels permission relay in permission UI (v2.1.81) #238

New Issue
Closed
opened 2026-03-23 14:01:55 -07:00 by hikari · 1 comment
hikari commented 2026-03-23 14:01:55 -07:00
Owner
Copy Link
Copy Source

Context

Claude Code v2.1.81 added a --channels permission relay. Channel servers that declare the permission capability can now forward tool approval prompts to the user's phone.

Why This Matters

Hikari Desktop has its own permission handling UI (permission sprite state, approval/denial flow). We should be aware of this new relay mechanism and decide:

  1. Whether to expose --channels as a config option
  2. Whether our existing permission UI needs to account for prompts that may be relayed from a channel server
  3. Whether the stream-json protocol surfaces any new message types related to channel-relayed permissions

Tasks

  • Investigate the --channels flag and how channel permission relay appears in stream-json output
  • Determine if any new message types or tool use blocks are emitted
  • Update src-tauri/src/types.rs if new types are needed
  • Consider adding --channels as a config option in the UI if useful
  • Add tests for any new message handling

References

  • Claude Code v2.1.81 changelog
  • src-tauri/src/types.rs
  • src-tauri/src/wsl_bridge.rs

✨ This issue was created with help from Hikari~ 🌸

## Context Claude Code v2.1.81 added a `--channels` permission relay. Channel servers that declare the permission capability can now forward tool approval prompts to the user's phone. ## Why This Matters Hikari Desktop has its own permission handling UI (`permission` sprite state, approval/denial flow). We should be aware of this new relay mechanism and decide: 1. Whether to expose `--channels` as a config option 2. Whether our existing permission UI needs to account for prompts that may be relayed from a channel server 3. Whether the stream-json protocol surfaces any new message types related to channel-relayed permissions ## Tasks - [ ] Investigate the `--channels` flag and how channel permission relay appears in stream-json output - [ ] Determine if any new message types or tool use blocks are emitted - [ ] Update `src-tauri/src/types.rs` if new types are needed - [ ] Consider adding `--channels` as a config option in the UI if useful - [ ] Add tests for any new message handling ## References - Claude Code v2.1.81 changelog - `src-tauri/src/types.rs` - `src-tauri/src/wsl_bridge.rs` ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-04-13 11:29:47 -07:00
Author
Owner
Copy Link
Copy Source

Investigation

Investigated the --channels permission relay feature (v2.1.81).

Hikari Desktop does not have a PreToolUse hook response mechanism — workspace trust is enforced at session start via --allowedTools flags rather than through live permission relay. There is no plumbing to respond to permission requests mid-session via channels.

This feature is only relevant to implementations that intercept and respond to PreToolUse hooks, which Hikari Desktop does not do. Closing as not applicable.

✨ Closed with help from Hikari~ 🌸

## Investigation Investigated the `--channels` permission relay feature (v2.1.81). Hikari Desktop does not have a PreToolUse hook response mechanism — workspace trust is enforced at session start via `--allowedTools` flags rather than through live permission relay. There is no plumbing to respond to permission requests mid-session via channels. This feature is only relevant to implementations that intercept and respond to PreToolUse hooks, which Hikari Desktop does not do. Closing as not applicable. ✨ Closed with help from Hikari~ 🌸
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#238
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?