An Agent needs somewhere to do the work
AI chat is easy to understand: you send a message and receive an answer. Agent work is different. An Agent may need to read a document, create several files, run a tool, revise an output, ask you one question, and then package the result into something useful.
That work needs an environment — a place for sessions, files, tools, and artifacts to live while the task is running and after you come back.
On Mac, Lumo uses the environment on your own computer. But what happens when you only have an iPhone or iPad with you? Lumo Cloud Agent provides a managed cloud workspace so the Agent can work without requiring your Mac to stay online.
What "cloud workspace" means
When you start Cloud Agent, Lumo prepares a remote Agent runtime associated with your account. The mobile app connects to it securely over HTTPS and uses the same conversation model you already know: sessions, streaming responses, tool activity, questions, and artifacts.
Inside that managed workspace, the Agent can:
- •Work with files created for the task.
- •Use supported tools to read, write, edit, and organize material.
- •Run multi-step Creator Skills included with Lumo.
- •Extract text from PDFs when a workflow needs source material.
- •Create structured artifacts such as content calendars, tables, HTML pages, and diagrams.
- •Keep session history and generated outputs available when the runtime wakes again.
The cloud workspace is not a copy of your Mac, and it does not automatically sync every file from your computer. It is an independent place for tasks you choose to run in Cloud Agent.
Start in three steps
- 1.Sign in to Lumo on iPhone or iPad with an eligible Pro or Max account.
- 2.Choose Lumo Cloud Agent from the connection screen. No Mac and no QR code are required.
- 3.Open a session and describe the outcome you need. Watch the Agent work, answer questions when needed, and open the resulting artifacts in the app.
If you have used Lumo by connecting to a Mac, the interaction will feel familiar. The important difference is where the work runs: Cloud Agent uses the managed cloud workspace instead of a computer on your local network.
Built for work that takes more than one prompt
Cloud Agent is most useful when the request has several connected steps. For example:
Turn research into a publishing plan
Give the Agent a topic, audience, and set of constraints. It can develop angles, organize the strongest ideas, draft a platform mix, and turn the result into a content calendar you can inspect as a structured artifact.
Turn a PDF into creator-ready material
Add source material that you are comfortable processing in the cloud. The Agent can extract the text, summarize the useful sections, identify claims that need checking, and develop the result into a brief, script, or comparison table.
Build and preview a lightweight web page
Ask for a launch page, resource page, or campaign draft. The Agent can create the HTML in its workspace and return an artifact that you can preview from the mobile app.
Package a repeatable workflow
Creator Skills give the Agent a more specific process to follow. That can mean planning a content calendar, preparing a metadata pack, proofreading subtitles, or turning one source into platform-specific versions.
In each case, the Agent is not only composing a response. It is moving through a workflow and leaving behind an output you can use.
Sessions and artifacts survive idle time
A cloud runtime does not need to consume resources forever just because you once opened it. When Cloud Agent is idle, the runtime can sleep. When you return, Lumo starts it again and reloads the session history and workspace from persistent storage.
Active work is treated differently. A running task and an active event connection keep the Agent available while it is busy. This lets the infrastructure rest when you are away without treating every pause as the end of your work.
This is persistence, not a frozen live computer. Processes do not remain suspended exactly where they were; the durable parts are your sessions, workspace files, artifacts, settings, and the context Lumo needs to resume the experience.
Follow progress without babysitting the task
Cloud Agent streams text and status events as it works. Tool calls appear in the conversation, and permission or clarification requests can be answered from the mobile interface.
When you leave the app during a longer task, Lumo can send a notification for the moments that matter:
- •The task finished.
- •The Agent encountered an error.
- •A tool needs permission.
- •The Agent needs an answer before it can continue.
You can return to the exact session, review what happened, and decide the next step. You can also stop work that is going in the wrong direction instead of waiting for it to finish.
Cloud Agent and Mac connection solve different problems
| Mode | Cloud Agent | Connect to Mac |
|---|---|---|
| Mac required | No | Yes, running on the same local network |
| Workspace | Managed cloud workspace | Your Mac's Lumo workspace |
| Best for | Travel, mobile-first tasks, independent access | Work involving local sessions and files on your Mac |
| Availability | Pro and Max plans | Desktop companion workflow |
| Files | Material added or created for the cloud task | Files available to Lumo on your Mac |
Neither mode replaces the other. Connect to Mac when local context matters. Choose Cloud Agent when independence and availability matter more.
Understand the cloud boundary
Cloud Agent runs work remotely, so material used in that workspace is processed by Lumo's cloud infrastructure and the selected AI services. This is different from running the Agent against files that remain in a local Mac workspace.
Only add files and information that are appropriate for cloud processing, especially when working with unreleased, confidential, or client-owned material. Lumo's Privacy Policy explains the current data categories, service providers, troubleshooting retention, and deletion options in more detail.
You remain in control of the lifecycle: sessions can be stopped or deleted, and the Cloud Agent can be destroyed from settings when you no longer want the cloud workspace available.
Who Cloud Agent is for
Cloud Agent is a strong fit if you:
- •Regularly work from iPhone or iPad without access to your Mac.
- •Want longer Agent tasks to continue while you move between other work.
- •Need structured creator outputs, not just one-off answers.
- •Prefer a ready-to-use environment instead of maintaining your own remote machine.
- •Want to start a creator workflow immediately when an idea arrives.
If your work depends on a large local media library, private source files, or software installed only on your Mac, direct Mac connection may be the better mode.
Start your first Cloud Agent task
Open Lumo on iPhone or iPad, sign in with a Pro or Max account, and select Lumo Cloud Agent. Begin with a task that has a clear outcome — a seven-day content calendar, a research brief, a script package, or a lightweight landing page — and let the Agent build the result in its managed workspace.
The point of a cloud container is not the container itself. The point is that your Agent has somewhere dependable to work, even when your Mac is somewhere else.