Skip to content

Feature Request: Remote Claude Code session support via SSH #163

@docchang

Description

@docchang

Feature Request: Remote Claude Code Session Support via SSH

Summary

Add native SSH connectivity to Claudia for managing remote Claude Code sessions, enabling developers to use any client device while running Claude Code on remote development servers.

Problem Statement

Currently, Claudia only works with the local ~/.claude directory, forcing all development to happen on the client machine. This conflicts with modern development practices where:

Development Reality

  • Development servers are typically remote Linux instances (cloud, on-prem, homelab)
  • Client machines can be anything (Mac, Windows, Linux)
  • Deploy targets are almost always remote Linux servers
  • Team environments require shared remote development instances

Current Limitations

  • Claudia forces development onto potentially incompatible client OS
  • No access to always-on remote development environments
  • Cannot leverage powerful remote compute resources
  • Difficult team collaboration on shared development instances
  • Environment inconsistency between development and deployment

Proposed Solution

Add SSH connectivity features to Claudia that allow:

  1. Remote Connection Configuration

    • SSH host/port/user configuration in Claudia settings
    • SSH key authentication support
    • Connection testing and validation
  2. Remote Session Management

    • Browse and manage sessions from remote ~/.claude directories
    • Fork remote sessions locally or on remote
    • Resume remote sessions via SSH tunnel
  3. Hybrid Workflow Support

    • Seamless switching between local and remote sessions
    • Session synchronization options (one-way/two-way)
    • Local caching of remote session metadata

Implementation Ideas

  • Use SSH2 libraries to establish secure connections
  • Mount remote ~/.claude directories via SSHFS or similar
  • Add remote server management UI in Claudia settings
  • Implement connection pooling for performance

Use Cases

  • Client-Server Development: Use any client device (Mac, Windows, Linux) to manage Claude Code running on remote development servers
  • Environment Consistency: Develop on the same OS/environment as production deployment
  • Team Collaboration: Multiple developers accessing shared remote development instances
  • Always-On Development: 24/7 remote servers vs. laptops that sleep/disconnect
  • Resource Optimization: Lightweight clients controlling powerful remote compute

Benefits

  • Platform Flexibility: Client can be any device with Claudia GUI
  • Environment Parity: Development matches deployment environment exactly
  • Resource Efficiency: Separates GUI from compute requirements
  • Team Scalability: Shared remote instances for collaboration
  • Deployment Confidence: Eliminates "works on my machine" issues

Additional Notes

This would complement existing local functionality without disrupting current workflows. Users could choose to work locally, remotely, or in hybrid mode based on their needs.


Thank you for considering this feature request! This would significantly expand Claudia's capabilities for users with remote development needs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions