The Deska blog

Monitoring OpenCode From Your Phone

Learn how to effectively manage long-running AI tasks by monitoring OpenCode from your phone using secure remote access and local-first developer tools.

· 10 min read

As AI coding agents become increasingly autonomous, developers are shifting from manual line by line coding to orchestrating complex, long running tasks. This shift creates a new challenge for the modern workflow, specifically the need for monitoring OpenCode from your phone while away from your primary workstation. OpenCode, an open source agent capable of executing commands and modifying files, often requires supervision during deep refactors or large migrations. Checking the status of these autonomous sessions ensures that an agent has not hit a logical loop or exhausted its context window without making progress.

The Evolution of Agentic Workflows

Traditional development tools are built for active input. You sit at a desk, you write code, and you save. With agents like OpenCode, the developer acts more like a project manager or an architect. You define a goal, provide the context, and the agent iterates. This process can take minutes or even hours depending on the complexity of the codebase.

The ability to step away from the desk without losing visibility into these processes is a significant productivity multiplier. It allows for a more flexible schedule while maintaining the integrity of the development cycle. Mobile monitoring is not about writing entire applications on a small screen. It is about verification, status checks, and intervention when an agent requires human clarification to proceed.

Current Approaches to Remote Development Monitoring

There are several ways to keep track of your terminal and agent sessions from a mobile device. Each method involves different trade-offs regarding security, latency, and ease of setup.

SSH and Terminal Emulators

The most traditional method is using an SSH client on your phone to connect to your development machine. You can run OpenCode inside a terminal multiplexer like tmux or screen. This allows you to detach from a session and reattach later from a different device.

  • Pros: Low overhead, works on almost any network, and requires no proprietary software.
  • Cons: Visualizing complex outputs or file changes on a small terminal screen is difficult. Touch interactions are often clunky in a CLI environment.

Remote Desktop and Screen Sharing

Using protocols like VNC or RDP allows you to see the entire desktop environment. You can see the IDE, the terminal, and the browser exactly as they appear on your monitor.

  • Pros: Full visual parity with your desktop setup.
  • Cons: High bandwidth requirements and significant latency. Navigating a high resolution desktop on a phone screen involves constant zooming and panning, which is frustrating for quick status checks.

Integrated Mobile Ecosystems

Some modern developer tools provide a dedicated mobile companion app. These apps are designed to translate desktop interfaces into mobile friendly views. Instead of streaming raw pixels, they sync the state of the workspace. This is where tools like Deska focus their utility, providing a bridge between a local-first environment and mobile accessibility.

Security Considerations for Remote Access

When you enable remote access to a machine running an agent like OpenCode, security is the primary concern. OpenCode has the authority to run commands and modify your filesystem. Exposing these capabilities to the public internet creates a massive attack surface.

Standard practices involve using a VPN or a secure relay service. You should avoid exposing raw ports on your router. A secure relay allows your mobile device and your desktop to pair directly. This setup ensures that your code and sessions stay on your machine rather than being stored on a third party server. Privacy is paramount in a local-first architecture, where the developer retains full ownership of the data.

Leveraging Deska for Agent Monitoring

Deska is a free desktop application available for Mac, Windows, and Linux. It provides an infinite canvas where you can place various panels, such as terminals, code editors, and browsers. One of the core strengths of this workspace is its ability to run coding agents like OpenCode side by side.

The Deska mobile app is specifically built for the use case of monitoring and continuing work. It connects to your desktop through a secure relay that requires direct pairing. Because no ports are exposed, it maintains a high security posture while providing a fluid interface for checking on your agents.

FeatureSSH/TmuxRemote DesktopDeska Mobile
InterfaceText onlyFull Pixel StreamNative Mobile UI
SecurityManual ConfigVPN RequiredSecure Relay
Resource UsageVery LowVery HighModerate
InteractionKeyboard heavyMouse emulationTouch optimized

By using the canvas layout, you can zoom out to see all your active agents at once on your desktop, and then use the mobile app to focus on specific threads when you are on the move.

Managing Agent State and Feedback

Monitoring OpenCode from your phone is most effective when you can provide feedback to the agent. Sometimes an agent might get stuck because it is unsure which library version to use or which architectural pattern to follow.

  1. Check Logs: View the terminal output to see the latest actions taken by the agent.
  2. Review Code: Use a mobile friendly editor or panel to see the diffs generated by the agent.
  3. Voice Commands: Use an assistant like Ask Deska to interact with your workspace via voice. You can ask the assistant to check the status of a specific session or run a new command.
  4. Pause/Resume: Stop an agent if it behaves unexpectedly to prevent it from consuming unnecessary API credits or making incorrect changes.

This level of control ensures that even though you are not at your desk, you are still in command of the development process. You can learn more about managing these sessions in the agent threads documentation.

FAQ

How to monitor OpenCode from your phone safely?

The safest way is to use an application that utilizes a secure relay for direct device pairing. This avoids exposing ports like 22 or 3389 to the internet. Always ensure that the connection is encrypted and that the tool follows a local-first philosophy where your files are never uploaded to a cloud provider.

Can I run OpenCode directly on a mobile device?

Running OpenCode directly on a phone is generally not recommended due to the high computational requirements and the need for a full development environment with compilers and runtimes. The best approach is to run the agent on a desktop or server and monitor the output remotely.

What is the best app for remote terminal monitoring?

For purely text based needs, apps like Termius or a simple SSH client with tmux are excellent. However, if you need to see code editors, browser previews, and multiple agent panels simultaneously, a specialized workspace tool like Deska with its companion mobile app provides a more comprehensive experience.

Get Started with Deska

If you are looking for a way to organize your AI agents and monitor them from anywhere, you can start by setting up your workspace on your desktop. Deska allows you to bring your own API keys for a lifetime tier, or you can use managed inference if you prefer a subscription model. The workspace itself remains free to use.

Download the desktop app for your operating system at /download and pair it with the mobile app to start monitoring your OpenCode sessions today. For more information on setting up your first workspace, visit the getting started guide.

💡 Ideas+🐛 BugsSuggest a feature or report a bug