Find your leak

Tick a line to see its fix.

All five leaks, in the order to fix them. Take the ones that match how you work.

Your fixes, in order

1. One long chat

   Before every reply, a Bot reads its whole conversation again. In a chat you've used all week, even a one-line answer spends usage on the week's history.

   Start a fresh chat for each task

2. A routine that runs too often

   Each run spends usage. An hourly schedule, a short interval or a Slack trigger on a busy channel can use up a week in a day.

   Slow your routines down

3. A routine on a Bot with a long chat

   A routine's runs happen in its Bot's chat. On a Bot you also talk to all day, every run reads that long chat again.

   Give a recurring routine its own Bot

4. Bots answering each other

   Every Bot reply counts, in a group chat and between Bots. A message that wakes a Bot costs a full turn, and its answer can wake the sender again.

   Keep Bots from answering each other

5. Big jobs, handed over blind

   Larger and longer jobs use more, and you can't tell how much until one has run.

   Check the meter before a big job

None of these sound like you? Go to If the week still runs out.