ClankerChoose the right fit
Choose where the work should run.
Start with a normal Workspace Session for writing, research, files, and selected tools. Use a cloud environment when the work needs a browser or compute, and a connected computer when it needs that machine’s files or apps. These options have different access and availability requirements.
Start with $20 in included credits. See usage and plans.
Match the environment to the dependency
| Environment | Suitable work | What to check |
|---|---|---|
| Normal Session | Writing, research, analysis, Project files, and selected tools | It cannot see or control your computer. |
| Cloud browser | Interacting with websites from a hosted browser | Required login access and ongoing usage. |
| Cloud compute or desktop | Scripts, calculations, files, or a hosted desktop when available | Account availability, saved outputs, and stop controls. |
| Connected computer | Work needing that machine’s local files and apps | Desktop app, approved connection, correct machine, online availability. |
What happens when your laptop closes?
Hosted Loops and Schedules can run recurring cloud work independently of your laptop. A task using your connected machine still needs that machine online and available. A normal conversation does not become a recurring background worker just because you close the browser.
Try the intended environment on a small task before relying on unattended execution. Check the saved result and worker history, and confirm that any computer jobs are permitted by the Agent and worker settings.
Keep the access boundary explicit
Upload or select the files needed for ordinary Workspace work. Connecting a remote computer is a separate decision. Choose the machine with the relevant apps and files; do not assume the active Session has access to every device you own.
The desktop provider path’s local credential custody is not a blanket claim that hosted Workspace data stays on your device. Review the data boundary of the actual feature and environment used.
Save the result and stop the environment
Open the output from the Project’s Files tab or Session Preview to verify what was retained. A running environment and a saved Project file are different things.
Use stop or shutdown controls when finished. Hiding a viewer may leave the underlying environment running and using credits. Pause or stop recurring workers separately if you no longer want future runs.
Common questions.
Can a normal Session see or control my computer?
No. A normal Session works with your writing, research, Project files, and selected tools. Use Cloud browser for website interactions, cloud compute for scripts, or an explicitly connected computer for its local files and apps.
More in the FAQCan it work while my laptop is closed?
Hosted Loops and Schedules can run recurring work in the cloud. Tasks using a connected computer still need that computer to be online and available. Simply starting a browser conversation does not turn it into a recurring background task.
More in the FAQDoes closing a viewer stop its computer?
Not necessarily. Active browsers, desktops, and cloud computers can continue using credits. Use their stop or shutdown controls when you finish. Availability and controls are shown in Workspace.
More in the FAQSources: Workspace guide: where work runs · Workspace guide: recurring work
Content reviewed against the Workspace Guide & FAQ. Features and access can depend on your account.