The folder shuffle is not portability
An agent is rarely one file. It can include instructions, skills, playbooks, routing metadata, evaluation contracts, and the experience it has been allowed to keep. Copying a folder to Drive, sending a ZIP through email, or carrying it on a USB stick moves bytes, but it does not tell the next computer which copy is authoritative or whether anything was lost along the way.
Agent Cloud gives an owned package a private retrieval path. Save it once under your Agentlas account, then restore the verified package on another supported computer after installing Agentlas OS and signing in. The package arrives with its identity and version intact instead of returning as an anonymous folder from an old attachment.
Keep the agent, skills, and experience connected
The agent package can carry its runtime adapters, skills, playbooks, and governed operating instructions. Agentlas records a reproducible package hash, so a restored execution copy can be checked against the Cloud source that produced it.
Experience assets have their own versioned exchange. They stay bound to the base agent release rather than being mixed into a loose archive. This is the difference between synchronizing an owned asset and merely copying whatever happened to be in a folder that day.
Routing replaces folder hunting
Retrieval should begin with the job, not with a filename. The /hep-cloud route searches only the signed-in owner's Agent Cloud packages. It does not silently switch to a public Hub agent or a random local card. Agentlas can match the request to an agent you own, restore the package when the current computer needs it, and pass the resolved local copy to the connected runtime.
That makes the same saved analyst, writer, researcher, or operating team available from the next supported host without forcing you to remember which drive contains the newest ZIP.
What does not move
Agent Cloud stores and retrieves the package. It is not a hosted LLM that performs the work for you, and it does not copy the authority of one computer onto another. API keys, local files, browser sessions, operating-system permissions, and provider access remain machine-specific.
On the second computer, you reconnect the model and tools you choose, review the permissions, and run the restored agent locally. The portable part is the owned operating asset; the execution boundary still belongs to the computer in front of you.
- Agent package and versioned identity: retrievable from Agent Cloud.
- Skills, playbooks, and governed experience: remain connected to the asset.
- API keys and local files: stay on each computer.
- Routing: searches the signed-in owner's Cloud scope through /hep-cloud.
Move once, retrieve when needed
The practical workflow is short: build or import the agent, save it to private Agent Cloud, install Agentlas OS on the next supported computer, sign in, and retrieve it with /hep-cloud. Use Drive, USB, and email for documents when they are the right tools. Do not make them the version-control system for the agents that contain your experience.
