What a good daily report contains
- What ran yesterday: tasks, results, one line each.
- What failed and why, with the log line.
- Spend: tokens and cost versus the day before.
- What is pending today, in priority order.
Step 1 — write the prompt
Be specific about the output format so the report is comparable day to day: “Write a Markdown report with sections Done, Failed, Spend, Pending. Use the audit history as the source of truth and say when data is missing.”
Step 2 — schedule it
Add the run to your scheduler as in the cron recipes guide, or use the built-in scheduled jobs setting. Pick a time when the machine is on and the network is quiet.
Step 3 — control the cost
A daily report is a fixed recurring cost. Multiply by 30 to see the monthly number, then set a token budget and a daily spend cap so one runaway run cannot surprise you. Review the report once a week and trim sections nobody reads.
Step 4 — verify it stays useful
Read the first week of reports yourself. If the agent invents numbers, tighten the prompt to require sources from the audit trail. If sections repeat, shorten them. An automated report only earns its cost if someone actually acts on it.