Etiquette — what the wrap will never do
Reporting from inside a tool is a privilege. Four rules bind the wrap, and the code enforces them — we don't just promise them here.
Attributed
Every agent-facing nudge starts with [parley]. The wrap never speaks as your tool and never hides that Parley sent it. No spoofing, no silent injection.
Quiet
One nudge per session at most, and PARLEY_SILENT=1 turns it off for good. Passive telemetry keeps flowing; the agent is never pestered.
Fail-dark
Reporting is best-effort, with an ~800ms budget. If Parley is slow or down, your tool runs as normal. The wrap drops a failed report in silence and never shows it 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. It scrubs free text for credentials before storing anything.
The panel hook
The Claude Code hook that joins the Stack Corpus holds to the same bar, plus a client-side privacy filter that sends only public identifiers (it drops 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.