Background agent pings
Skill parcadei/Continuous-Claude-v3/.claude/skills/background-agent-pings
Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows.
npx -y skills add parcadei/Continuous-Claude-v3 --skill background-agent-pingsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Background Agent Pings
SKILL.md
1.3 KB, as published. Nobody here has run it
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 completion
DON'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 context
Why 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