# AI use cases for Frog (wevm/frog) Repo: [wevm/frog](https://github.com/wevm/frog) | Use cases: 4 | Page: https://dedupedai.com/use-cases/wevm-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. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Log agent friction and report it as a GitHub issue: https://dedupedai.com/use-cases/wevm-frog/log-friction-and-report-as-issue/ - Report friction in a dependency to its maintainers: https://dedupedai.com/use-cases/wevm-frog/report-friction-to-dependency-maintainers/ - Share one friction log across agents in PostgreSQL: https://dedupedai.com/use-cases/wevm-frog/share-friction-log-in-postgres/ - Accept friction reports from other repositories: https://dedupedai.com/use-cases/wevm-frog/accept-friction-reports-from-other-repos/ ## How to log agent friction and report it as a GitHub issue with Frog Repo: [wevm/frog](https://github.com/wevm/frog) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Record a friction entry in the repo so the next agent reads it and an owner gets an issue. **Who it is for:** A developer whose coding agent keeps working around the same tool or config problem and wants the workaround written down and assigned. **The problem:** Workarounds go unrecorded, so each new agent rediscovers the same friction from nothing and nobody who can fix it hears about it. **The outcome:** A committed entry directory in .agents/friction-log/ that is reported as an issue, and deleted once that issue closes. ### Steps 1. Run `npm install -g frog` or use the standalone installer from the README. 2. Run `frog init` in the repository to create the friction log, config, and issue form. 3. Run `frog log --publish` so the entry is reported as an issue immediately. (inferred, check the README) 4. Run `frog list` to confirm the entry is listed and shows that it has been reported. 5. After the issue closes, run `frog sync`, then `frog publish` if needed, and review the pull request that deletes the resolved entry. (inferred, check the README) ### Prompt to paste into your agent ```text In the frog repository at , 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. ``` ### Caveat The README says to choose one automation method per repository, because running both can create duplicate issues. Risk, credentials: Choosing the Frog GitHub App or Action-only mode changes repository access, so confirm the choice with the user before installing the App or adding the workflow. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wevm-frog/log-friction-and-report-as-issue/ ## How to report friction in a dependency to its maintainers with Frog Repo: [wevm/frog](https://github.com/wevm/frog) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Send a friction entry to an upstream project that has opted in, using its issue form. **Who it is for:** A developer whose agent hits a bug or rough edge in an npm dependency and wants the maintainers to receive a structured report. **The problem:** Friction caused by a dependency stays in the local repository, so the project that could fix it never hears about it. **The outcome:** A friction entry targeted at an opted-in project, scaffolded from that project's GitHub issue form. ### Steps 1. Run `frog targets` to list the dependencies that accept friction reports. 2. Run `frog log --target viem` with the dependency name from the list, replacing viem with your target. 3. Fill in the prompts so the scaffolded entry answers the target project's issue form questions. 4. Run `frog list` to check that the entry shows its target. 5. Run `frog publish` to report the pending entry to the target project. ### Prompt to paste into your agent ```text In the frog repository, run `frog targets` and then `frog log --target ` 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. ``` ### Caveat A dependency only receives reports if it has opted in through its repository, so a target missing from `frog targets` cannot be reported to with this workflow. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wevm-frog/report-friction-to-dependency-maintainers/ ## How to share one friction log across agents in PostgreSQL with Frog Repo: [wevm/frog](https://github.com/wevm/frog) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Store friction entries in a shared PostgreSQL database that several agents can read and write. **Who it is for:** A team running several agents or applications that need to record and inspect the same friction history. **The problem:** A friction log kept in one repository's files is hard for several agents and applications to record to and inspect together. **The outcome:** Friction entries stored in a shared PostgreSQL database, listed from the same command for every agent that connects. ### Steps 1. Set your PostgreSQL connection string with `export FROG_DATABASE_URL=postgres://...`, replacing the placeholder with your own value. 2. Run `frog migrate` to create or upgrade the selected store. 3. Run `frog list` to confirm the agents can read the shared entries. 4. Point each agent or application at the same connection string through its own configuration, using the Store.postgres({ connectionString }) factory from the README. (inferred, check the README) ### Prompt to paste into your agent ```text In the frog repository, set FROG_DATABASE_URL to the team's PostgreSQL connection string, run `frog migrate`, then `frog list`. Expected output: the store is created or upgraded and the list shows entries from the shared database. Verify that the list command exits without error. ``` ### Caveat The README lists PostgreSQL as the only available database, with SQLite and Cloudflare D1 marked as coming soon. Risk, credentials: The connection string grants database access, so keep it in an environment variable or secret store and do not commit it to the repository. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wevm-frog/share-friction-log-in-postgres/ ## How to accept friction reports from other repositories with Frog Repo: [wevm/frog](https://github.com/wevm/frog) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Turn on inbound reports so other repositories can send friction to your project. **Who it is for:** A maintainer of a library or application whose users' agents hit friction and should be able to report it back. **The problem:** Friction reported by people or agents using a project has no way to reach that project's own friction log. **The outcome:** A project that accepts inbound friction reports from other repositories through its config. ### Steps 1. Run `frog init` in the project, which enables inbound reports by default. 2. Check that .agents/friction-log/config.json contains "inbound" with "enabled": true. 3. If you do not want inbound reports, run `frog init --no-inbound` in a fresh initialization instead. (inferred, check the README) 4. Run `frog list` to confirm the friction log is in place. ### Prompt to paste into your agent ```text 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/wevm-frog/accept-friction-reports-from-other-repos/