What do you want to do?
4 use cases
-
Log agent friction and report it as a GitHub issue
Record a friction entry in the repo so the next agent reads it and an owner gets an issue.
- REPO
wevm/frog - Software and DevOps
- Intermediate
View prompt
In the frog repository at <project path>, run `frog log --publish` to record the friction the agent just hit. Expected output: a new directory under .agents/friction-log/ with friction.md, plus a reported issue. Verify by running `frog list` and confirming the new entry shows as reported.
- REPO
-
Report friction in a dependency to its maintainers
Send a friction entry to an upstream project that has opted in, using its issue form.
- REPO
wevm/frog - Software and DevOps
- Intermediate
View prompt
In the frog repository, run `frog targets` and then `frog log --target <package>` for the dependency that caused the friction. Expected output: a targeted entry scaffolded from that project's issue form. Verify by running `frog list` and checking that the entry shows the target package.
- REPO
-
Accept friction reports from other repositories
Turn on inbound reports so other repositories can send friction to your project.
- REPO
wevm/frog - Software and DevOps
- Beginner
View prompt
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.
- REPO
Quick start with Frog
- Check you have what it needs: 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.
- Open wevm/frog on GitHub and read the README and license.
- Run
npm install -g frogor use the standalone installer from the README. - Run
frog initin the repository to create the friction log, config, and issue form. - Run
frog log --publishso the entry is reported as an issue immediately. (inferred, check the README) - Run
frog listto confirm the entry is listed and shows that it has been reported.
These steps come from our top use case, Log agent friction and report it as a GitHub issue, which also has a copy-paste agent prompt.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for wevm/frog
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 freeAbout this repo
- Who it is forDevelopers and teams whose AI agents keep hitting the same friction in their repositories or dependencies and need that friction recorded and owned.
- Why it is hot267 stars
- LanguageTypeScript
- Sourcegithub.com/wevm/frog · Back to Hot repos
Requirements
- 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
Add this badge to your README
Maintain Frog? Show readers where to find these use cases.
Markdown
[](https://dedupedai.com/use-cases/wevm-frog/?utm_source=github&utm_medium=badge&utm_campaign=wevm-frog)
HTML
<a href="https://dedupedai.com/use-cases/wevm-frog/?utm_source=github&utm_medium=badge&utm_campaign=wevm-frog"><img src="https://dedupedai.com/badge/wevm/frog.svg" alt="Use cases on Deduped" height="20"></a>
A static image, no tracking script. About the badge
Questions about Frog
What is Frog?
Frog is a TypeScript command line tool that lets AI agents record friction they hit as committed entries, report them as GitHub issues, and remove them once resolved. It is an open-source project on GitHub: https://github.com/wevm/frog.
How do I use Frog?
Run npm install -g frog or use the standalone installer from the README; then run frog init in the repository to create the friction log, config, and issue form; run frog log --publish so the entry is reported as an issue immediately. The use cases on this page give the full steps and a copy-paste agent prompt for each job.
Who is Frog for?
Developers and teams whose AI agents keep hitting the same friction in their repositories or dependencies and need that friction recorded and owned.
What can I do with Frog?
4 use cases so far, for example: Log agent friction and report it as a GitHub issue; Report friction in a dependency to its maintainers; Share one friction log across agents in PostgreSQL. Each has steps and a copy-paste agent prompt.
What do I need to run Frog?
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.
What are alternatives to Frog?
Other hot AI repos in Software and DevOps: Deep Infer, Harness2, Orca, Opencode, Graphify.
Is Frog safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.