Who it is forA maintainer of a library or application whose users' agents hit friction and should be able to report it back.
The problemFriction reported by people or agents using a project has no way to reach that project's own friction log.
The outcomeA project that accepts inbound friction reports from other repositories through its config.
What you need first
- A GitHub repository for the project that the agent works in
- npm, pnpm, bun, or yarn, or the standalone executable from the install script
- A choice between the Frog GitHub App and Action-only mode, made with the user before access is changed
- A PostgreSQL connection string, only if you want a shared database store
Steps
- Run
frog initin the project, which enables inbound reports by default. - Check that .agents/friction-log/config.json contains "inbound" with "enabled": true.
- If you do not want inbound reports, run
frog init --no-inboundin a fresh initialization instead. (inferred, check the README) - Run
frog listto confirm the friction log is in place.
Prompt for your agent
In the frog repository, run `frog init`, then open .agents/friction-log/config.json and confirm the inbound setting is enabled. Expected output: a config file with inbound.enabled set to true. Verify by reading that file and running `frog list` without errors.
Caveat. The README says inbound reports are enabled by default on Frog init, so projects that do not want them must pass --no-inbound.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for wevm/frog and "Accept friction reports from other repositories"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer