tclaude

Author and edit tclaude group templates (a.k.a. summoning circles / task forces) by talking to a scribe agent, via `tclaude agent templates`. Covers the template JSON wire shape, the safe show-json → edit → edit-file → show round-trip, which permission slugs a scribe needs (templates.manage, and roles.manage / profiles.manage only when touching the shared registries), and the wizard-mode vocabulary (circle/party/rite/quest/drumbeats) a human may speak. Use when asked to create, edit, inspect, rename, delete, snapshot, export/import, or reason about a group template / summoning circle — or when a human describes a team blueprint in wizard words.

Coordinate with other tclaude-managed Claude Code or Codex CLI conversations via `tclaude agent`. Routes through a `tclaude agentd` daemon (the human starts it; you don't). Use when you've been put in a group with peer agents and need to look them up, send them messages, or read messages they sent you. Triggered by a `[system: new agent message #...]` line appearing in your conversation, or when the user explicitly asks you to talk to another agent.

Present a pull request intentionally in the tclaude operator dashboard via `tclaude agent present-pr <url>`. Use when you have opened or updated a PR and want the human/operator to see it even if branch/statusline PR detection has not picked it up. Requires `self.pr` for your own PR (default-granted by `tclaude setup --install-default-agent-permissions`); manager pattern: `tclaude agent present-pr <url> --target <peer>` requires `agent.pr`, OR ownership of a group containing the target.

Manage your own context window via `tclaude agent context-info`, `compact`, `reincarnate`, and `clone`. Use when you need context pressure details, a /compact injection, a fresh successor that inherits identity, or a sibling agent that keeps the original running. `reincarnate` requires a follow-up so the new pane is not idle. Context thresholds and cadence are project/operator policy; this skill documents the capability, not when to invoke it. Manager pattern: every verb accepts `--target <peer>` to act on another agent (requires the matching `agent.<verb>` slug, OR ownership of a group containing the target).

Reincarnate NOW — replace yourself with a fresh successor that inherits your identity (groups, permissions, ownerships) via `tclaude agent reincarnate`. This is the do-it-now procedure: checkpoint your task state to a handoff file, then hand off. Use when the human types `/reincarnate` (optionally followed by a focus for the successor), asks you to reincarnate / hand off to a fresh instance, or you have already decided to act on a full context window. For the full lifecycle reference — compact vs. clone trade-offs, when-to-act policy, and the `--target` manager pattern — see the `agent-lifecycle` skill.

Copy text to the HUMAN's system clipboard via `tclaude agent clipboard` — for when the human asks you to put a draft, command, or snippet on their clipboard. The `tclaude agentd` daemon runs the platform copy tool on the host (your sandbox can't reach the display). Permission-gated on the `human.clipboard` slug: NOT granted by default and NOT implied by group ownership, so you need an explicit grant or a per-call `--ask-human` popup approval. Use when the human says "copy this to my clipboard / put X on my clipboard". NOT for agent-to-agent data passing — that is `agent-coord`.

Reach the human via `tclaude agent notify-human "<message>"` — the message lands in the agentd dashboard's Messages tab, where the human reads it off the busy terminal. Permission-gated on the `human.notify` slug (group owners also pass); the human grants the slug to a trusted coordinating agent (e.g. the PO), so an agent with neither the slug nor group ownership cannot post to the channel. Use to send the human status updates or questions that need a human decision. NOT for agent-to-agent messaging — that is the `agent-coord` skill.

Set, clear, or show an agent's task-reference link — the clickable URL (a Linear issue, GitHub issue/PR, ticket, …) shown in the dashboard's Task column next to each agent — via `tclaude agent task set|clear|show`. Use to record what work item YOU are on (`self.task`, default-granted), or, when spawning workers, to point each one at its issue: `tclaude agent spawn --task <url>`. Manager pattern: `tclaude agent task set <url> --target <peer>` sets ANOTHER agent's link (requires the `agent.task` slug, OR being an owner of a group containing the target).

Schedule recurring nudges and check-ins via `tclaude agent cron {ls, add, rm, logs}`. The agentd scheduler ticks every 30s and fires due jobs as agent_messages (when sender + target share a group) or direct tmux send-keys (solo target). Use to set up periodic status pings to peer agents (e.g. a Product Owner agent pinging workers every 10 minutes), self-check-ins, or any task that's currently a `/loop` or external cron. Self-targeted scheduling needs `self.schedule` (default-granted alongside the other self-lifecycle slugs); cross-agent scheduling needs `agent.schedule` OR being an owner of a group containing the target.

Toggle your own Claude Code Remote Access on/off via `tclaude agent remote-control [on|off|toggle|status]`. tclaude agentd injects Claude Code's `/remote-control` toggle into your pane, exposing the running session to claude.ai/code + the Claude mobile app (after a claude.ai login), gated on the `self.remote-control` permission. Use when the user asks to enable/disable remote access, reach this session from their phone or the Claude app, or check whether it's currently reachable (`status`). Codex CLI has no built-in remote access, so this is Claude-Code-only. Manager pattern: `--target <peer>` toggles ANOTHER agent's remote access (requires the `agent.remote-control` slug, OR being an owner of a group containing the target).

Rename your own tclaude-managed conversation via `tclaude agent rename "<title>"`. tclaude agentd applies the harness-specific rename path on your behalf (Claude Code uses `/rename` injection; Codex CLI updates its title store), gated on the `self.rename` permission. Use when the user asks you to rename the conversation/session/agent, or when you decide to give yourself a clearer name (e.g. after taking on a new role in a group). Manager pattern: `tclaude agent rename "<title>" --target <peer>` renames ANOTHER agent (requires the `agent.rename` slug, OR being an owner of a group containing the target).

Report — or open a terminal in — the directory an agent is working in, via `tclaude agent dir`. A tool-using agent cannot read tclaude's "where am I building" state or spawn a terminal window from a tool; tclaude agentd tracks the most-recent dir you've edited files in (the PostToolUse hook records it) and, being outside your sandbox, can open a terminal there. Use when the user asks "what directory are you working in / building in", "where are you", "open a terminal here / in the repo", or "/agent-dir". Manager pattern: `tclaude agent dir <peer>` reports another agent's dir; `tclaude agent dir <peer> --open` opens a terminal in it.

Review the diff when a task is finished.