Team Brief
Team Brief answers three operating questions without opening every receipt: what finished, what needs attention, and what should you do next. The in-app view is private and available whenever you sign in.
Read one bounded operating view
Open Team Brief from Notifications, Agent Team Inbox, Team Insights, or /brief. Choose 7 days for the current operating pulse or 30 days for a broader pattern. The top row compares completed outcomes with the immediately preceding window and keeps one deterministic next action above the Team activity list.
- Outcomes, failures, active runs, approvals, recoveries, health signals, and actual model cost come from stored hosted-run facts.
- Estimated time appears only when an owner or editor entered minutes per outcome in Team Insights, and it is always labeled Assumption.
- Team status summarizes observed work as healthy, active, or needs attention; it is not a quality guarantee.
Choose a simple email rhythm
Open Settings > Notifications or use the control on Team Brief. In app only sends nothing. Weekly email is available on Free. Daily email requires Pro or Max. Delivery is opt-in and uses the verified email attached to the signed-in account; Codelit does not accept or store a separate recipient address in the preference.
- Weekly briefs are scheduled for Monday at 9 AM in the saved browser timezone.
- Daily briefs are scheduled for 9 AM in that timezone.
- An empty brief advances the schedule without sending an email.
- Each period has one deterministic delivery key, so a retry cannot send the same brief twice.
Know the privacy and cost boundary
Building Team Brief does not call a model, connector, browser provider, or execution runtime. It aggregates existing operational records. The brief and email exclude prompts, source content, output, logs, credentials, account identities, provider responses, run identifiers, and exact external resource identifiers. Email also excludes user-defined Team names; those remain in the private in-app view.
- The authenticated API is private and no-store.
- The delivery preference is server-owned and denied to direct client Firestore access.
- Only cadence, timezone, bounded delivery status, plan, and verified-email readiness return to the interface.
- Email is the only variable delivery cost, and empty periods do not send.
Disable, retry, or delete safely
Turn delivery to In app only at any time without removing the private brief. A delivery failure releases its short lease, records only a bounded failure code, and retries after six hours without logging the email-provider response. Operators can set TEAM_BRIEF_DELIVERY_DISABLED=true to stop all outbound Team Brief work while keeping the in-app view available.
- Delete account & data removes the preference, its notification receipts, Team assumptions, runs, and other owned records before deleting the identity.
- The cron isolates Team Brief failure from hosted runs, triggers, Team Health, and other maintenance.
- Turning email off removes the next delivery time but keeps the last bounded delivery status visible.