SSH connectivity

​

Overview

Claworc establishes a secure connection to each agent instance using SSH. This connection carries all traffic to the instance — browser access, terminal sessions, file operations — without requiring any ports to be opened or configured on the instance side. From a user’s perspective, the connection is automatic and invisible: click Browser or Terminal and you’re in. Under the hood, Claworc authenticates using a single global ED25519 key pair, monitors connection health continuously, and reconnects automatically if anything drops.

---

​

SSH key management

​

Global key pair

Claworc generates one ED25519 key pair on first run, stored in the data directory (/app/data/ssh_key and /app/data/ssh_key.pub). The same public key is uploaded to every agent’s authorized_keys when a connection is established.

​

Key upload on connect

Before establishing an SSH connection, Claworc uses the orchestrator (via kubectl exec or docker exec) to write the public key to the agent’s /root/.ssh/authorized_keys. This ensures connectivity even after a container restart that clears the filesystem.

---

​

Connection States

On the instance details tab you can check the SSH connection status:

---

​

Health monitoring

Claworc monitors connections at three layers: If any layer detects a failure, automatic reconnection is triggered.

---

​

SSH key rotation

Rotate the global key pair from Settings → SSH Keys → Rotate key. The rotation process maintains live connectivity throughout — both old and new keys work temporarily while the switch is made.