Skip to content

fix: replace arbitrary 5-minute pulse time budget with goal-based completion #2466

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
marcusquinn merged 1 commit into from
Feb 27, 2026
Merged

fix: replace arbitrary 5-minute pulse time budget with goal-based completion #2466

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 2 additions & 2 deletions .agents/scripts/commands/pulse.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You are an intelligent supervisor, not a script executor. The guidance below tel

**Speed over thoroughness.** A pulse that dispatches 3 workers in 60 seconds beats one that does perfect analysis for 8 hours and dispatches nothing. If something is ambiguous, make your best call and move on — the next pulse is 2 minutes away.

**Time budget: 5 minutes max.** If you've been running longer than 5 minutes, you're overthinking. Wrap up what you have and exit. The next pulse will handle anything you missed.
**Run until the job is done, then exit.** The job is done when: all ready PRs are merged, all available worker slots are filled, TODOs are synced, and any systemic issues are filed. That might take 30 seconds or 10 minutes depending on how many repos and items there are. Don't rush — but don't loop or re-analyze either. One pass through the work, act on everything, exit.

## Step 1: Check Capacity

Expand Down Expand Up @@ -133,5 +133,5 @@ Output a brief summary of what you did (past tense), then exit.
3. **NEVER use `claude` CLI.** Always `opencode run`.
4. **NEVER include private repo names** in public issue titles/bodies/comments.
5. **NEVER exceed MAX_WORKERS.** Count before dispatching.
6. **NEVER run longer than 5 minutes.** Exit and let the next pulse continue.
6. **Do your job completely, then exit.** Don't loop or re-analyze — one pass through all repos, act on everything, exit.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot Feb 27, 2026

Choose a reason for hiding this comment

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

medium

The phrase "Do your job completely, then exit." is more direct and actionable than the original. To ensure 'completely' is well-understood, add a bullet-pointed list clarifying the specific criteria for job completion.

7. **NEVER ask the user anything.** You are headless. Decide and act.
Loading