Remotes
A remote is a CLI instance connected to your simse cloud account. Once connected, the CLI syncs sessions and memory with the cloud, and you can access it from the web app at app.simse.dev.
Connecting a remote
Log in from your CLI to register it as a remote:
simse login
This opens a browser window to authenticate. Once you confirm, the CLI is linked to your account and appears in the web app under Settings > Remotes.
Each machine you log in from registers as a separate remote.
Remote status
Every remote reports its status to the cloud:
- Online — The CLI is running and reachable. You can interact with it from the web app.
- Offline — The CLI is not running or the machine is disconnected. Synced sessions and memory are still accessible, but you cannot send commands to the remote.
The dashboard shows the current status of all your remotes at a glance.
Managing remotes
Open Settings > Remotes in the web app to see all connected CLI instances. From this page you can:
- View details — See the remote name, machine hostname, last seen time, and connection status.
- Rename — Give a remote a friendly name to tell your machines apart.
- Disconnect — Temporarily stop syncing without removing the remote. Reconnect later with
simse login.
- Remove — Permanently delete a remote from your account. The CLI on that machine will need to run
simse login again to reconnect.
Use cases
- Access your dev machine from anywhere — Leave the CLI running on your workstation, then open the web app on a tablet or another computer to pick up where you left off.
- Sync across devices — Sessions and memory sync automatically between all connected remotes. Start work on one machine, continue on another.
- Team visibility — Team members can see which remotes are online and coordinate shared environments.
Troubleshooting
If a remote shows as offline unexpectedly:
- Confirm the CLI is still running on that machine.
- Check the machine's network connection.
- Run
simse status on the CLI to verify the connection to the cloud.
- If the remote was removed, run
simse login again to re-register it.