It watches while you are away
A Loop runs on Comma's servers, without an always-on sandbox. Your computer can be off. Open the Task to see what the Loop watches and what it reported.
Ask in chat. Comma writes a Loop, a small program that runs on Comma's servers. The Loop checks an inbox, a repository or a feed, and wakes the agent only when your condition is met.
In Comma's Home chat, Alex asks Comma to watch the acme/api repository on GitHub and to tell him when a pull request touches billing. Comma answers that it wrote a Loop, shows the Loop as code, and names the Task that holds it. The Task shows in the Tasks list with the mark On updates.
The Loop looks at every change. It wakes the agent only when your condition is met. Only then does the agent run and use model tokens.
A Loop runs on Comma's servers, without an always-on sandbox. Your computer can be off. Open the Task to see what the Loop watches and what it reported.
Send an event to a Loop through the API, or through the Loop's secret webhook URL. A build server or any other service can supply the signal. The Loop checks the event and can wake the agent.
A Loop saves a checkpoint and gets it back when it starts again. It can wake the agent only a limited number of times in ten minutes. A Loop that stays at that limit for an hour pauses, and the Task shows it.
There is no builder. You describe the watch, and the agent writes it.
Name the source, the change that matters and the response you want. For example: watch a release feed for breaking API changes and summarize any match.
The agent writes a Loop, and Comma runs it on its servers. The Loop checks sources or receives events, within your access.
When attention is needed, the Loop notifies its agent. What the agent does next depends on your instruction, its tools and its permissions.
Watching an inbox, repository or feed you can access, classifying what changes, and notifying the agent when a condition needs attention. The follow-up depends on the agent's instructions and tools.
A source it watches, such as an inbox, repository or feed, or an event an external system sends through the Loop's API or secret webhook URL, within the Loop's capabilities and your permissions.
A scheduled task starts at a set time. A Loop responds when a condition or signal calls for work. The Routines briefing prepares prompts for you to send; it does not run every item on its own.
No. A Loop acts with its creator's authority and a fixed set of capabilities. For example, the read-only Google Workspace connection cannot send email because a Loop saw a new message.
Agent wake-ups are limited within ten minutes, and a Loop that stays at the limit for an hour pauses. After a fault, the server restarts the Loop from its checkpoint at most three times an hour; after that it stops and tells its agent.
Not for the Loop: it runs on Comma's servers, without an always-on sandbox. If the follow-up needs files, apps or a coding runtime on your computer, that computer must be online for that work.