Repository navigation
Paused issues that are blocked become Blocked, with a new issue for the blocker #267
Description
Problem
When a worker or issue owner stops because something outside its issue blocks it (a missing feature, another bug, an owner decision, an external service), the issue lands in Paused (work exists, no agent on it). Nothing records what blocks it, so the owner can't see it, and nobody picks the blocker up. The owner wants these issues to show as Blocked, with a new issue created for whatever blocks them.
issueProgress already shows an issue as blocked when it has an open GitHub "blocked by" link. What's missing is the way to make that link:
propose_issue_changehas no operation to add or remove a "blocked by" relationship (it supports create, split, body, milestone, state and sub_issue). GitHub hasaddBlockedBy/removeBlockedByGraphQL mutations; Forgejo has issue dependencies.- The model-facing text for implementors and issue owners doesn't tell them what to do when blocked.
Wanted
- A
blocked_byoperation (add and remove) onpropose_issue_change, through the issue host for GitHub and Forgejo, auto-executed likesub_issue. Reverse state: remove unblocks. - Instructions for managed implementors and issue owners: when work can't continue because of something outside the issue, create an issue describing the blocker (
create), link it withblocked_by, and end the turn with a final result that names the blocker. Don't do this for owner questions that the question tool answers, or for ordinary failing tests inside the issue's scope. - Run the evals that
evals/README.mdnames for this text with the free--context/--dry-runchecks only (no paid runs).
Done when
A worker that hits an outside blocker leaves its issue showing Blocked, linked to a new open issue for the blocker; closing the blocker returns the issue to Paused or Ready.
Activity
tannerpolley commentedon Oct 31, 2026
T3 Code status: Unavailable
Issue: #267 Paused issues that are blocked become Blocked, with a new issue for the blocker
Thread: thread:delegated-task:command%3Amcp%3A66d39c35-d3cf-4d02-bb35-a21c95b55dac%3Adelegate-task%3Aissue-267-impl
Model: gpt-6.1-sol
Branch: issue-267-paused-issues-that-are-blocked-become
Updated: 2026-11-13T05:10:19.979Z
tannerpolley commentedon Oct 31, 2026
T3 Code closeout: done
Issue: #267 Paused issues that are blocked become Blocked, with a new issue for the blocker
Thread: thread:delegated-task:command%3Amcp%3A66d39c35-d3cf-4d02-bb35-a21c95b55dac%3Adelegate-task%3Aissue-267-impl
Model: gpt-6.1-sol
Branch: issue-267-paused-issues-that-are-blocked-become
Completed: 2026-10-31T21:05:10.352Z
Implemented #267 and committed as
8f5c7e67cfonissue-267-paused-issues-that-are-blocked-become. Working tree is clean.blocked_byadd/remove through the existing contracts → MCP → issue-change service → host path, using GitHub GraphQL mutations and Forgejo dependencies.Validation passed: 135 tests, including
core.test.ts; package typechecks for server, contracts, provider-core, web, and evals; formatting and linting. Claude and Codex eval--context/--dry-runchecks passed without paid calls.The commit hook’s sole failure was the known unused-exports baseline #256; used the authorized
--no-verifyexception.No push or PR. Live host mutations and paid model behavior remain unverified; no real issues or relationships were created, and live T3 data was untouched.