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

feat: remote instance monitoring panel #187

New Issue
Open
opened 2026-03-06 09:33:46 -08:00 by hikari · 0 comments
hikari commented 2026-03-06 09:33:46 -08:00
Owner
Copy Link
Copy Source

Overview

Inspired by ralph-tui's remote instance management feature, this adds a Remote Instance Panel that allows monitoring and controlling Hikari Desktop sessions running on other machines from a unified interface.

User Story

As a developer who runs Claude Code sessions on multiple machines (e.g. a powerful server for heavy tasks and a local laptop for quick edits), I want a single Hikari window that shows me the status of all my running instances, so I can monitor progress without switching machines.

Feature Details

Architecture

  • Each Hikari instance exposes a lightweight local server (WebSocket or HTTP)
  • Remote instances are registered by host/port + authentication token
  • The monitoring panel polls or subscribes to events from each registered instance

Remote Panel UI

  • Instance List: Sidebar listing all registered remote instances
    • Status indicator (connected / disconnected / error)
    • Latency display (ms ping)
    • Current conversation count and active task status
    • Last activity timestamp
  • Instance Detail View: Clicking an instance shows:
    • Live terminal output (read-only stream)
    • Current conversation list
    • Token/cost stats
    • Task loop progress (if running)
  • Add/Remove Instance: Form to register a new remote by host:port + token

Authentication

  • Token-based: each Hikari instance generates a local server token on first run
  • Tokens stored in ~/.config/Hikari/remote-tokens.json
  • Connection tokens separate from server tokens (shorter-lived) for session handshakes
  • Automatic reconnection with exponential backoff on disconnect

Configuration Push

  • Optionally push configuration (model, budget limits) to remote instances
  • Remote instances can accept or reject pushed config based on their own settings

Keyboard Navigation

  • Tab key cycles between local and remote instance views
  • Escape returns to local view

Implementation Notes

  • The local server should be opt-in and off by default (security consideration)
  • Server binds to 127.0.0.1 only by default; user must explicitly enable external access
  • All communication should be over authenticated WebSocket

Acceptance Criteria

  • Hikari can optionally expose a local monitoring server (opt-in, localhost only by default)
  • Remote instances can be registered by host:port + auth token
  • Panel displays live status of all registered instances
  • Live terminal output from remote instances is readable (read-only)
  • Latency/connection status displayed per instance
  • Graceful handling of disconnection with auto-reconnect
  • Server is off by default with a clear enable toggle in settings
  • Tests written for server logic, connection handling, and token management

✨ This issue was created with help from Hikari~ 🌸

## Overview Inspired by [ralph-tui](https://github.com/subsy/ralph-tui)'s remote instance management feature, this adds a **Remote Instance Panel** that allows monitoring and controlling Hikari Desktop sessions running on other machines from a unified interface. ## User Story As a developer who runs Claude Code sessions on multiple machines (e.g. a powerful server for heavy tasks and a local laptop for quick edits), I want a single Hikari window that shows me the status of all my running instances, so I can monitor progress without switching machines. ## Feature Details ### Architecture - Each Hikari instance exposes a lightweight local server (WebSocket or HTTP) - Remote instances are registered by host/port + authentication token - The monitoring panel polls or subscribes to events from each registered instance ### Remote Panel UI - **Instance List**: Sidebar listing all registered remote instances - Status indicator (connected / disconnected / error) - Latency display (ms ping) - Current conversation count and active task status - Last activity timestamp - **Instance Detail View**: Clicking an instance shows: - Live terminal output (read-only stream) - Current conversation list - Token/cost stats - Task loop progress (if running) - **Add/Remove Instance**: Form to register a new remote by host:port + token ### Authentication - Token-based: each Hikari instance generates a local server token on first run - Tokens stored in `~/.config/Hikari/remote-tokens.json` - Connection tokens separate from server tokens (shorter-lived) for session handshakes - Automatic reconnection with exponential backoff on disconnect ### Configuration Push - Optionally push configuration (model, budget limits) to remote instances - Remote instances can accept or reject pushed config based on their own settings ### Keyboard Navigation - Tab key cycles between local and remote instance views - Escape returns to local view ## Implementation Notes - The local server should be opt-in and off by default (security consideration) - Server binds to `127.0.0.1` only by default; user must explicitly enable external access - All communication should be over authenticated WebSocket ## Acceptance Criteria - [ ] Hikari can optionally expose a local monitoring server (opt-in, localhost only by default) - [ ] Remote instances can be registered by host:port + auth token - [ ] Panel displays live status of all registered instances - [ ] Live terminal output from remote instances is readable (read-only) - [ ] Latency/connection status displayed per instance - [ ] Graceful handling of disconnection with auto-reconnect - [ ] Server is off by default with a clear enable toggle in settings - [ ] Tests written for server logic, connection handling, and token management ✨ This issue was created 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#187
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?