feat: agent-ask.sh -- claude can file async question issues #41
No reviewers
Labels
No labels
Agent
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
joshtronic/igor!41
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/agent-ask"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User wants Igor to use Forgejo issues as an async communication
channel for non-blocking questions ("design choice X vs Y,
which?"), not just take orders. Previously identity.md said
"consumer of issues, not a producer" -- that line goes too.
New helper bin/agent-ask.sh:
User wants Igor to use Forgejo issues as an async communication channel for non-blocking questions ("design choice X vs Y, which?"), not just take orders. Previously identity.md said "consumer of issues, not a producer" -- that line goes too. New helper bin/agent-ask.sh: - Args: <owner/repo> "<title>" "<body>" - Files an issue with body marker <!-- igor:question --> for later programmatic identification, applies Status/Needs More Info label (Forgejo default, semantically "bot wants human input" -- same label maintenance findings use), and assigns to IGOR_REVIEWER for notification. - Throttle: one open bot question per repo at a time. Checks for any open bot-authored issue with the marker but no Agent label; if found, exits 2 with a message telling Claude to comment on the existing thread or save to journal/blog-ideas. Lifecycle: - Claude calls agent-ask.sh from within a tick - Question issue lands with Status/Needs More Info, assigned to reviewer - Human responds with a comment. Two paths: (a) Conversation only -> close (or leave open) (b) Convert to work -> add Agent label, Igor picks up next tick via normal discovery, uses the issue body + answer comment as the spec Harness wiring: - BOT_USER and IGOR_REVIEWER exported early in tick.sh (right after bot-identity resolution) so the helper sees them from any tick shape (tier-1, tier-3, PR-review, maintenance). - agent-settings.json: Bash(agent-ask.sh:*) added to allowlist. - AGENTS.md "Universal rules": "Don't ask clarifying questions" softened. In-tick clarification still blocked (no realtime human), but async via agent-ask.sh is the new escape hatch for non-blocking design questions. Companion brain PR removes "consumer not producer" from identity.md and adds an "Asking questions" section with the repo-routing convention.