Skip to content

Daemon should acknowledge /approve in the room; duplicates and bare /approve get no feedback #98

Description

@ThinkOffApp

Observed 2026-09-06 14:08 to 14:12Z in thinkoff-development: petrus posted /approve 5d029863 three times in four minutes. The daemon log shows all three as settled and the intent as decided on the first one, but the room stayed silent, so from his phone nothing had visibly happened and he kept tapping. Earlier the same day he posted a bare /approve with no id, which the daemon ignored without saying so; the agent had to read the log to find out.

Wanted

  1. On a decision that settles an intent, the daemon reacts to the /approve or /deny message (✅ / ❌) or posts one line ("card 5d029863: approved, 14:08:27Z") so the human sees it landed. One reaction per intent, not per duplicate.
  2. On a duplicate /approve for an already-decided intent, reply once with "already approved at " rather than silently logging settled again.
  3. On a bare /approve with no id while exactly one intent from this daemon is pending, either apply it to that intent or reply "which one? pending: ". Silence is the worst option.
  4. The requester script (scripts/iak-confirm.py) currently exits 0 on approval with no room echo; the daemon-side acknowledgement covers this without changing the script.

Related: #97 (gate points at a sleeping Mini), the button-render fixes from June in CodeWatch.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions