Settings and permissions
Production monitoring settings decide how much Coldtea does on a repository without you, and how far its agents can go. You choose them when you set up production monitoring for a repository.
These settings appear once production monitoring is turned on for your TeaHouse.
Settings are per repository. Each repository you run production monitoring on has its own permission, budget, split, default agent, working days, and timezone.
Delivery status
A repository's production monitoring is either running or paused.
- Running: Coldtea keeps monitoring the repository, starting new work on the daily schedule.
- Paused: Coldtea does not start any new production monitoring work until you resume it.
You can pause and resume delivery at any time from the production monitoring settings. Pausing stops new work; it does not undo work already filed or started.
Supervised versus yolo
The permission setting controls how the reported findings are acted on:
- Supervised: the agent pauses for approval before it takes actions that need a decision, the same way a local agent prompts you in its own pane.
- Yolo: the agent finds issues and dispatches agents to work on it and issue a PR
Supervised keeps a human in the loop while the work runs. Yolo trades that for speed. Either way, Coldtea does not merge the result for you. Review still happens before anything ships.
We strongly advise only turning up YOLO when you've set up agentic testing for stronger verification signals
Capacity points
Production monitoring files a bounded amount of work each day. The bound is a daily capacity budget, measured in points, and it defaults to 8.
Coldtea sizes each task it files on a T-shirt scale and spends points from the day's budget as it goes:
- XS is 1 point.
- S is 2 points.
- M is 3 points.
- L is 5 points.
- XL is 8 points.
Filing continues, highest-ranked first, until the day's points are spent. Anything larger than XL is broken down into a parent item and smaller pieces rather than filed as one oversized task. Raise the budget to let more through in a day; lower it to keep each day small.
Working days
Production monitoring works all day round by default. Working days decide which days those are. Pick any combination of Monday to Sunday; every day is on to begin with.
A day you leave out gets nothing: no filed tasks, no plan email, and no brief. Turn Saturday and Sunday off and a repository plans Monday through Friday only.
At least one day stays on. Work already filed or running is unaffected, so a cloud run that started on Friday still finishes and opens its PR over the weekend.
To stop everything for a while instead, pause delivery.
Maintenance and feature split
Work production monitoring finds is either maintenance or a feature. The split setting is the target share of the day's budget for each, and the two shares add up to 100. The default is 70 percent maintenance and 30 percent feature.
Use the split to steer what gets filed. A repository you mainly want kept healthy leans toward maintenance; one you are actively growing leans toward features.
Default agent
Production monitoring starts its work as cloud runs, and the default agent decides which agent runs them. It can be any of Coldtea's cloud agents (Claude, Codex, or OpenCode) and defaults to Claude. Gemini is local-only and is not a cloud agent, so it is not available here.
What you keep control of
You control the emails production monitoring sends to you. See daily brief for the two per-user subscriptions.