feat(agents): task-implementor should post a 'work started' comment before cloning #11031

Closed
opened 2026-05-08 09:27:16 +00:00 by hamza.khyari · 1 comment
Member

Summary

The task-implementor agent currently reads the issue/PR, clones the repo, implements the fix, runs quality gates, commits, and posts an attempt comment — all silently until the final attempt comment. The user has no visibility that implementation work has started.

Add a notification comment posted after reading the issue/PR (confirming it exists) but before cloning — giving the user instant visibility.

Proposed Change

Add a Step 1.5 in both issue_impl and pr_fix procedures — after Step 1 (read issue/PR) but before Step 2/3 (clone).

For issue_impl

Post comment on the issue:

> Starting implementation for issue #{work_number}: {issue_title} (`issue_impl`)...
>
> Reading requirements and setting up development environment. This may take several minutes.

---
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

For pr_fix

Post comment on the PR:

> Starting fix for PR #{work_number}: {pr_title} (`pr_fix`)...
>
> Addressing review feedback and CI failures. This may take several minutes.

---
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

Why Step 1.5 (not Step 0)

  • Issue/PR is confirmed to exist (no false notifications on nonexistent items)
  • Title is available for a more informative message
  • Clone + implementation hasn't started yet (fast notification)

Affected Files

  • .opencode/agents/task-implementor.md — add Step 1.5 to both procedures

Subtasks

  • Add notification step to issue_impl procedure (after read issue, before clone)
  • Add notification step to pr_fix procedure (after read PR, before clone)

Acceptance Criteria

  • User sees a comment within seconds of the implementor starting work
  • Comment includes work number, title, and work type
  • Comment includes the bot signature

Metadata

  • Commit Message: feat(agents): add work-started notification to task-implementor
  • Branch: feature/impl-started-notification
## Summary The `task-implementor` agent currently reads the issue/PR, clones the repo, implements the fix, runs quality gates, commits, and posts an attempt comment — all silently until the final attempt comment. The user has no visibility that implementation work has started. Add a notification comment posted after reading the issue/PR (confirming it exists) but before cloning — giving the user instant visibility. ## Proposed Change Add a **Step 1.5** in both `issue_impl` and `pr_fix` procedures — after Step 1 (read issue/PR) but before Step 2/3 (clone). ### For `issue_impl` Post comment on the issue: ``` > Starting implementation for issue #{work_number}: {issue_title} (`issue_impl`)... > > Reading requirements and setting up development environment. This may take several minutes. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor ``` ### For `pr_fix` Post comment on the PR: ``` > Starting fix for PR #{work_number}: {pr_title} (`pr_fix`)... > > Addressing review feedback and CI failures. This may take several minutes. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor ``` ## Why Step 1.5 (not Step 0) - Issue/PR is confirmed to exist (no false notifications on nonexistent items) - Title is available for a more informative message - Clone + implementation hasn't started yet (fast notification) ## Affected Files - `.opencode/agents/task-implementor.md` — add Step 1.5 to both procedures ## Subtasks - [ ] Add notification step to `issue_impl` procedure (after read issue, before clone) - [ ] Add notification step to `pr_fix` procedure (after read PR, before clone) ## Acceptance Criteria - User sees a comment within seconds of the implementor starting work - Comment includes work number, title, and work type - Comment includes the bot signature ## Metadata - **Commit Message**: `feat(agents): add work-started notification to task-implementor` - **Branch**: `feature/impl-started-notification`
HAL9000 added this to the v3.7.0 milestone 2026-05-08 15:30:25 +00:00
Owner

Implementation PR Updated

This issue is being implemented in PR #11032.

Update: All compliance items resolved:

  • CHANGELOG.md updated with feature entry under [Unreleased]
  • Milestone assigned: v3.7.0
  • Dependencies documented in PR body

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

## Implementation PR Updated This issue is being implemented in PR #11032. **Update**: All compliance items resolved: - CHANGELOG.md updated with feature entry under `[Unreleased]` - Milestone assigned: `v3.7.0` - Dependencies documented in PR body --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#11031
No description provided.