Skip to main content
List and manage inferred follow-up commitments. Commitments are opt-in (commitments.enabled), short-lived follow-up memories created from conversation context and delivered by heartbeat. See Inferred commitments for the conceptual guide and config. With no subcommand, openclaw commitments lists pending commitments.

​
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: show all statuses instead of only pending commitments.
  • --agent <id>: filter to one agent id.
  • --status <status>: filter by status. Values: pending, sent, dismissed, snoozed, or expired. Unknown values exit with an error.
  • --json: output machine-readable JSON.
dismiss marks the given commitment ids as dismissed so heartbeat will not deliver them.

​
Examples

List pending commitments: 
openclaw commitments
List every stored commitment: 
openclaw commitments --all
Filter to one agent: 
openclaw commitments --agent main
Find snoozed commitments: 
openclaw commitments --status snoozed
Dismiss one or more commitments: 
openclaw commitments dismiss cm_abc123 cm_def456
Export as JSON: 
openclaw commitments --all --json

​
Output

Text output prints the commitment count, the store path, any active filters, and one row per commitment:
  • commitment id
  • status
  • kind (event_check_in, deadline_check, care_check_in, or open_loop)
  • earliest due time
  • scope (agent/channel/target)
  • suggested check-in text
JSON output includes the count, the active status and agent filters, the commitment store path, and the full stored records.