Skip to content

Issue Monster: enforce issue_number for assign_to_agent and soften assignment comment wording #27160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 4 commits into from
Apr 19, 2026
Merged

Issue Monster: enforce issue_number for assign_to_agent and soften assignment comment wording #27160

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
86d71f6
Initial plan
Copilot Apr 19, 2026
166cab5
chore: start investigating issue-monster assign_to_agent field mismatch
Copilot Apr 19, 2026
7141dc7
fix(issue-monster): enforce issue_number key for assign_to_agent output
Copilot Apr 19, 2026
a26f97a
chore: remove issue monster workflow regression test
Copilot Apr 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/issue-monster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -584,6 +584,8 @@ For each selected issue, use the `assign_to_agent` tool from the `safeoutputs` M
safeoutputs/assign_to_agent(issue_number=<issue_number>, agent="copilot")
```

Use the exact field name `issue_number` (underscore). Do **not** use `issue-number` (hyphen), which is invalid and will fail safe-output validation.

Do not use GitHub tools for this assignment. The `assign_to_agent` tool will handle the actual assignment.

The Copilot coding agent will:
Expand All @@ -597,7 +599,7 @@ The Copilot coding agent will:
For each issue you assign, use the `add_comment` tool from the `safeoutputs` MCP server to add a comment:

```
safeoutputs/add_comment(item_number=<issue_number>, body="🍪 **Issue Monster has assigned this to Copilot!**\n\nI've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.\n\nThe Copilot coding agent will analyze the issue and create a pull request with the fix.\n\nOm nom nom! 🍪")
safeoutputs/add_comment(item_number=<issue_number>, body="🍪 **Issue Monster selected this for Copilot!**\n\nI've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.\n\nIf assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.\n\nOm nom nom! 🍪")
```
Comment on lines 601 to 603
Copy link

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment template now correctly avoids claiming assignment success ("requested assignment" / "If assignment succeeds"), but the surrounding instruction text still frames this as "Add Comment to Each Assigned Issue" / "For each issue you assign". Consider aligning that wording to "requested" or "attempted" assignment to avoid confusing agents about whether they should comment even when assignment fails.

Copilot uses AI. Check for mistakes.

**Important**: You must specify the `item_number` parameter with the issue number you're commenting on. This workflow runs on a schedule without a triggering issue, so the target must be explicitly specified.
Expand Down
Loading