# No Polling Agents

> Never poll background agents with sleep loops; continue working and check status files only when needed. Use when tempted to loop-wait on agents. Trigger phrases: "stop polling agents", "sleep loop waste", "agent completion check".

- Skill: `dojogenesis/no-polling-agents` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dojogenesis/no-polling-agents`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dojogenesis/no-polling-agents/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: DojoGenesis (https://skillmd.com/u/dojogenesis)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dojogenesis/no-polling-agents

---


# 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.txt` in 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

```typescript
// 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.txt
```

## Source

User feedback: "You can just wait until everyone pings you"