Early access
See the prompts behind every pull request
Procket records the prompts your engineers send to their AI coding tools, links them to the commits they produced, and shows them on the pull request with their token cost. Reviewers see how the code was made, and you see where AI spend goes.
Free for up to 10 engineers. Then $1 per seat a month.
procketbotcommented on pull request #142
🧾 Procket
3 of 4 commits link to AI prompts · 1 not in the ledger
2 prompts behind the code · 1 engineer · 67,500 billable tokens
Most expensive prompts
| # | Engineer | Tokens | Share | Prompt |
|---|---|---|---|---|
| 2 | alice | 66,000 | 97% | Here's the full test log, why is the import failing? … |
| 1 | alice | 1,500 | 2% | Add pagination to the list endpoint |
Worth a look
- Prompt #2 is 6,200 characters. Pasted logs can usually be replaced by a path or a targeted excerpt.
- Prompt #2 had 2 secret-like values redacted. Avoid pasting credentials.
#1 · alice · 1,500 billable · Add pagination to the list endpoint
Commits: 3f9a2c1 (exact)
Branch when sent: task/pagination
How it works
Set up once, then it runs itself
- 1
Install the GitHub App
Pick your GitHub organisation. Every repository is covered, including new ones. No workflow files, no secrets, nothing to add to each repository.
- 2
Each engineer runs one command
One command covers every repository and AI tool on their machine, then signs them in with GitHub. Nothing to type, once per machine.
- 3
Prompts appear on the pull request
Every PR gets a comment listing the prompts behind its commits and what they cost, updated on each push.
brew install procket-dev/tap/procket
procket setupWindows, Linux, package managers and company-managed rollouts are covered in the install guide.
What you get
The record git doesn't keep
A diff shows what changed. Procket shows the instructions that produced it.
Prompts follow the code, not the branch
Rebases, squash merges, cherry-picks and amended commits all keep their prompts. Engineers can prompt on one branch and commit on another.
See spend that never landed
The team report shows prompts whose changes never reached a commit (dead ends, questions, abandoned experiments), so you can see where tokens go.
Review prompts like code
The costliest prompts are listed first, with hints: pasted logs, runaway context, credentials that had to be redacted.
Tamper-evident
Every record is hash-chained in an append-only store, and each pull request comment publishes the chain's latest hashes on GitHub, where nobody can rewrite them, us included. An edited record shows, and so does a removed one that a comment has published.
Secrets redacted twice
Keys, tokens and passwords are stripped on the engineer's machine before anything is saved or sent, and again on the server.
Never in the way
Hooks never print, never prompt, and can never fail a commit. If the network is down, events wait on the machine and send later.
Built for the people being recorded
Visibility, not surveillance
Procket records what people type at work, so it is built to be something engineers will agree to install.
How we handle your data- Only repositories you connect are recorded. Personal projects on the same laptop never leave it.
- No leaderboards. Engineers see their own prompts in the team report; reviewers see what is on the PR.
- Laptop credentials can write, never read. A stolen laptop exposes nobody's prompts.
- Encrypted at rest, hosted in Ireland, kept for 12 months by default, erased on request.
Free for your first 10 engineers
Then $1 per seat a month. Reviewers and viewers never need a seat.