Frontmatter:
title: Remote Environments
description: Run Kepler Tasks on a remote machine via SSH or inside a Windows Subsystem for Linux (WSL) environment, or expose Kepler for remote access using the built-in server.
taxonomy:
category: kepler
Purpose: Cover two distinct remote scenarios: (1) running Tasks and agents on a remote machine or WSL environment, and (2) using Kepler's Remote Access server to access the app from another device.
Sections to include:
SSH (run Tasks on a remote machine)
When to use: the repo is large, the build is slow, or the work needs more compute than the local machine has.
Prerequisites: SSH access to the remote machine.
Step-by-step: how to connect a remote machine in Kepler.
What runs remotely (Tasks, worktrees, agents) vs. what stays in Kepler's local UI.
Troubleshooting: common SSH connection failures.
WSL (Windows Subsystem for Linux)
When to use: developers on Windows who need a Linux environment for agents or builds.
Prerequisites: WSL installed; confirm version requirements.
Step-by-step: how to connect a WSL environment the same way as a remote machine.
Troubleshooting: WSL not detected, version conflicts.
Remote Access (access Kepler from another device)
This is a different feature from SSH/WSL. Remote Access starts a local server inside Kepler so you can access the app from another device on your network or via a tunnel.
Settings (Settings → Remote Access):
Port: the port Kepler's server listens on. Default: 3000.
Host: the host address. Default: 0.0.0.0.
URL Override: if set, used in the QR code instead of the auto-detected address. Example: https://my-tunnel.ngrok.io.
How to start Remote Access: click "Start" in Settings → Remote Access.
The QR code use case: scan to connect from a mobile device or secondary machine.
Using an ngrok tunnel to expose Kepler outside the local network.
Security considerations: who can connect, whether any authentication is required.
Frontmatter:
title: Remote Environments
description: Run Kepler Tasks on a remote machine via SSH or inside a Windows Subsystem for Linux (WSL) environment, or expose Kepler for remote access using the built-in server.
taxonomy:
category: kepler
Purpose: Cover two distinct remote scenarios: (1) running Tasks and agents on a remote machine or WSL environment, and (2) using Kepler's Remote Access server to access the app from another device.
Sections to include:
SSH (run Tasks on a remote machine)
When to use: the repo is large, the build is slow, or the work needs more compute than the local machine has.
Prerequisites: SSH access to the remote machine.
Step-by-step: how to connect a remote machine in Kepler.
What runs remotely (Tasks, worktrees, agents) vs. what stays in Kepler's local UI.
Troubleshooting: common SSH connection failures.
WSL (Windows Subsystem for Linux)
When to use: developers on Windows who need a Linux environment for agents or builds.
Prerequisites: WSL installed; confirm version requirements.
Step-by-step: how to connect a WSL environment the same way as a remote machine.
Troubleshooting: WSL not detected, version conflicts.
Remote Access (access Kepler from another device)
This is a different feature from SSH/WSL. Remote Access starts a local server inside Kepler so you can access the app from another device on your network or via a tunnel.
Settings (Settings → Remote Access):
Port: the port Kepler's server listens on. Default: 3000.
Host: the host address. Default: 0.0.0.0.
URL Override: if set, used in the QR code instead of the auto-detected address. Example: https://my-tunnel.ngrok.io.
How to start Remote Access: click "Start" in Settings → Remote Access.
The QR code use case: scan to connect from a mobile device or secondary machine.
Using an ngrok tunnel to expose Kepler outside the local network.
Security considerations: who can connect, whether any authentication is required.