Briefings and Schedule
Create timed research in Bot, inspect the result, and control future runs from Schedule.
Ask for timed work#
- Open Bot and make a clear request with the work and timing. Example: “Send me a briefing every weekday at 8:00 AM.”
- Read the receipt for the cadence and next execution time. Creating a Loupist alone creates no schedule.
- Open Schedule and select the task to inspect its details and saved runs.
- Use Ask Bot to draft a change to its time or prompt, then review and send the request.
The default morning briefing is 08:00 Monday through Friday in this Mac's time zone. Custom scheduled research supports once, interval, daily and weekly work. Daily and weekly schedules use a time zone.
Read a result#
A finished or failed run appears in Bot with From: and Open. Open its research to read the answer and linked evidence. Schedule keeps run status and timing, including failed work. Briefings can include dated asset changes, results, alerts and checks against principles.
Briefings and scheduled research use your AI account for each run. Watching uses no AI. Unattended research has fewer permitted actions than interactive Chat; it cannot save your Journal judgment, change schedules or publish charts and table cards.
Pause, run or stop#
| Control | Effect |
|---|---|
| Pause | Prevent future starts |
| Resume | Enable future starts again |
| Run now | Attempt a run immediately, including on a paused task |
| Stop | Cancel the current run separately |
| More → Delete | Remove a custom task after confirmation |
Run now does not turn a paused recurring schedule back on. Briefing and results tasks are paused rather than deleted. A completed one-time task needs editing before it can resume.
Keep the app running#
Schedules need Loupist open or running in the menu bar. Settings → General → Keep running in the menu bar controls window-close behavior. Without an earlier explicit choice, the first briefing or Watching opt-in turns it on. Cmd+Q quits the app.
Missed recurring occurrences combine into one due run. Three consecutive failures pause a recurring task; rejected credentials or a missing model can pause it immediately. Inspect the failed run, repair the account or data access, then resume.
Based on the app’s source documentation and English interface labels. Report a docs issue.