A conversation that never loads on mobile is the app layer failing, not your work — the session itself is fine on the host. That's the split I built CLIAnywhere around: the terminal session lives on your computer and persists there, and your phone connects into that same session over an encrypted connection. Nothing to reload, and if the connection drops you reconnect to the session still running. No public IP or port forwarding. Details: https://t.co/1Gi4b5btMd
Exacto, a Grok Build solo le falta eso — pero no tienes que esperar a que xAI lo agregue. Si Grok Build corre en la terminal de tu computadora, puedes tomar la capa remota por tu cuenta: construí CLIAnywhere para eso. La sesión queda viva en tu máquina y tu celular se conecta a esa misma sesión por una conexión cifrada, sin IP pública ni port forwarding. Lo que corres en esa terminal — Grok Build, Claude Code, Codex — queda accesible desde el cel. Detalles: https://t.co/1Gi4b5btMd
Deleting the pairing to get your own conversations back is a wild fix to have to live with. The pairing is the fragile part — I built CLIAnywhere without it: the terminal session runs on your computer and stays there, and your phone connects into that same session over an encrypted connection whenever you open it. Nothing to re-pair, and a dropped connection just means reconnecting to the session that's still running. No public IP or port forwarding. Details: https://t.co/1Gi4b5btMd
That list — sessions not loading, messages stuck on Sending, finished tasks still showing Thinking, flaky pairing — is what you get when the session lives inside the app's remote layer. I built CLIAnywhere so the session lives on your own computer instead: it persists there, and your phone is just a window into it over an encrypted connection. A drop means reconnecting to the same session, not reloading it. No public IP or port forwarding. Details: https://t.co/1Gi4b5btMd
That silent failure is the worst part — pairing either works or tells you nothing. It's why I moved the connection out of the app-pairing model entirely with CLIAnywhere: the terminal session runs on your computer and persists there, and your phone connects to that session over an encrypted connection. No pairing dance to break, no public IP or port forwarding, and when the connection drops you reconnect to the same session instead of starting over. Details: https://t.co/1Gi4b5btMd
Oui — et ça ne dépend pas de l'outil que vous testez. Je développe CLIAnywhere : la session terminal reste active sur votre propre machine, et votre téléphone s'y connecte via une connexion chiffrée. Vous pouvez donc lancer et surveiller Claude Code (ou Codex, ou un simple shell) depuis votre téléphone, sans IP publique ni redirection de port. La session survit aux déconnexions : vous vous reconnectez à la même session, toujours en cours. Détails : https://t.co/1Gi4b5btMd
That settings detour is what happens when remote control is bolted onto each app separately. There's a simpler layer to attach it at: the terminal session itself. That's how I built CLIAnywhere — the session stays alive on your own machine, and your phone or browser connects into it over an encrypted connection. No slash command to wait for, no settings to hunt through; if the agent runs in a terminal, it's reachable. No public IP or port forwarding either. Details: https://t.co/1Gi4b5btMd
The disconnects don't have to hurt. When the session lives inside the remote connection, a drop takes the agent down with it. I built CLIAnywhere the other way round: the terminal session runs on your own computer and persists there, so if the phone connection drops, you reconnect into the same session — still running, nothing lost. It works with whatever runs in that terminal, over an encrypted connection, no public IP or port forwarding. Details: https://t.co/1Gi4b5aVWF
O Claude travar no remote control geralmente é a camada remota falhando, não o agente em si. Foi por isso que construí o CLIAnywhere na camada do terminal: a sessão fica viva no seu próprio computador, e o celular entra nessa mesma sessão por uma conexão criptografada. Como o Claude Code roda num terminal normal, ele funciona igual ao uso local — sem as limitações e travamentos do modo remote control. Sem IP público nem port forwarding para configurar. Detalhes: https://t.co/1Gi4b5btMd
You're not using it wrong — that queueing is how their mobile remote control handles follow-ups. It's why I built CLIAnywhere at the terminal layer instead: the session lives on your Mac and persists there, and your phone is just a window into that same session, so typing from the phone behaves exactly like typing at the desk — follow-ups go straight in, no separate mobile queue. The connection is encrypted, no public IP or port forwarding to manage. Details: https://t.co/1Gi4b5btMd
Before you leave OpenCode over this — the remote part doesn't have to come from the harness. I built CLIAnywhere so the terminal session lives on your own computer; your phone connects into that same session over an encrypted connection, no public IP or port forwarding needed. OpenCode runs in a terminal, so the session you already have is reachable from your phone as-is — no Telegram workaround, no switching tools just for remote access. Details: https://t.co/1Gi4b5btMd
This is exactly the failure mode I built CLIAnywhere to remove. When the terminal session lives on the PC itself instead of inside your SSH connection, a dropped connection doesn't take the work with it — you reconnect from your phone or laptop into the same session, still running, and pick up where you left off. The connection is encrypted, P2P with relay fallback, and there's no public IP or port forwarding to manage. Hope the images turn out to be saved. Details: https://t.co/1Gi4b5btMd
That 'absolutely horrible remote control implementation' is the tax you pay for letting each harness rebuild the remote layer itself. I took a different route with CLIAnywhere: the terminal session lives on your own computer and persists there, and your phone connects into that session through an encrypted relay. Claude Code, Codex CLI, whatever is running in that terminal is equally reachable, and the harness's own remote control quality stops mattering. It's here: https://t.co/1Gi4b5btMd
That ability doesn't have to wait for the iOS app to ship it. If Codex runs in a terminal on that remote computer, the phone side can be handled at the terminal layer today: I built CLIAnywhere so the session stays alive on the computer itself, and your phone or browser connects into that same session through an encrypted relay — no public IP or port forwarding to set up. It's here if you want a look: https://t.co/1Gi4b5aVWF
Your wishlist is exactly the problem I built CLIAnywhere for — full disclosure, it's a product rather than a DIY recipe. The agent runs on the Mac Studio itself and keeps the session alive there; your iPhone or iPad connects to that same session over an encrypted connection, P2P when possible, relay only as fallback. Nothing on the Studio is exposed to the public internet, no port forwarding or DDNS, and the MacBook and Mini aren't in the path at all. Details: https://t.co/1Gi4b5btMd