Background Agent Pings
- 482 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
background-agent-pings is a Claude Code agent skill that teaches developers to rely on system reminder notifications for background subagent progress instead of polling Task output.
About
background-agent-pings is a non-user-invocable Claude Code skill from parcadei/continuous-claude-v3 that defines a trust-the-reminder pattern for background agent orchestration. When a developer launches Task with run_in_background=true and specifies an output path such as .claude/cache/agents/<type>/output.md, the skill instructs the agent to immediately continue unrelated work rather than poll. System reminders surface progress signals—new tools used, token counts, and output-file writes—so the agent checks the output file only when notified. Developers reach for background-agent-pings when running parallel specialist subagents during long builds, refactors, or research without blocking the primary session thread.
- background-agent-pings
Background Agent Pings by the numbers
- 482 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #859 of 4,347 Backend & APIs 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 background-agent-pingsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 482 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you avoid polling background Claude agents?
Use background-agent-pings for development tasks
Who is it for?
Developers running multiple parallel Claude Code background agents who want uninterrupted main-session work without manual status polling.
Skip if: Developers who need synchronous subagent results before any next step, or environments without background Task and system reminder support.
When should I use this skill?
A background Task is launched with run_in_background=true and the agent is tempted to poll or block waiting for subagent completion.
What you get
Non-blocking background Task runs, system-reminder-driven progress checks, and output files read only when notified.
- background subagent output files
- non-blocking parallel agent sessions
Files
Background Agent Pings
Trust system reminders as agent progress notifications. Don't poll.
Pattern
When you launch a background agent, continue working on other tasks. The system will notify you via reminders when:
- Agent makes progress:
Agent <id> progress: X new tools used, Y new tokens - Agent writes output file (check the path you specified)
DO
1. Task(run_in_background=true, prompt="... Output to: .claude/cache/agents/<type>/output.md")
2. Continue with next task immediately
3. When system reminder shows agent activity, check if output file exists
4. Read output file only when agent signals completionDON'T
# BAD: Polling wastes tokens and time
Task(run_in_background=true)
Bash("sleep 5 && ls ...") # polling
Bash("tail /tmp/claude/.../tasks/<id>.output") # polling
TaskOutput(task_id="...") # floods contextWhy This Matters
- Polling burns tokens on repeated checks
TaskOutputfloods main context with full agent transcript- System reminders are free - they're pushed to you automatically
- Continue productive work while waiting
Source
- This session: Realized polling for agent output wasted time when system reminders already provide progress updates
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
What does background-agent-pings do?
background-agent-pings teaches Claude Code agents to treat system reminders as progress notifications for background Tasks. Instead of polling, the main agent continues other work and reads the subagent output file only when a reminder reports activity.
Where should background agent output be written?
background-agent-pings specifies output paths like .claude/cache/agents/<type>/output.md. When a system reminder signals the subagent wrote that file, the main agent reads it rather than checking repeatedly.