For the team
Anyone on the team can ask the code. The engineers keep coding.
Everyone has questions only the code can answer, and today asking one means interrupting an engineer. With a team host, you ask in a Slack channel you’re already in, without creating an account, and the answer comes back footed with the commit it was read from.
Product managers
@PRCHD is the export limit still 500 rows, and where is it enforced?
Product questions get answered from the code, without booking an engineer.
Engineering managers
@PRCHD what’s changed on main since Friday, and what’s risky in it?
The status an engineering manager currently assembles by asking five people assembles itself.
Founders and CTOs
@PRCHD how hard would it be to support a second currency?
Leadership gets ground truth directly, at 22:00, without pulling anyone off anything.
Support and QA
@PRCHD a customer says CSV export drops the last row — is that possible in the current code?
The first-line answer comes from the code, names its commit, and takes a minute.
On-call and incident response
@PRCHD this stack trace [paste] — which commit last touched the line it dies on?
The alert arrives already triaged, attributed, and written up.
Designers
@PRCHD are the new empty states live on main, and what do they look like?
Design QA happens against the real app, without waiting for a build or an engineer.
Data and analytics
@PRCHD signups dropped 12% on Tuesday — did anything ship that touches the signup path?
Analytics questions and code questions become one investigation.
Docs and technical writing
@PRCHD is the rate-limit number in our docs the number in the code?
Doc drift gets caught on a schedule, not by a customer.
Security and compliance
@PRCHD which endpoints skip the auth middleware?
Security questions get answered from the code, not from a spreadsheet of what someone believed it did.
The recipes on these pages are examples a team writes for itself, not a library that ships with PRCHD. The product supplies the engine — a stored prompt, a posture, and four ways to fire it — and a team adds a recipe in a minute.
How access works
The Slack channel is the access list.
Access is the channel membership you already manage. Everyone in a bound channel has the same reach, and PRCHD adds no accounts, roles, or per-person permissions on top.
- Bind an exec channel ask-only, and leadership can ask anything while the code stays exactly as it was
- Enable runs on a private engineering channel, and that room can start recipes
- Public channels ask; running a recipe takes a private channel the operator enabled
- Remove someone from the channel, and their access goes with it
Where your code lives
The computer you own is the computer that runs.
Repositories, worktrees, prompts, transcripts, diffs, command output, attachments, environment values, and the event log stay on the computer you installed PRCHD on — the one that already has your code and your tools. The agent works there, so there is nothing to copy into a hosted environment and nothing uploaded to be indexed.
One small public service handles what a computer with no open port can’t do on its own: it enrolls your computer’s identity, forwards short push notifications, and holds webhook deliveries until your computer collects them. Each delivery is sealed to your computer’s public key the moment it arrives, so the service only ever holds ciphertext, and it is never in the path of your work.
One person installs it. Everyone else just asks.
The operator sets up PRCHD on a shared computer in an afternoon. For everyone else, the whole product is a Slack channel they’re already in.