No Polling Agents
- 462 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
no-polling-agents is a Claude agent skill that keeps background agents running without sleep-loop polling by trusting status-file completion signals for developers orchestrating parallel agent tasks.
About
no-polling-agents is a parcadei continuous-claude-v3 skill that instructs agents how to launch parallel background workers without wasteful polling loops. Background agents write to status files on completion while the parent continues other work, checking results only when needed or when the user asks. The skill explicitly forbids sleep-and-cat polling patterns that burn tokens and block progress. Developers reach for no-polling-agents when running multiple background agents on complex tasks and wanting Claude to stay productive instead of repeatedly checking status files in tight loops.
- Eliminates polling loops in agent workflows
- Enables continuous Claude operation across long-running tasks
- Reduces context-window thrashing from repeated manual interventions
- Supports reliable multi-step agentic processes
- Designed for production-grade agent reliability
No Polling Agents by the numbers
- 462 all-time installs (skills.sh)
- +3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,861 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/parcadei/continuous-claude-v3 --skill no-polling-agentsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 462 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do background agents signal completion without polling?
Keep Claude continuously engaged on complex tasks without manual re-prompting or polling loops.
Who is it for?
Developers running parallel Claude background agents on complex tasks who want non-blocking orchestration without sleep loops.
Skip if: Single-threaded tasks with no background agents or workflows that require synchronous blocking on immediate agent results.
When should I use this skill?
The agent launches parallel background tasks and might otherwise poll status files with sleep loops instead of trusting completion signals.
What you get
Non-blocking parallel agent runs with status-file completion signals and no token-wasting poll loops.
- non-blocking agent orchestration pattern
Files
No Polling for Background Agents
When launching parallel background agents, do NOT poll with sleep loops.
Pattern
Background agents write to status files when complete. Wait for them naturally.
DO
- Launch agents with
run_in_background: true - Continue with other work while agents run
- Check status file only when user asks or when you need results to proceed
- Trust the agent completion system
DON'T
- Run
sleep 10 && cat status.txtin loops - Continuously poll for completion
- Waste tokens checking status repeatedly
- Block on agents unless absolutely necessary
When to Check Status
1. User explicitly asks "are they done?" 2. You need agent output to proceed with next task 3. Significant time has passed and user is waiting
Example
// Launch agents
Task({ ..., run_in_background: true })
Task({ ..., run_in_background: true })
// Continue with other work or conversation
// Agents will write to status file when done
// Only check when needed
cat .claude/cache/status.txtSource
User feedback: "You can just wait until everyone pings you"
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What polling pattern does no-polling-agents forbid?
no-polling-agents forbids sleep-and-cat loops like sleep 10 && cat status.txt that repeatedly check agent status, waste tokens, and block the parent agent unnecessarily.
How should agents wait for background task completion?
no-polling-agents tells agents to launch with run_in_background true, continue other work, and check status files only when the user asks or results are required to proceed.