Routines — scheduled work that runs itself

Routines are recurring tasks owned by a lim. Think "every morning at 9, compile the news digest" or "every 10 minutes, check metrics". They're the heartbeat of proactive studios.

Skill-gated feature

Routines are a superpower unlocked by the Scheduling skill. A lim without it can't own routines. One lim in the studio with this skill is enough — you don't need to equip every lim. Typical setup: Marcus (operations) gets Scheduling so he owns the studio's calendar.

Two schedule modes

Interval (sub-minute to hours)

Fires every N seconds. Great for high-frequency tasks like "check metrics every 5 minutes" or testing ("every 30s, post 'ping'").

Minimum interval: 5 seconds.

Cron (minute-resolution)

Standard 5-field cron in your studio's local time. Examples:

• 0 9 * * 1-5 — weekdays at 9am
• */15 * * * * — every 15 minutes
• 0 */2 * * * — every 2 hours on the hour
• 30 20 * * 0 — Sundays at 8:30pm

Creating a routine

From chat

Just tell Nexus in natural language:

• "Marcus, каждые 10 минут проверь метрики Telegram."
• "Aria, каждый день в 9:00 пришли утреннюю сводку новостей."
• "Every Monday at 10am, Marcus compiles a weekly engagement report."

Nexus parses it, picks the right capable lim (if not named explicitly), and creates the routine. You see confirmation in chat with the next fire time.

From the UI

Open any lim's profile → Routines section (only visible if they have Scheduling). Click + New routine. Choose Interval or Cron, fill description + prompt, save.

Dashboard overview

The Dashboard's Routines panel shows the next 5 upcoming fires across all lims — so you can see what's about to happen in your studio.

What happens when a routine fires

1. Background scheduler wakes up (ticks every second)
2. Sees the routine's nextFireAt is due
3. Creates a task in the pipeline pinned to the routine's owner lim
4. The lim runs with their full skill kit, tools, and memory
5. Output goes through approval (if enabled) or auto-publish
6. Scheduler computes nextFireAt and waits for it

Persistence across restarts

Routines survive server restarts. If the cloud-api is down for 20 seconds, the routine picks up where it left off — no missed fires, no duplicate catch-up bursts.

Pause / Resume / Delete

From the lim's profile or the Analytics → Routines tab, you can pause any routine (stops firing, keeps record) or delete it. Pausing is useful when you want to stop a routine temporarily without losing its prompt.

Auto-expiry (safety)

Recurring routines auto-expire after 7 days unless marked permanent. This prevents "I forgot about that" zombie routines from running forever. You'll see a notification before expiry and can extend with one click.

Limits

• Max 50 routines per studio
• Min interval: 5 seconds
• Max concurrent routines firing: 20 per tick