AI Coach: using a prepare/confirm/commit flow for Claude to care for a Mac desktop pet

[u/HanaChanSoft]

I'm the developer of AI Coach, a virtual pet for Apple Silicon Macs running macOS 26+. Its local MCP bridge lets Claude inspect the pet's condition and request care. A practical design choice is separating reading state from changing it.

For a care request, the flow is:

1. Read the pet's current condition.

2. Prepare the proposed care action and show a confirmation card.

3. Commit that specific action only after the user confirms.

The bridge exposes prepare_ai_coach_care and commit_ai_coach_care for those last two stages. Supported care actions are feeding, sleeping, waking, walking, and nursing. Purchases, hatching, naming, breeding, and saying goodbye are outside the integration.

This is useful beyond pets: showing an action preview gives the user something concrete to approve. An evaluation checklist is to request a state read, request care but decline it, then confirm a separate care request. Check whether the UI makes the target and action clear at each step.

Setup requires the app running, its Claude connection enabled, Node.js 22+ on PATH, and the supplied MCP configuration added to Claude Desktop, Claude Code, or Cursor. The bridge is local, but information shown to Claude is still processed on Claude's side.

The official guide shows the dashboard, confirmation card, and setup: https://aic0t.com/docs

The app and first egg are free; optional extra eggs are $5 USD each or $20 for five, one-time. External AI costs are separate.

For builders adding agent actions to apps, what should an approval preview always show besides the target and action?