DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to log agent friction and report it as a GitHub issue with Frog

Record a friction entry in the repo so the next agent reads it and an owner gets an issue.

Short answer: 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. All steps.

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.

Who it is forA developer whose coding agent keeps working around the same tool or config problem and wants the workaround written down and assigned.

The problemWorkarounds go unrecorded, so each new agent rediscovers the same friction from nothing and nobody who can fix it hears about it.

The outcomeA committed entry directory in .agents/friction-log/ that is reported as an issue, and deleted once that issue closes.

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

  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 for your agent

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.

Caveat. The README says to choose one automation method per repository, because running both can create duplicate issues.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for wevm/frog and "Log agent friction and report it as a GitHub issue"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer