메뉴
Use to discover which coding agents are running in tmux, find agents relevant to the current repo, check what they're working on, and coordinate or control them. Run before starting work to avoid conflicts, or to send commands to other agents.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Standalone Speedrift-native planning and Workgraph compilation. PlanForge V2 uses a model-mediated planner persona, validated schema, critic pass, and Speedrift module/model assignment to produce an executable Workgraph with tests, evals, drift gates, and fix loops. Use directly when you need discovery, decomposition, or an end-to-end Speedrift execution graph.
Use when agents need Google Workspace access across Drive, Docs, Sheets, Calendar, Slides, Tasks, People, or related GWS services; choose the correct gws-account profile before using gws CLI or domain-specific gws-* skills. Do not use Python gspread/googleapiclient or custom OAuth. Use msgvault for email search/reading.
gws CLI shared reference. Use before any gws-* skill to choose the correct gws-account profile, avoid raw gws config drift, and apply shared Drive flags, auth checks, output formatting, and security rules.
Use when a local Pi agent needs administrator privileges, a password-protected command, or approval for global or ambiguous deletion
Workgraph-first drift-control autopilot (driftdriver + coredrift + optional specdrift/datadrift/depsdrift/uxdrift/therapydrift/yagnidrift/redrift) with optional Amplifier runtime integration. Use for start/resume, dependency-aware execution, and keeping code/spec/intent synced without hard blocks.
Use when managing projects, programs, initiatives, dependencies, schedules, Workboard/PAIA Program tasks, Linear/GitHub/Google/Folio work, cross-system planning, weekly operating reviews, stale work rescue, operational task decomposition, or research-backed planning for Braydon's work. Covers a model-mediated program panel, research/evidence discovery, model-authored records, HTML inspection packets, change plans, approval gates, and execution ledgers.
| name | tmux-monitor |
| description | Use to discover which coding agents are running in tmux, find agents relevant to the current repo, check what they're working on, and coordinate or control them. Run before starting work to avoid conflicts, or to send commands to other agents. |
Discover and coordinate coding agents running across tmux sessions.
# Agents in current repo (uses cwd)
tmux-monitor status
# Agents in a specific repo
tmux-monitor status --repo driftdriver
# JSON for programmatic parsing
tmux-monitor status --json
# All agents including unrelated repos
tmux-monitor status --all
The JSON output includes a pane_id field. Use it to send commands:
tmux send-keys -t %272 "your command" Enter
# List all sessions
tmux-monitor sessions
# View a pane's log output
tmux-monitor logs "fresh_7.1"
# Run a single heartbeat cycle
tmux-monitor heartbeat
| Field | Meaning |
|---|---|
session | tmux session name |
pane | Window.pane identifier (e.g., fresh:7.1) |
pane_id | tmux internal ID for send-keys control (e.g., %298) |
type | Agent type: codex, claude-code, opencode, kilocode, pi-dev, shell, idle |
title | Pane title from tmux (often shows current task or repo) |
relevance | same_repo / related / unrelated |
current_task | LLM-extracted task description |
summary | LLM-generated paragraph summary of recent activity |
controllable | Whether the agent can receive tmux send-keys commands |
tmux-monitor status --jsonrelevant_count > 0: Read the existing agent's current_task and summarytmux send-keys or deferStatus file: ~/.local/share/driftdriver/tmux-monitor/status.json
Pane logs: ~/.local/share/driftdriver/tmux-monitor/panes/
Daily events: ~/.local/share/driftdriver/tmux-monitor/daily/