Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.doe.so/llms.txt

Use this file to discover all available pages before exploring further.

Loops are standing cloud agents for recurring tasks. A Loop stores a prompt, a cadence, and the context it needs, then runs automatically on your behalf.

​
Creating a Standing Agent

Ask for work that includes a time reference: 
Send me a weekly pipeline summary every Monday at 9am PT.

Every morning, check @Ramp for transactions over $1,000 from yesterday and flag missing approvals.
Doe detects the schedule, extracts the recurring work, validates the cadence, and asks you to confirm. After confirmation, the Loop appears on the Loops page. Loops can use the same context as normal requests, including files, folders, previous sessions, and connected integrations. Use Loops for the work that should happen whether or not someone remembers to ask: pipeline checks, weekly metrics, expense reviews, renewal risk, customer follow-ups, and team updates.

​
Managing Loops

Open the Loops page with Cmd + J (Mac) or Ctrl + J (Windows). Each Loop shows its status, cadence, next run, last run, total runs, success rate, and services involved.
ActionWhat it does
Run NowExecute immediately
Pause/ResumeStop or restart the schedule
EditChange the Loop prompt and schedule language
DeleteRemove the Loop from the Loops list
See runOpen the chat created by a past run
When editing a Loop, Doe validates schedule changes before saving. If the prompt no longer includes a usable schedule, Doe will ask you to rewrite it in plain English.

​
Operate Loops at Scale

The Loops page is built for more than a short personal list. Use it to monitor recurring tasks across services, spot failures, and manage many standing agents at once.
ControlUse it for
SearchFind Loops by name, service, prompt, or related task
FiltersNarrow by status, running state, cadence, health, or service
SortReview by next run, created date, success rate, total runs, service, or name
List viewScan details such as next run, status, service, total runs, and success rate
Board viewGroup Loops by status, service, cadence, or next-run timing
Multi-selectPause, resume, or delete several Loops at once
Run historyOpen past runs and inspect the chat, output, and failure details
Use health and next-run views to catch overdue or failing Loops before they become silent gaps in reporting.

​
Execution Limits

Loops have built-in safeguards:
  • Minimum interval: 5 minutes between runs
  • Active Loops: 50 active Loops per user
  • Max executions: Optional cap on total runs when configured
  • Expiration date: Optional end date
  • Auto-pause: Stops after 5 consecutive failures
When a Loop hits its limit or expires, it pauses automatically.

​
Examples

Sales Pipeline Review - Weekdays at 9am 
Check @HubSpot for deals closing this month.
Show deal name, value, stage, days since last activity.
Flag any over $50k with no activity in 7 days.
Daily Expense Check - Every day at 8am 
Check @Ramp for transactions over $1,000 from yesterday.
Categorize by department. List any missing approvals.
Customer Follow-Up Queue - Every weekday at 4pm 
Search @Gmail and @HubSpot for customer replies that need a response.
Draft replies only. Do not send. Include source thread links.
Weekly Metrics Workbook - Mondays at 7am 
Pull activation and revenue metrics from the connected analytics and revenue sources.
Update the metrics spreadsheet and summarize changes.
Executive Briefing - Mondays at 8am 
Review CRM, customer, product, and finance signals from last week.
Draft an executive briefing with wins, risks, open decisions, and owner follow-ups.
Save the report and draft a team update for review.

​
Troubleshooting

Check status on the Loops page. It may be paused, expired, or hit its max runs. Also verify your integrations are still connected in Settings -> Integrations.
Loops pause after repeated failures. Check run history for errors. Common causes are expired integrations, missing permissions, insufficient credits, or prompts that need clearer scope.
Verify your timezone in the Loop settings. Scheduled times use the timezone you selected, not your system timezone.
Yes. Mention the files, folders, sessions, or integrations the Loop should use. Make sure any connected services stay active.

​
Next Steps

Prompting

Write better prompts for Loops

Integrations

Connect apps for Loops to use

Sharing

Share Loop outputs and recurring report folders

Preview Pane

Monitor Loop execution in real-time