Cuttlefish by DigitalOcean is a mobile interface for coding agents running on DigitalOcean rather than on the phone itself. Its audience is developers and teams who want to start work, follow a session and respond when an agent needs a decision away from their desk. The distinction matters: this is access to a managed working environment, not a promise that an iPhone becomes a complete local development machine.
This First look uses the official App Store description. We have not run an agent through Cuttlefish, audited its isolation or measured responsiveness. The useful proposition is continuity between cloud-based work and mobile supervision, with costs and permissions that need deliberate setup.
Based on official store information. We have not tested this app hands-on.
What it does
The listing names Claude Code, Codex CLI, OpenCode and Hermes, plus the ability to run a LangGraph or CrewAI project from GitHub. It also describes choosing models from several providers. Those are alternatives within a session setup, not a claim that every agent and model supports identical tools or produces equivalent results. All sessions are presented in one list.
Setup begins by choosing an agent, model and sandbox size. The developer says an hourly price appears before creation. A practical first project would be a bounded task in a repository where mistakes are reversible: explain a failing check, propose a small change and inspect the resulting files. That is an evaluation suggestion, not a workflow we have performed.
The mobile controls include following streamed replies and tool calls, messaging the agent, stopping a turn and pausing or resuming a session. Files can be browsed, previewed and shared from the workspace. Checkpoints, rollback and session forks offer ways to revisit a state or explore another approach. A checkpoint still needs to be understood in relation to external actions that may already have happened.
Team sessions can be shared so participants see a live conversation, tool calls and results. The description shows who started a session and who joined. Teammates can approve or deny commands, including seeing the exact command, and notifications announce when input is needed or work finishes. These features support shared oversight; they do not establish that every teammate has the same authority or that an approval is technically correct.
Before you install
Permission rules can allow, ask about or deny tools and commands. The listing also names restricted networking, environment variables, scoped secrets, custom MCP servers and reusable skills. Treat those as configuration responsibilities. A small mobile screen is convenient for a clear decision, but a long or unfamiliar command may require reviewing more context before approval.
Action Gateway integrations include development and operational services. Connecting them broadens what an agent may be able to read or change. Scope access to the task, distinguish a proposed action from a completed one and inspect the relevant service when a result matters. Rollback in a coding session should not be assumed to reverse a message, ticket update or external deployment.
Logs and traces through Insights are listed for inspection. They can help explain what happened, while also potentially containing repository details or tool output. Review access and retention arrangements suitable for your team before putting sensitive work into a shared session. We have not audited how secrets are filtered or what an integration records.
Agent output remains something to evaluate. A completed notification is not proof that tests passed, a patch was reviewed or a production change is safe. Decide what completion means for your task and verify those conditions separately.
Price and access
The linked US App Store download is free. Using Cuttlefish requires a DigitalOcean account with access to Managed Agents, and the description says environment pricing is shown before creation. Free installation therefore does not imply free compute or model usage. Confirm the current service charges, account eligibility and supported iPhone requirements in the official purchasing and compatibility information before starting a session.
Our take
The strongest fit is a team that already understands its repositories, permissions and review process and wants to remain available for small decisions away from a laptop. Seeing the exact command and a shared session history can make mobile oversight more concrete than a generic completion alert. Whether it is comfortable for extended work needs direct evaluation.
Start with one low-risk project and a narrow permission set. Check what notifications arrive, whether you can inspect enough context and how the result moves into your normal review process. Keep a route back to a full development environment when the decision becomes complex.
Our take remains a source-based introduction. We have not verified supported integrations, sandbox behavior, billing accuracy or the quality of generated changes. Cuttlefish offers a documented way to supervise managed agents remotely; the responsibility for reviewing their work remains part of the workflow.
When inviting a teammate, agree who is responsible for approving changes. Shared visibility can reduce duplicated effort, but it can also create uncertainty if everyone assumes someone else checked a command. Use an explicit owner for a sensitive decision.
Sources
App icon from the official store listing.
