Overdue commitments

A commitment is easier to keep when the missed date remains visible. Overdue commitments gives a team a short list of overdue work to review with the people responsible.

Try the report

Enable Overdue commitments in Plugins, then choose Run report. It uses the workspace’s existing tasks and needs no plugin-specific credentials. The plugin starts disabled. Use an authorized workspace, or explore Plugins in the fictional demo.

A fictional task to send a project summary was due yesterday. A second task is already complete. The pending task appears in the report; the completed task does not. Open the source task to review or change the next step.

Pending or snoozed tasks with a due date before the current UTC date qualify. Tasks due today and completed tasks are excluded.

Reading the result

Treat each finding as a reason to open its source record, not as a verdict on its own. Check the inspected-record count and any truncation notice before drawing a conclusion from what's shown: each source caps at 100 records, the combined input at 64 KiB, and displayed findings at 20, so an empty result means nothing matched in that particular snapshot, not that your whole business is clear.

The report itself is read-only and deterministic: it never changes a business record and never contacts anyone. Its AI/MCP tool is run_commitment_watch, and the host checks whether the plugin is actually enabled every time it runs. Running it needs no write approval and makes no model request on its own, though hosting and database usage still apply, and an AI conversation you have around the report can still incur its own model charges.

What this example teaches you to build

Turn a precise business rule into an inspectable report. This pattern can support other deadline reviews once the relevant records and permissions exist. The current report does not reschedule tasks or send reminders.

Start with the report source and its module manifest. The report code receives declared fields inside the shared isolate; the host supplies access and records the result. Reuse that boundary when changing the logic.

What to check, and how to turn it off

Turning the plugin off in Plugins stops new evaluations immediately; source records and historical receipts stay exactly as they were. For a missing-source or access error, check the workspace's source registration and permissions, correct them, and rerun, and for a truncated result, go inspect the source records directly rather than assuming whatever got cut off would have been clear. Running the report again never creates a duplicate task or message, so re-running it to double-check is always safe.

The developer guide links the source contracts and controlled tests, including npm run test:report-plugins. Those fixtures exercise the report behavior; they do not verify every installation's data or provider connections.