How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-auto-context:run-workerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Auto Context 워커를 수동 실행하거나 상태를 확인한다.
Auto Context 워커를 수동 실행하거나 상태를 확인한다.
LOCK=".claude-auto-context/worker.lock"; if [ -f "$LOCK" ]; then PID=$(cat "$LOCK"); if kill -0 "$PID" 2>/dev/null; then echo "RUNNING (pid=$PID)"; else echo "STALE LOCK (pid=$PID, not alive)"; fi; else echo "NOT RUNNING"; fisqlite3 .claude-auto-context/db/claude-auto-context.db "SELECT count(*) FROM raw_events WHERE status='pending'" 2>/dev/null || echo "DB not found"!tail -5 .claude-auto-context/db/worker.log 2>/dev/null || echo "No log file"
Arguments: $ARGUMENTS
status — 위 Current Status 섹션 정보를 보여주고 끝logs — tail -30 .claude-auto-context/db/worker.log 실행하여 최근 로그 출력force — 강제 재시작:
a. Lock file에서 PID 읽어서 kill $PID 실행
b. Lock file 삭제: rm -f .claude-auto-context/worker.lock
c. scripts/worker-launcher.sh 실행 (현재 프로젝트 디렉토리를 인자로 전달)
d. 2초 후 lock file 확인하여 시작 여부 보고scripts/worker-launcher.sh 실행 후 상태 확인워커 실행 시 반드시 이 명령을 사용:
./scripts/worker-launcher.sh "$(pwd)"
직접 bun .claude-auto-context/worker.mjs를 실행하지 말 것 — launcher가 lock file, 환경변수(CLAUDECODE unset), 로그 리다이렉트를 처리한다.
npx claudepluginhub getklaim/claude-auto-context --plugin claude-auto-contextLaunches and manages Claude Code, Codex, or Pi worker sessions as sub-processes. Useful for project managers that delegate tasks, assign work, monitor progress, review tool calls, and collect results via the `csd` CLI.
Provides expert guidance for Vercel Workflow DevKit when building durable workflows, long-running tasks, API routes, or agents needing pause/resume, retries, step execution, or crash-safe orchestration.
Dispatches workers from controller side: opens workers, checks targeted status, replies via agent-team CLI commands like `agent-team worker open` and `agent-team reply`. Useful for managing workers before replying.