← All docs
Getting started
Your first sessionThe workspaceSSH access
Core concepts
Agent rolesExperimentsResearch plansCanvasWorkflows
Integrations
GitHubWebhooksNotifications
Platform
Billing and plansAgent memoryMulti-chatKeyboard shortcuts
Reference
GPU catalogAgent toolsAPI referenceSecurityLimits and quotas
← Docs
Getting started

SSH access

Why SSH

The workspace chat handles most tasks. But sometimes you want a real terminal for running htop, using vim, or connecting your local IDE. SSH gives you direct shell access to the active workspace compute target.

Find your SSH command

Open the Terminal panel, then click the key icon on the active terminal tab. Meshia shows the two steps for that target: create a workspace key, then copy the command.


chmod 600 ~/Downloads/meshia_key.pem && ssh -i ~/Downloads/meshia_key.pem -p 23456 mesh@203.0.113.10

If you have not saved a workspace key yet, click Generate, then copy or download meshia_key.pem. Meshia stores only the public key and save timestamp, not the private PEM. The same saved PEM is installed across live compute for that workspace.

Connect from your terminal

If you downloaded the key, paste the command into your local terminal and hit enter. Meshia points it at ~/Downloads/meshia_key.pem and locks the PEM permissions before SSH starts. The first time, you'll be asked to confirm the host fingerprint. Type yes.

You're now in a shell on the selected compute target. Everything you do here is visible through the shared filesystem, but Meshia will not interrupt your terminal session.

What the parts mean

  • mesh@203.0.113.10. You connect as the sandboxed mesh user on the selected compute target.
  • -p 23456. The public port assigned to that compute target for this boot.
  • -i ~/Downloads/meshia_key.pem. The private key file you generated and downloaded for this workspace.

Tips

  • VS Code Remote SSH: Use the SSH command as a Remote SSH target in VS Code. You get your full editor connected to the pod's filesystem.
  • Port forwarding: Add -L 8080:localhost:8080 to the SSH command to forward a port. Useful for Jupyter notebooks or TensorBoard running on the pod.
  • Multiple sessions: You can have multiple SSH sessions open to the same compute target. They share the same workspace filesystem.
  • Session persistence: Your SSH connection stays alive as long as the pod is running. If compute stops, the connection drops; sessions can only resume when Meshia still has a retained workspace volume for that session.
← The workspaceAgent roles →