Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 78 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

[OPS] Loop issue filter -- exclude DO-NOT-CLOSE, epic, and meta issues from agent pickup #117

New Issue
Closed
opened 2026-04-04 11:55:14 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-04 11:55:14 +00:00
Owner
Copy Link

Problem

Gemini loop grabbed issue #431 (DO NOT CLOSE -- Master Escalation) and tried to work it. Loops should never pick up permanent/meta/epic issues.

Solution

Tighten the get_next_issue filter in claude-loop.sh and gemini-loop.sh:

  1. Skip issues with title containing: [DO NOT CLOSE], [EPIC], [META], [GOVERNING], [PERMANENT]
  2. Skip issues with title containing: [MORNING REPORT], [RETRO], [INTEL]
  3. Skip issues assigned to Rockachopa (human-only)
  4. Add the filter to timmy-config source control so it survives deploys

Acceptance

  • No loop worker ever picks up a DO-NOT-CLOSE or EPIC issue
  • Filter list is maintained in one place in timmy-config
  • Existing filters in loop scripts are updated
## Problem Gemini loop grabbed issue #431 (DO NOT CLOSE -- Master Escalation) and tried to work it. Loops should never pick up permanent/meta/epic issues. ## Solution Tighten the get_next_issue filter in claude-loop.sh and gemini-loop.sh: 1. Skip issues with title containing: [DO NOT CLOSE], [EPIC], [META], [GOVERNING], [PERMANENT] 2. Skip issues with title containing: [MORNING REPORT], [RETRO], [INTEL] 3. Skip issues assigned to Rockachopa (human-only) 4. Add the filter to timmy-config source control so it survives deploys ## Acceptance - No loop worker ever picks up a DO-NOT-CLOSE or EPIC issue - Filter list is maintained in one place in timmy-config - Existing filters in loop scripts are updated
Timmy self-assigned this 2026-04-04 11:55:14 +00:00
Timmy closed this issue 2026-04-04 16:00:08 +00:00
Timmy commented 2026-04-04 16:01:17 +00:00
Author
Owner
Copy Link

Delivered in commit 3cf9f0d on main. Tested locally. Closing.

Delivered in commit 3cf9f0d on main. Tested locally. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#117
Delete Branch "%!s()"

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?