Yep Anywhere runs on your development machine. Remote access changes how a browser reaches that server; it does not move provider processes or session storage into a hosted account.
Any controller, any host
Anything with a modern web browser can be the control surface—for example, another computer, a tablet, or a phone. The host computer keeps the code, provider credentials, sessions, and agent processes.
Claude Remote Control and Codex Remote Control provide useful first-party paths inside their respective products. Yep Anywhere is provider-neutral and browser-first: the same interface supervises Claude Code and Codex across the machines you control, without requiring a native controller app or a particular controller operating system.
Choose a connection method
| Method | Best for | Trade-off |
|---|---|---|
| Direct LAN/private network | Trusted local networks or an existing Tailscale setup | You manage reachability |
| Public relay | Fast access from any browser without port forwarding | Connection metadata reaches the relay; application traffic is end-to-end encrypted |
| Self-hosted relay/reverse proxy | Operators who want full infrastructure control | More deployment and security responsibility |
Public relay
This is the no-network-setup path. There is no manual device pairing, VPN, or port forwarding: install Yep Anywhere, choose a username and strong password, enable the relay, then sign in from any browser.
In Settings → Remote Access, choose a username and a strong password, then enable the relay. For a headless setup:
yepanywhere --setup-remote-access --username myserver --password "use-a-long-unique-password"Connect at yepanywhere.com/remote. The browser and server authenticate with SRP and encrypt application messages before they cross the relay. The relay sees connection metadata and encrypted traffic, not the session contents or password.
Public read-only sharing is opt-in because it uses a different trust boundary. The current public-share relay path is readable by a relay operator and must not be described as equivalent to an end-to-end encrypted Remote Access session. See Security and privacy.
Direct access
For a trusted LAN or private network, open the server using the host’s reachable address and configured port. Tailscale is a common way to give the host and phone a private address without exposing a public port.
Do not publish an unauthenticated local listener directly to the internet. Terminate HTTPS and require authentication when using your own public reverse proxy.
Self-hosted infrastructure
You can run your own relay or place Yep Anywhere behind an HTTPS reverse proxy. This is an operator workflow: you are responsible for certificates, authentication, updates, origin restrictions, logs, and abuse controls.
The public relay design documents the protocol and deployment components for self-hosting.
Why no native mobile app yet?
The responsive browser client already supports the complete Yep Anywhere workflow on phones and tablets, including approvals, diffs, uploads, voice input, notifications, session history, and new sessions. Shipping a native app that only wraps this interface would add another installation and release path without adding enough user value.
The Android app is in development as a real companion, with iOS planned afterward. More reliable background notifications, deep links, trusted packaged client code, and a multi-server inbox are the intended native advantages. Neither app is published. Use the browser client today; no public APK or app-store listing is available.
Connection troubleshooting
Check these in order:
- Confirm the Yep Anywhere server is running locally.
- Open the local dashboard on the host.
- Verify the username and exact remote URL.
- Check Settings → Remote Access for relay status.
- Look at the server log for reconnect or authentication errors.
Continue with Troubleshooting for log locations and safe issue-report evidence.