Schedule Reports, Not Meetings

You have typed the same prompt into chat sixteen Mondays in a row. Weekend signups, grouped by source, flagged against the trailing seven-day average. You know the wording by heart. You probably keep it pinned in a Notion doc so you can paste it without thinking.

The cost is not the typing. The cost is that the question is not asked until you show up to ask it. If you are sick on Monday, no one sees the weekend. If standup runs long, the chart is not in the channel by the time the meeting starts. A question you ask every week is a different artifact than a question you ask once — and Limerence's chat has always been good at the second one. Automations is the place the first one lives.

Pin the Prompt to a Schedule

Open the Automations page. Click "New Automation," pick the agent that already answers this question, paste the prompt verbatim, and use the visual schedule builder.The schedule is stored as a 5-field cron expression and runs in UTC. The builder writes the string for you — Hourly, Daily, Weekly, Monthly, Yearly with day and hour toggles — so you never have to type 0 9 * * MON-FRI yourself, and you never have to think about cron syntax to use it. Save. The automation appears in the sidebar under Scheduled, with the next run time in human form.

The four-beat version, for the skim:

1. 1

   Pick the agent that already answers this question — the one you would have opened a chat with anyway.

2. 2

   Paste the prompt you have been retyping. No rewrite needed; the same words that work in chat work here.

3. 3

   Set the schedule with the visual builder. Daily, weekdays only, 09:00 — no cron syntax required.

4. 4

   Save, then hit Run Now once to confirm the prompt and the agent agree on what you meant.

Open the automation's detail panel and the layout is the part that earns the feature. Schedule rendered in plain English. Next run time as a real timestamp. Prompt right there, editable. A Run Now button for when you want the answer immediately. And underneath, a Recent Runs list — every past run is a row, and clicking one opens the historical chat with the messages, charts, and artifacts the agent produced, exactly the way they looked when the run finished.

Where the Result Lands Today

Worth being plain. Today the result of a tick lands in the app, not in your inbox or a Slack channel. Slack, Google Chat, and email push are on the roadmap; for now, the answer is a tab you keep open or a bookmark you check.

What you get instead is the Automations page as a dashboard of your team's recurring questions. Sessions group as Scheduled and Paused. Underneath, a live feed of In Progress and Completed runs — open the page and you see what is running right now and what finished while you were away. Clicking a completed run opens that historical chat, intact: the same messages, charts, and artifacts the agent generated for that tick.

Pause is a single toggle. Edit the prompt or the schedule, save — the cron registration reconciles in place and the next tick uses the new version.Pausing does not delete history. A paused automation keeps every past run visible in its detail panel, so you can re-open last quarter's reports on an automation that has been off for months.

One caveat worth naming up front: schedules run in UTC, and there is no per-automation timezone yet. A reader in São Paulo who wants 09:00 local picks 12:00 UTC and re-does the math at daylight saving. Per-automation timezones are on the roadmap; for now, the builder makes it obvious which UTC hour you picked.

Why the Tick Is Fast Even When the Answer Is Slow

The schedule and the LLM run live in two separate queues. The cron tick fires, writes a chat session row, and hands the work off to a second worker — which can take seconds or minutes without that latency leaking back to the schedule. A 90-second answer never blocks the next 9am tick. The companion deep-dive walks through the mechanism if you want it.

What It Enables, What's Coming

Once a question is on a schedule, a few things shift. Recurring analyses stop being attached to one person's morning. The team gets a shared, scrollable record of every past run — an artifact that survives someone going on leave, or a new hire wanting to understand where last quarter's numbers came from. A noisy automation gets paused, not deleted; the question is still there next quarter when it is useful again.

What is coming, in priority order: outbound delivery to Slack, Google Chat, and email, so a tick can push to where the conversation is happening; per-automation timezones beyond the global UTC default; richer run-history surfaces beyond the current chat-session view.

The Automations page is in the left rail. The first one takes about ninety seconds. The second is faster, because by then you already know which questions are recurring.