Synk — Remote Session Control
Control your AI coding sessions from anywhere — mobile, tablet, or web browser.
What is Synk?
Synk is the remote command deck for ekkOS. It lets you spawn, monitor, and interact with AI coding sessions running on your development machines — from your phone, tablet, or any browser.
iOS App
TestFlight & App Store
Web Dashboard
synk.ekkos.dev
CLI Daemon
Background service
Key Features
Remote Session Spawning
Start new Claude, Codex, or Gemini sessions on any connected machine — pick the model, context window, permission mode, and working directory from your phone.
Live Session Monitoring
Watch messages stream in real time. See tool calls, permission requests, token usage, and cost tracking as your agent works.
Permission Approval
Approve or deny tool permissions from your device. Review file edits, bash commands, and destructive actions before they execute.
Multi-Machine Management
Connect multiple development machines. Switch between them, view active sessions across all machines, and manage the daemon lifecycle remotely.
Model & Context Window Selection
Choose between Opus, Sonnet, and Haiku models with 200K or 1M context windows. Each combination shows output token limits so you know what you're getting.
End-to-End Encryption
All session data is encrypted with TweetNaCl before leaving your device. The server never sees your code or conversation content.
Pulse Mode
When launching a session with Pulse routing enabled, your AI traffic flows through proxy.ekkos.dev — unlocking the full ekkOS memory layer:
- Automatic pattern injection from past sessions
- Directive enforcement (MUST/NEVER/PREFER/AVOID)
- Auto-forging of bug fixes and learned solutions
- Schema injection to prevent database column errors
- Context eviction and replay at 90% capacity (seamless)
You can also use Direct routing to bypass the proxy and connect straight to the provider's API using your own credentials.
Setup
Step 1: Install the ekkOS CLI
npm i -g @ekkos/cli
Step 2: Authenticate
ekkos auth login
This generates a keypair and links your machine to your ekkOS account. A QR code will appear — scan it with the Synk app to pair.
Step 3: Start the Daemon
ekkos daemon start
The daemon runs in the background, keeping a persistent WebSocket connection to the Synk server. It receives spawn requests, manages sessions, and handles auto-updates when the CLI version changes.
Step 4: Install the Synk App
Download the Synk app from the App Store (iOS) or use the web dashboard at synk.ekkos.dev. Sign in with your ekkOS account and your connected machines will appear automatically.
Daemon Management
The daemon is the bridge between your machine and the Synk app. Common commands:
ekkos daemon startStart the background daemonekkos daemon stopGraceful shutdownekkos daemon statusCheck if daemon is runningekkos daemon listShow active sessionsekkos daemon logsTail daemon log outputekkos daemon installAuto-start daemon on bootModel & Context Window Options
When spawning a new session from Synk, you can select from these Claude model configurations:
| Model | Context | Max Output |
|---|---|---|
| Auto Route | 200K | 16K |
| Opus 4.5 | 200K | 16K |
| Opus 4.6 | 200K | 16K |
| Opus 4.6 | 1M | 64K |
| Sonnet 4.5 | 200K | 16K |
| Sonnet 4.6 | 200K | 16K |
| Sonnet 4.6 | 1M | 64K |
| Haiku 4.5 | 200K | 16K |
The 1M context window is available on Opus 4.6 and Sonnet 4.6 at standard GA pricing. Legacy models (4.5) have long-context premium rates when exceeding 200K.
How It Works
Daemon connects
The daemon on your machine maintains a persistent encrypted WebSocket to the Synk server. Your machine appears in the Synk app as soon as the daemon starts.
You spawn a session
From the Synk app, pick a machine, directory, model, and permission mode. The app sends an encrypted RPC to the daemon, which spawns the ekkOS CLI process.
Messages stream both ways
You type messages in the app, the daemon relays them to the CLI process. Responses stream back in real time — including tool calls and permission requests.
Everything is encrypted
Session content is encrypted with TweetNaCl on your device before transmission. The Synk server relays encrypted blobs — it never sees your code.
Troubleshooting
Machine not appearing in app?
- • Verify daemon is running:
ekkos daemon status - • Check auth status:
ekkos auth status - • View daemon logs:
ekkos daemon logs
Session spawn failing?
- • Ensure the directory exists on the target machine
- • Check the daemon has write access to the directory
- • Run
ekkos doctorto diagnose orphaned processes
Session disconnected?
- • Sessions auto-reconnect when the daemon comes back online
- • Check your network connection on both ends
- • Restart the daemon:
ekkos daemon stop && ekkos daemon start