nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 15 Pull Requests 37 Actions Releases 23 Activity

Support remote session browsing and resumption #124

New Issue
Closed
opened 2026-02-06 16:31:25 -08:00 by hikari Β· 1 comment
hikari commented 2026-02-06 16:31:25 -08:00
Owner
Copy Link
Copy Source

Description

Claude Code 2.1.33 (VSCode) added the ability to browse and resume sessions from claude.ai, enabling cross-platform session continuity.

Current State

We don't support browsing or resuming remote sessions.

Proposed Changes

  1. Investigate if remote session APIs are available via the CLI
  2. If available, add a session browser panel to list remote sessions
  3. Add ability to resume a remote session in Hikari
  4. Consider syncing local session history with remote

References

Priority

Low - Depends on API availability; nice-to-have for cross-platform workflows

✨ This issue was created with help from Hikari~ 🌸

## Description Claude Code 2.1.33 (VSCode) added the ability to browse and resume sessions from claude.ai, enabling cross-platform session continuity. ## Current State We don't support browsing or resuming remote sessions. ## Proposed Changes 1. Investigate if remote session APIs are available via the CLI 2. If available, add a session browser panel to list remote sessions 3. Add ability to resume a remote session in Hikari 4. Consider syncing local session history with remote ## References - [Changelog 2.1.33](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#2133) ## Priority Low - Depends on API availability; nice-to-have for cross-platform workflows ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-02-07 13:23:06 -08:00
Author
Owner
Copy Link
Copy Source

Investigation Results πŸ”

I've investigated whether remote session browsing is available in the CLI (we're running v2.1.34), and here's what I found:

CLI Support: ❌ Not Available

Remote session browsing was added to the VSCode extension in v2.1.33, but it's not available in the CLI:

  • No CLI flags for listing remote sessions
  • No API endpoints for claude.ai session access
  • No authentication flow for claude.ai in CLI
  • Sessions are only stored locally in ~/.claude/sessions/

Could We Implement It Ourselves? πŸ€”

Theoretically possible, BUT extremely difficult:

What we'd need:

  1. Authenticate with Anthropic's claude.ai API
  2. Access private session storage APIs
  3. Implement OAuth flow in our Tauri app
  4. Handle session sync between local and remote

Complexity: Very High (20+ hours)

  • Reverse-engineer private claude.ai APIs
  • Implement OAuth authentication
  • Handle session sync logic
  • Build session browser UI

Major barriers:

  • ❌ No public API documentation for remote sessions
  • ❌ Would require reverse-engineering VSCode extension
  • ❌ Private APIs could break at any time
  • ❌ Unclear if Anthropic allows third-party access

Why We're Not Implementing It 🎯

Reasons:

  1. No API access - Would require reverse-engineering private APIs
  2. Fragile solution - Could break with any Anthropic backend change
  3. Very high complexity - 20+ hours for a niche feature
  4. VSCode-specific - Designed for VSCode's architecture
  5. Better priorities - Time better spent on achievable features

Conclusion βœ…

Closing as Won't Implement because:

  • Feature requires private APIs we don't have access to
  • Would need to reverse-engineer VSCode extension
  • Too fragile and high-risk for uncertain benefit
  • CLI architecture doesn't support this use case

Note: If Anthropic ever releases public APIs for remote session access, this could be revisited!

✨ This assessment was done with help from Hikari~ 🌸

## Investigation Results πŸ” I've investigated whether remote session browsing is available in the CLI (we're running v2.1.34), and here's what I found: ### CLI Support: ❌ Not Available Remote session browsing was added to the **VSCode extension** in v2.1.33, but it's **not available in the CLI**: - No CLI flags for listing remote sessions - No API endpoints for claude.ai session access - No authentication flow for claude.ai in CLI - Sessions are only stored locally in `~/.claude/sessions/` ### Could We Implement It Ourselves? πŸ€” **Theoretically possible, BUT extremely difficult:** **What we'd need:** 1. Authenticate with Anthropic's claude.ai API 2. Access private session storage APIs 3. Implement OAuth flow in our Tauri app 4. Handle session sync between local and remote **Complexity:** Very High (20+ hours) - Reverse-engineer private claude.ai APIs - Implement OAuth authentication - Handle session sync logic - Build session browser UI **Major barriers:** - ❌ No public API documentation for remote sessions - ❌ Would require reverse-engineering VSCode extension - ❌ Private APIs could break at any time - ❌ Unclear if Anthropic allows third-party access ### Why We're Not Implementing It 🎯 **Reasons:** 1. **No API access** - Would require reverse-engineering private APIs 2. **Fragile solution** - Could break with any Anthropic backend change 3. **Very high complexity** - 20+ hours for a niche feature 4. **VSCode-specific** - Designed for VSCode's architecture 5. **Better priorities** - Time better spent on achievable features ### Conclusion βœ… Closing as **Won't Implement** because: - Feature requires private APIs we don't have access to - Would need to reverse-engineer VSCode extension - Too fragile and high-risk for uncertain benefit - CLI architecture doesn't support this use case **Note:** If Anthropic ever releases public APIs for remote session access, this could be revisited! ✨ This assessment was done 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#124
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?