Neura Market Logo

OpenClaw Commitments Command: Inspect and Dismiss Inferred Follow-ups

Reference for the openclaw commitments CLI command, used to review and manage records from the retired inferred commitments experiment. Covers listing, filtering, and dismissing commitments.

Read this when

  • You want to inspect inferred follow-up commitments
  • You want to dismiss pending check-ins
  • You are auditing what heartbeat may deliver

Review and manage records left behind by the retired inferred commitments experiment. OpenClaw no longer generates or sends new commitments, though the maintenance command remains available so upgrades can inspect and clear existing SQLite entries.

Without a subcommand, openclaw commitments shows commitments that are pending.

Usage

openclaw commitments [--all] [--agent <id>] [--status <status>] [--json]
openclaw commitments list [--all] [--agent <id>] [--status <status>] [--json]
openclaw commitments dismiss <id...> [--json]

Options

  • --all: display commitments in every status, not just pending ones.
  • --agent <id>: limit results to a single agent ID.
  • --status <status>: narrow results by status. Acceptable values: pending, sent, dismissed, snoozed, or expired. An unrecognised value causes the command to exit with an error.
  • --json: produce output in machine-readable JSON format.

dismiss sets the status of the specified commitment IDs to dismissed.

Examples

Show commitments that are pending:

openclaw commitments

Display every stored commitment:

openclaw commitments --all

Restrict to one agent:

openclaw commitments --agent main

Locate commitments with a snoozed status:

openclaw commitments --status snoozed

Dismiss one or more commitments:

openclaw commitments dismiss cm_abc123 cm_def456

Export data as JSON:

openclaw commitments --all --json

Output

Text output includes the total number of commitments, the path to the shared SQLite database, any filters that are active, and one line per commitment:

  • commitment ID
  • status
  • kind (event_check_in, deadline_check, care_check_in, or open_loop)
  • earliest due time
  • scope (agent, channel, or target)
  • suggested check-in text

JSON output provides the count, the active status and agent filters, the shared SQLite database path, and the complete stored records.