
Principle Never Block On The Human
- 399 installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
When credentials, approvals, or missing context appear, continue with safe defaults, parallel prep, and documented assumptions instead of stalling the task.
About
Establishes an autonomy rule for Cursor agents: never halt execution solely because a human has not replied—pursue verifiable progress, record assumptions and blockers clearly, and keep momentum while flagging what truly requires human decision or secrets.
- Continue with safe assumptions
- Prepare parallel fallback paths
- Log blockers for human follow-up
- Avoid idle waiting loops
- Resume when input arrives
Principle Never Block On The Human by the numbers
- 399 all-time installs (skills.sh)
- Ranked #1,970 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill principle-never-block-on-the-humanAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 399 |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
What it does
When credentials, approvals, or missing context appear, continue with safe defaults, parallel prep, and documented assumptions instead of stalling the task.
Files
Never Block on the Human
The human supervises asynchronously. Agents must stay unblocked: make reasonable decisions, proceed, and let the human course-correct after the fact. Code is cheap. Waiting is expensive.
Why: Every permission pause stalls the pipeline and makes the human the bottleneck. Since code changes are reversible and reviewable, a wrong decision usually costs less than blocking.
Pattern:
- Proceed, then present. Do the work, show the result. Don't ask "should I do X?" Do X, explain why.
- Reserve questions for genuine ambiguity. Ask only when you truly cannot infer intent from context.
- Make the system self-healing. When you notice a problem, log it and fix it in the next round.
- Supervision is async. The human reviews plans, diffs, and changes on their own schedule. Design workflows for review-after-the-fact.
- Code is cheap, attention is scarce. A wrong implementation costs minutes to fix. A blocked agent costs the human's attention to unblock.
Boundaries:
- Irreversible actions (force-push, delete production data, send external messages) still require confirmation.
- Reversible actions (write code, edit notes, split tasks) should proceed without blocking.
- Product direction comes from the human; execution should not block.