Ownership
Your agent. Your server. Your rules.
A ready-made agent workspace saves setup time. Before you give it your repository, decide who should hold the machine, the credentials and the way out. Mobile SSH lets you bring your own host — from the box under your desk to a VM in your cloud account.
Choose the host. Check the model route.
SSH to the host you choose
- Your physical machineHome, office or your own server room
- Your cloud-account VMYou administer the guest; the provider runs the hardware
Files, tools and the agent process live on the selected host
If using a cloud model: prompts and selected context leave the host
The invitation is appealing: open a workspace and find Codex, Claude Code or Gemini CLI already waiting. No machine to prepare, no packages to install. Connect a repository, describe the task, and let a cloud VM do the work. For an experiment or a disposable project, that convenience can be exactly what you want.
Then the experiment becomes your daily workspace. Private code arrives. So do test fixtures, internal documentation and whatever credentials you supply. Before that handover becomes routine, ask a more durable question: who controls the place where this work lives?
A ready-made workspace has an operator
In a provider-managed agent environment, someone else operates the execution host. Your repository may be cloned there, data uploaded, and permissions granted to reach other systems. Isolation, administrator access, retention and export options depend on the service. Preinstalled tools tell you how quickly you can start; they tell you little about those arrangements.
That is a choice you can make deliberately. Managed environments can reduce maintenance and provide useful isolation. Read what happens to workspace disks, transcripts, snapshots and credentials, including after a session ends or an account closes. You do not have to assume bad intentions to want clear answers about your private work.
Keep the keys. Keep a backup. Keep the ability to leave.
Three places to run the same agent
A VM in your own cloud account gives you another arrangement. You choose the guest operating system, install the tools, issue access and manage the instance's lifecycle. The cloud company still operates the physical infrastructure. Calling it your server describes administrative control, not ownership of the underlying hardware. [1]
A physical machine you own goes further: you choose the hardware and decide where it sits. An existing desktop, a small home server or an office machine can hold the workspace. You also inherit the practical jobs: power, connectivity, repairs, patches and recovery. Ownership gives you decisions to make; it does not make them for you.
| Decision | Managed agent workspace | VM in your cloud account | Hardware you own |
|---|---|---|---|
| Physical hardware | Service or infrastructure provider | Cloud provider | You own the machine |
| Administrative control | Defined by the service | You administer the guest OS | You administer the host |
| Workspace and storage | Service-managed disks and retention | Volumes and lifecycle you configure | Storage you choose and maintain |
| Credentials and network policy | Service controls plus permissions you grant | Your OS, identity and network configuration | Your OS, identity and network configuration |
| Backups and the way out | Check export and deletion options | Manage copies outside the instance | Manage copies outside the machine |
| Operational work | Provider runs the environment; you configure its use | You maintain the guest; provider maintains infrastructure | You maintain hardware, OS and connectivity |
Bring your server to your phone
Mobile SSH works with either user-operated option. Connect to a reachable SSH host on your local network, through a network path you configure, or in your cloud account. Ordinary SSH sessions do not require a Mobile SSH-operated session relay or a Mobile SSH account. You choose the destination and provide its credentials.
Install the agent you want on that host. Open its working directory, run Codex, Claude Code or Gemini CLI, and use the terminal you already understand. You can keep a session under tmux, herdr or Zellij and return to it from your phone while the host and process remain running. The work belongs to that environment; changing your phone does not require moving the repository.
That leaves useful choices in your hands. Keep sensitive fixtures on a local machine. Use a cloud VM when its resources suit the task. Change agents without rebuilding the mobile workflow. Mobile SSH provides terminal access, SFTP and tunnels; it does not require you to rent a particular agent workspace.
Your server and your model are separate choices
This distinction matters most when discussing private data. Running an agent on hardware you own does not necessarily run its model there. A cloud-backed agent can send prompts, selected repository context and tool results to the model service. The agent process and working tree can stay on your server while inference happens elsewhere. [2] [3]
SSH encrypts the connection between your phone and its endpoint. It does not prevent software on the host from reading permitted files or making its own network requests. Decide which model service the agent uses, what it may read, and which tools or integrations may send data out. Check the policies for your actual account and configuration.
If the work requires local inference, choose a compatible agent and model setup and verify its network behavior. Do not infer that guarantee from the word local on an installer. Mobile SSH's optional analytics and plugin downloads also have their own data flows; the app's privacy settings and policy explain them.
Make control something you can exercise
A root password is only the beginning. Practical control means you can restrict access, recover from a mistake, inspect what changed and move the workspace without asking an agent platform to preserve it for you. Give those abilities the same attention as the choice of model.
Six ways to keep control
- Give credentials a small job
Use separate, revocable credentials for the workspace. Grant only the repository and service permissions the task needs.
- Limit the workspace
Run the agent as a dedicated, unprivileged user where practical. Keep unrelated private files and production secrets outside its reach.
- Verify the SSH destination
Check unfamiliar host fingerprints through a trusted channel. Investigate changed keys before replacing a saved identity.
- Keep an independent backup
Keep encrypted copies under accounts you control, separate from the working host. Test a restore, including uncommitted work you need to preserve.
- Review what leaves the host
Check model endpoints, plugins, external tools and telemetry settings. Share the minimum context needed and review the resulting changes.
- Practice moving
Restore the workspace on another host, reconnect and run its tests. The ability to leave should be something you have tried.
None of this makes a home server automatically safer than a managed service. A neglected machine with broad credentials can be a poor place for private data. Choose the level of responsibility you can maintain. The advantage is being able to make that choice, inspect it, and change it when your needs change.
Own the machine when you can. Keep control of the workspace wherever it runs.
The next time a ready-made agent environment asks for your repository, take a moment before connecting it. Decide where the files should live, who should administer that host, and how you will take the work with you. Then pick up your phone. Mobile SSH can meet you at the server you chose.