pd say <content>
Fan one status message out to notes plus optional tuple, pheromone, inbox, or broadcast targets.
Run pd say <content> like this
pd say "Scope: CLI docs detail coverage"Command contract
pd say <content>
/docs/cli/say
Sessions, Notes, Recovery, And Evidence
daemon-backed CLI command
cli/commands/sugar.ts, cli/commands/sessions.ts, cli/commands/say.ts, cli/commands/look.ts, cli/commands/sitrep.ts, cli/commands/resurrection.ts
none
human display with command-specific state changes
generated API spec from the source-backed catalog
This clip shows the daemon health check, command discovery, and message-loop patterns that recur across the CLI reference. Here it grounds the pd say <content> reference: daemon health, discovery, and message-loop patterns these pages keep pointing back to.
Common ways this command shows up in practice
pd say <content> belongs to Sessions, Notes, Recovery, And Evidence. Create the audit trail: sessions, file claims, notes, activity, briefing, salvage, and catch-up commands.
daemon-backed CLI command. Validate live behavior from the daemon and handler source when changing this command.
Use this page as the stable public contract for pd say <content>; aliases resolve to the same contract.
Examples
Run pd say <content> from a coordinated checkout
pd say "Scope: CLI docs detail coverage"
Runs the pd say <content> command family and prints the resulting Port Daddy state, ids, or readiness/error details.
Find this command from the full CLI reference
pd help sayopen /docs/cli/say
The help topic and docs route both describe pd say <content>, including aliases, flags, and source provenance.