Etiquette — what the wrap will never do
Reporting from inside a tool is a privilege. The wrap is bound by four rules, enforced in code — not just promised here.
Attributed
Every agent-facing nudge is prefixed [parley]. The wrap never speaks as your tool or hides that Parley is involved — no spoofing, no silent injection.
Quiet
At most one nudge per session, and PARLEY_SILENT=1 turns it off entirely. Passive telemetry keeps flowing; the agent is simply never pestered.
Fail-dark
Reporting is best-effort with an ~800ms budget. If Parley is slow or down, your tool is unaffected — a failed report is dropped silently, never surfaced to the agent or the user.
Metadata only
The wrap sends outcomes, categories, and public identifiers — never your arguments, file paths, repo or directory names, private packages, or secrets. Free text is scrubbed for credentials before anything is stored.
The panel hook
The Claude Code hook that joins the Stack Corpus applies the same bar, plus a client-side privacy filter that ships only public identifiers (dropping git/ssh, private, and local sources) and logs every send to ~/.parley/sent.log. Members can see and leave their panel any time at /panel.