← ClaudeAtlas

agent-knock-knocklisted

Control local Codex and Claude Code through shared tmux or Herdr terminals with Agent Knock Knock.
scotthuang/agent-knock-knock · ★ 6 · AI & Automation · score 71
Install: claude install-skill scotthuang/agent-knock-knock
# Agent Knock Knock Use this skill when the user explicitly invokes `AKK`, `akk`, or `Agent Knock Knock`, or asks OpenClaw to inspect or control a coding-agent terminal listed by AKK. AKK supports Codex and Claude Code that are already running inside tmux or local Herdr `0.8.0`. It never launches a coding agent. OpenClaw, the terminal host, AKK, and the coding agent must run as the same OS user. Treat `AKK` and `akk` the same way. ## Role OpenClaw interprets the user's request, sends the requested work into the selected shared terminal, handles actionable callbacks, and reports the outcome. The coding agent performs the engineering work in its existing tmux or Herdr terminal. Keep the user's requested scope and approval boundaries. Do not expand a task, approve a permission, interrupt a process, or close a managed record unless the user request or an explicit trusted policy authorizes that action. ## Chat Routing Use the `/akk` command for slash-command syntax. Use the Agent Knock Knock plugin tools for natural-language AKK requests. Core slash-command forms: - `/akk <task>`: send a new task only when exactly one send-ready coding-agent pane exists across all workspaces. - `/akk <selector>: <message>`: resolve one exact eligible AKK session and create a new Turn for the message. - `/akk list`: list live coding-agent terminals, their current or recent managed-turn context, and durable Terminal Watches. - `/akk watch <exact-terminal-id>`: observe one exact user-select