chat git:20261015.fe6d11dA

Immutable. This exact content never changes and is served at /api/v1/blob/f141386ff188136e.

---
name: chat
description: Messages teammates — `pfm chat call {target} '{one line}'` delivers a turn; `pfm whoami` gives your address. Use for "call the other chat", "ping", or "reply to {session}". Returns a delivery receipt.
---

<!--
HAND-WRITTEN CARD — no generated marker. `engine-sync codex build` preserves it because
chat is a host-level MCP/CLI surface with no project-local Claude command source.
This card carries the one page a Codex lane actually needs mid-flight.
-->

# pfm chat essentials (Codex shape)

Canonical tool: `$HOME/.local/bin/pfm chat`.

## Call

`$HOME/.local/bin/pfm chat call {target} '{one-line message}'`

- `{target}` = exact tmux session name or a pane label; resolution scans every socket. Executor lanes get the orchestrator's address from the BRIEF.
- ONE line per message — make N calls for N lines. Plain text is auto-signed with your reply address; a `/`-prefixed harness command travels unsigned.
- Success prints `called LIVE … Enter confirmed` plus a delivery-proof screen capture — read it; that is your receipt. Queued-on-busy is normal (a busy pane queues your turn).
- exit 3 = the target chat is dead.
- exit 4 = no matching chat; exit 6 = the message was not delivered.

## Who am I

`$HOME/.local/bin/pfm whoami` → your own address; include it in pings so verdicts route back.

## Coordination

Native subagents communicate through `collaboration.send_message` to the parent agent path; the parent waits with `wait_agent`. Separate terminal chats use the `mcp__chat-professor__*` tools or `pfm chat call` with the exact target supplied by the orchestrator. Agent paths such as `/root/...` are mailbox addresses, never terminal-chat targets. A delivery failure is reported to the caller with the failed target; no event spool is consumed by the harness.

## Boundaries

- `chat call` rejects `/compact`: pfm never types a compaction. Check `pfm chat call --help` for supported delivery flags.
- Never capture or scrape another pane to infer state — ping and ask; the orchestrator rules from reports.