Feature Request: Expose additional ports (SSH/port 22)

[grmkris]

Use Case

We're building a platform on top of Sprites where users create dev environments (boxes). Users want to connect to their sprites using:

• SSH (port 22) for terminal access
• Cursor/VS Code Remote-SSH for IDE integration

Current Limitation

Currently only port 8080 is exposed publicly. While the Sprite CLI's sprite proxy command can tunnel any port via WebSocket, this requires users to have the Sprite CLI installed and authenticated - which doesn't work for our use case where end-users only interact through our web UI.

Request

Would it be possible to:

1. Expose port 22 (SSH) directly on the sprite's public URL, or
2. Allow configuring additional exposed ports during sprite creation, or
3. Provide an alternative mechanism for direct SSH access without requiring the Sprite CLI on the user's machine

Workarounds Considered

• Tailscale: Works but requires users to set up Tailscale first
• WebSocket-to-SSH bridge: Would need a client-side connector app
• Browser-based terminal: Works but not compatible with native IDEs like Cursor

Ideal Solution

Being able to specify exposed ports when creating a sprite, e.g.:

ports: [8080, 22]

Or having SSH exposed by default alongside HTTP.

Thanks for considering this! Happy to provide more context.