ClankerA practical Workspace guide
Test it once. Give it a rhythm.
Use a Loop when the next run should follow the previous run and a delay. Use a Schedule for set times. First test the task in a Session, then save the Project, Agent, goal, timing, and notification rule.
Start with $20 in included credits. See usage and plans.
Make one run useful before repeating it
Test the instructions with current inputs and inspect the saved output. Decide what counts as a meaningful change and what should happen if a source is unavailable. Ask for missing-source notes instead of a fabricated “all clear.”
Define the notification rule in the goal. A daily brief may need a short update every day; a monitor may need to stay quiet until something actionable changes. Choose the behavior that matches the work.
Choose the timing model
| Choice | Use it for | Check before starting |
|---|---|---|
| Loop | A repeating task with a delay after each run | Delay, expected run duration, model cost |
| Schedule | Work at set times | Timezone, selected days, goal, and sources |
Check what can run unattended
Allow computer jobs permits scripts and commands while your browser is closed. The Agent must also allow unattended work; Answer only, Research, and Always ask Agents cannot run unattended computer jobs.
Hosted workers can run in the cloud. Work using a connected computer still needs that machine online. Starting an ordinary Session does not automatically create a recurring worker.
Review history and stop unused work
Each worker keeps its conversation, progress, files, and run history. Inspect results and use pause, resume, run-now, or stop when appropriate. Check a failed job before assuming its result was saved.
Loops use 10× the model tokens, and computer usage is charged separately. Review the model, timing, current rates, and balance before starting. A short delay can turn a small individual run into substantial recurring usage.
Try it with a small example.
Copy, open a Session, and paste your prompt. It is not sent automatically.
Common questions.
Can 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 FAQCan recurring work run scripts while I am away?
Allow computer jobs lets a Loop or Schedule run scripts and commands while your browser is closed. Its Agent must permit unattended work; Answer only, Research, and Always ask Agents cannot run unattended computer jobs. Review progress and job results in the worker history.
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: Loops and Schedules
Content reviewed against the Workspace Guide & FAQ. Features and access can depend on your account.