You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/durable-sessions.mdx
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Keep your remote SSH shell sessions alive through network changes, computer slee
16
16
Durable sessions are designed for **remote SSH connections only**. Local terminals and WSL connections use standard sessions, as they're not affected by network interruptions and remain active as long as Wave is running.
17
17
:::
18
18
19
-
Durable sessions protect your terminal state when working with remote SSH connections. Unlike standard SSH sessions that terminate when the connection drops, durable sessions maintain your:
19
+
Durable sessions protect your terminal state when working with remote SSH connections, similar to tmux or screen but built directly into Wave. Unlike standard SSH sessions that terminate when the connection drops, durable sessions maintain your:
20
20
21
21
-**Shell state** - Current directory, environment variables, and shell history
22
22
-**Running programs** - Background jobs and long-running commands continue executing
@@ -194,16 +194,14 @@ The session was terminated on the remote server, possibly due to:
194
194
### Session Won't Reconnect
195
195
Verify that:
196
196
- Your SSH connection to the server is working (check the connection status)
197
-
- The remote server can reach Wave's connection manager
198
197
- The job manager process is still running on the remote server
199
198
200
-
**Solution**: Right-click terminal → Advanced → Force Restart Controller
199
+
**Try**: Right-click terminal → Advanced → Force Restart Controller
201
200
202
201
### "Failed to Start" Error
203
-
The job manager couldn't initialize on the remote server. Check:
204
-
- Remote server has sufficient resources
205
-
- Required directories and permissions are available
206
-
- No conflicting processes using the same socket
202
+
The job manager couldn't initialize on the remote server. Check the error message for specific details.
203
+
204
+
**Try**: Restart the session. If the issue persists, file a bug report with the error details.
207
205
208
206
:::info Technical Details
209
207
Durable sessions use Unix domain sockets on the remote server to maintain persistent connections between the shell and Wave's job manager. The job manager process runs independently and survives SSH disconnections.
@@ -212,6 +210,7 @@ Durable sessions use Unix domain sockets on the remote server to maintain persis
212
210
## Privacy & Security
213
211
214
212
- Durable sessions run entirely on your remote servers
215
-
- No session data is transmitted through Wave's cloud services
216
-
- Job managers use authentication tokens to prevent unauthorized access
213
+
- All data is transmitted over SSH between your local Wave instance and the remote machine
214
+
- No open ports on the remote machine - communication happens through your existing SSH connection
215
+
- When disconnected, output is buffered locally on the remote machine until you reconnect
217
216
- Sessions are isolated per user and use your remote user's permissions
0 commit comments