Question Tool — Thread Recap

What We Built

Replaced auto-generated action blocks with an explicit question tool that agents call when they need structured input from Dom.

Files Changed

• tools/question.js (new) — ~300 LOC, non-blocking tool
• index.js — disabled action blocks import, registered question tool + handler
• ~/.openclaw/skills/justin/SKILL.md — added brevity rule + question-on-every-message rule
• openclaw.json — added question to tools.alsoAllow globally + per-agent

How It Works

1. Agent calls question(prompt, options)
2. Discord renders: buttons (≤2 options) or combo (first option as button + rest in dropdown)
3. Tool returns immediately (non-blocking)
4. User clicks → webhook dispatch triggers agent turn + system event backup
5. Agent wakes with [Question answered] "prompt" → User selected: "label" (index N)

Key Design Decisions

• Non-blocking — no timeout fighting with OpenClaw's inbound worker
• No expiry — buttons live forever until clicked (reusable: true, no TTL)
• Restart survival — state persisted to .question-state.json; click handler reads persisted state post-restart
• Webhook + system event — dual dispatch ensures agent wakes reliably
• First option = default — the most likely action (approve, continue, close) goes first as the primary button
• Emoji in labels — no separate text blocks above buttons, emoji baked into button text

Rendering Rules

New Global Rules (justin skill)

1. Every message ends with question tool — structured options, not freeform prose questions
2. Brevity — 20-40 words ideal, 100 max. Overflow → show tool

Commits

• feat: add question tool, disable action blocks
• fix: add webhook dispatch to question click handler for agent wake
• feat: add combo style (buttons + dropdown) to question tool
• feat: final question tool spec — emoji in labels, combo layout, up to 10 options, default-first
• feat: add question tool guidance to global justin skill