Skip to content
FeedbotFeedbot Docs

Agent reports & CLI

Not every agent speaks MCP. Feedbot gives you two file-based options that work with any agent. Both are available on Pro and Business.

CLI

Section titled “CLI”

Put your API key in .env:

.env
FEEDBOT_API_KEY=fb_live_...

Pull open issues into the repo:

Terminal window
npx feedbot pull

This writes one file per issue to .feedbot/issues/<id>.md. Point your agent at the folder, for example: “Read .feedbot/issues and fix the most frequent issue.”

When it’s fixed:

Terminal window
npx feedbot resolve 42 "Fixed Blob download in Safari"

Options:

Flag Description
--bot <id> Only issues from one bot.
--since <date> Only issues updated since a date, e.g. 2026-09-01.
--out <dir> Output folder. Default: .feedbot/issues.

Add .feedbot/ to .gitignore if you don’t want issues in version control.

Agent-ready report

Section titled “Agent-ready report”

GET /v1/reports/agent.md?botId=…&since=… returns one Markdown document written as instructions for an agent. In the dashboard, use Copy for agent or Download .md on the Insights page.

Each issue includes:

  • a short description and category (bug, UX, missing feature, idea);
  • frequency and the last time it was reported;
  • user quotes;
  • affected pages and browsers;
  • suggested acceptance criteria;
  • links to the source conversations.
## #42 CSV export fails in Safari (7 reports, last 3 days)
Page: /app/reports · Browser: Safari 18 (macOS, iOS)


> "I click Export and nothing happens" — Ann, Pro plan


Acceptance criteria:
- Export downloads a .csv in Safari 17+ on macOS and iOS
- The user sees an error message if the export fails

Tracker export

Section titled “Tracker export”

On Pro and Business, you can export issues to GitHub Issues or Linear with one click, or automatically when an issue reaches a number of reports you choose. GitHub-based agents can then pick them up from there.