DebugBundle

Smart Reports

Business reports for recorded resolutions, major issues, downtime and the next priorities.

Business Smart Reports combine recorded incident and improvement transitions, observed health recovery and downtime, aggregate analytics and available retained context. They distinguish solved issues, recurrence, incomplete coverage and high/critical work that still needs attention. A report does not infer a fix from missing data or treat an AI suggestion as proof of causation.

Smart Reports setup

Use an agent to prepare Business reports covering resolved work, major incidents, downtime and next priorities, with the right projects, recipients and schedule.

Configure a report

Open Reports in the selected organisation. An authorised project administrator can create a definition covering projects they can manage. Explicitly enable reporting and review the AI disclosure before opting in to source collection. Full mode then uses bounded redacted evidence by default; choose Restricted to limit the context. Current privacy settings can narrow or withhold the whole report.

The new-report form starts with Monthly reporting, automatic generation at 09:00 in your device timezone, and your verified account email selected. Choose projects, review the evidence consent and save to activate the report. You can change these defaults or turn off Generate reports automatically for manual generation. Existing reports keep their saved schedule and recipients.

Select daily, weekly or monthly reporting, up to ten explicit projects and ten verified recipients. Every recipient must retain access to the complete saved scope. Organisation membership alone does not replace the project and origin checks. Viewer access permits authorised reading, not generation or administration.

Analysis uses complete UTC days, Monday–Sunday weeks or calendar months. Delivery uses the selected IANA timezone and local time; daylight-saving transitions are deduplicated. New projects or merged origins are not silently added to a saved scope.

Business includes five definitions and forty generations per account per monthly billing allowance, including annual plans. Extra capacity does not multiply this pool. Review remaining allowance and the schedule forecast. Excess demand produces a visible skipped-quota result; it does not create a hidden charge. A daily report plus weekly and monthly reviews must fit the shared allowance.

Read and download

The report you read in DebugBundle, its downloadable PDF and its email overview use the same saved facts and narrative. PDF preparation is asynchronous and shared across concurrent requests. Downloads, PDF retries and authorised archive reads do not run AI again. Links require authentication; PDFs are not public object URLs or email attachments.

Delivery status distinguishes accepted, rejected, uncertain and suppressed mail. An uncertain send is held for reconciliation because an absent acknowledgement does not prove that no email was sent. Access loss, unverified recipients, disabled preferences or exhausted notification allowance can suppress delivery.

Existing weekly digests keep their settings. If a weekly Smart Report overlaps an enabled digest, explicitly choose whether to keep both.

Automation

API, CLI and ordinary MCP use the same report services and actual actor identity. Start with:

debugbundle reports list ORGANISATION_ID --json
debugbundle reports get ORGANISATION_ID DEFINITION_ID --json
debugbundle reports allowance ORGANISATION_ID DEFINITION_ID --json

The API starts at /v1/organizations/ORGANISATION_ID/report-definitions and /v1/organizations/ORGANISATION_ID/reports. Ordinary MCP includes list_report_definitions, create_report_definition, list_reports, generate_report, prepare_report_pdf and get_report_pdf. Exact payloads and all run, delivery and PDF commands are in the generated API, CLI and MCP references.

Restricted agent and OpenAI read-only profiles do not acquire report mutations. Scoped member tokens must permit every selected project and original origin. Revocation is rechecked before processing, publication and email delivery.

Retention and self-hosting

Report-enabled numeric history can cover up to twelve months. New reports use only retained evidence; source caches follow the original source expiry and shorter privacy settings. Saved canonical reports and private PDF copies have a separate retention of up to ninety days. Explicit privacy changes and deletion take precedence. Account export includes bounded report-history sections and authenticated canonical downloads.

Self-hosted debugging does not require AI. Smart Report AI needs explicit opt-in, your own provider key and budget. Disabling new reporting preserves authorised archive access while current scope and privacy checks still apply.

On this page