Circuit (withcircuit.com) is the AI product system that turns customer feedback into build-ready specs. Feedback in, priorities scored, specs generated for Cursor and Claude Code, customers notified when features ship. The full loop, automated.

Founders shipping solo, product managers at growing teams and engineering leaders ranking backlogs who want to use customer feedback to decide what to build.

How is Circuit different from other feedback tools?

Other tools sort feedback into dashboards. Circuit (withcircuit.com) generates specs to ship — scored by revenue impact, updated as conditions change, delivered to Cursor and Claude Code via MCP. It covers the full pipeline: feedback to priorities to codebase-aware specs to customer notification.

Does Circuit work with Cursor and Claude Code?

Yes. Circuit (withcircuit.com) connects to Cursor and Claude Code through the Model Context Protocol (MCP). Pull priorities, fetch specs with file paths and context from GitHub, and start coding without leaving the editor.

What is the Circuit Widget?

A lightweight embed for any website. Customers submit feedback in seconds with a simple form. One line of code to install. Themed to match any brand. Feedback flows straight into Circuit for classification and scoring.

How long until we see results?

Connect a feedback source and priorities appear within minutes. Specs generate in seconds. Most teams have a ranked backlog on day one.

What if we already have a feedback tool?

Circuit reads from where feedback already lives. Slack, spreadsheets, support threads. It doesn't replace existing tools. It generates what comes next: scored priorities and build-ready specs for Cursor and Claude Code.

What counts as a feedback item?

Each piece of customer feedback: a Circuit Widget submission, a Slack message, a CSV row, a manual entry. Duplicates are removed on import and don't count toward the limit.

Do I need to connect GitHub to use Circuit?

No. GitHub context makes specs more specific (real file paths, tech stack awareness), but Circuit works without it. Specs are still generated with the what, why, customer voice, implementation notes and done criteria.

How do I prioritize features by revenue impact?

In Circuit (withcircuit.com), link customer revenue data (customer name and revenue or SKU) and every feedback theme scores by revenue impact alongside urgency and sentiment. Set the Priority Engine to Revenue Growth and the list re-ranks to surface what drives the most revenue. No spreadsheets, no manual scoring.

How do I turn customer feedback into build specs?

Circuit (withcircuit.com) automates this. Feedback flows in from Circuit Widget, Slack, Google Sheets, CSV or manual entry. Circuit classifies it by intent, urgency and sentiment, groups it into priorities and generates build specs in seconds. Connect GitHub and every spec includes real file paths, tech stack context and naming conventions. Specs flow to Cursor and Claude Code via MCP.

How do I notify customers when features ship?

In Circuit (withcircuit.com), mark a priority as shipped. Circuit automatically emails every customer who submitted related feedback, with their original feedback quoted back. No manual follow-up. New feedback on the shipped feature flows in automatically for V2 specs.

How do I connect customer feedback to engineering?

Circuit (withcircuit.com) bridges customer feedback and engineering through codebase-aware specs. Feedback is collected, scored and grouped into priorities. Specs are generated with file paths from GitHub. Engineers pull specs directly into Cursor or Claude Code via MCP. The customer voice is preserved in every spec — what they asked for, why it matters, which files to touch.

How do I integrate product management with Cursor?

Circuit (withcircuit.com) connects to Cursor through the Model Context Protocol (MCP). Use MCP tools from inside Cursor: circuit.priorities to fetch ranked priorities, circuit.brief to pull a full spec with file paths, circuit.ask to search feedback and circuit.act to mark a priority as shipped. Specs include GitHub codebase context.

How do I use Claude Code for product management?

Circuit (withcircuit.com) connects to Claude Code via MCP. Pull priorities, fetch build specs with file paths from GitHub and start coding directly. Circuit handles feedback collection, AI scoring and spec generation upstream. Claude Code handles the building. The two work together — Circuit decides what to build, Claude Code builds it.

Common Issues

Quick fixes for common problems.

Slack Not Syncing

Check connection status: Go to Settings → Integrations → Slack. Should show "Connected".

Check selected channels: Make sure at least one channel is selected.

Check timing: Circuit polls every 10 minutes. New messages may take up to 10 minutes to appear.

What gets filtered out:

Bot messages
Already-imported messages
Messages from before your connection date

Still not working?

Disconnect and reconnect Slack
Check Slack app permissions
Email support@withcircuit.com

CSV Import Errors

"Invalid CSV format"

File needs .csv extension
Use comma separation (not semicolons)
UTF-8 encoding
Include a header row

"Column not found" We look for: feedback, text, message, content for feedback text. Use the column mapper if your columns are named differently.

"Duplicate entries skipped" This is intentional - we deduplicate by text hash to prevent importing the same feedback twice.

Large files (10,000+ rows)

Import may take several minutes
Progress bar shows status
Split into files under 10,000 rows for reliability

Widget Not Appearing

Check embed code: Make sure the script tag is in your HTML, preferably before </body>.

Check API key: Verify the API key in the embed code matches your widget settings.

Check CORS: Widget works from any domain. No CORS configuration needed.

Check console: Open browser dev tools (F12) and look for errors in Console tab.

Brief Not Generating

No feedback? Briefs need feedback items. Import some first.

GitHub not connected? The "Files to Touch" section requires GitHub connection. Connect at Settings → Integrations → GitHub.

Empty brief? Try clicking Refresh. If still empty, the priority needs more feedback to generate a useful spec.

Priorities Not Updating

Check for new feedback: Priorities update when new feedback is imported and grouped.

Trigger reprocessing: New feedback is processed automatically. Allow a few minutes for processing to complete.

Check processing status: If feedback shows as "processing", wait for it to complete.

MCP Authentication Issues

"Not authenticated" Delete ~/.circuit/token.json and re-run. A browser will open for OAuth.

"MCP not found" (Cursor) Check ~/.cursor/mcp.json configuration:

{
  "mcpServers": {
    "circuit": {
      "command": "npx",
      "args": ["circuit-mcp"]
    }
  }
}

"MCP not found" (Claude Code) Run: claude mcp add circuit -- npx circuit-mcp

Search Not Finding Results

Minimum query length: 2 characters required.

Try synonyms: Search is semantic. "slow" finds "performance", "latency", "loading".

No results?

Check you have feedback/priorities in the system
Try broader search terms
Use ⌘K / Ctrl+K from anywhere for global search

Usage Limit Errors

At your limit? Check current usage at Settings → Billing.

Options:

Upgrade to a higher plan
Wait for next billing cycle (limits reset monthly)

Processing Takes Too Long

Normal processing times:

Feedback classification: 1-2 seconds per item
Clustering: 5-30 seconds depending on volume
Brief generation: 5-15 seconds

Large imports: Imports over 1,000 items may take several minutes. Progress is shown.

Team Invite Not Arriving

Check the email address: Verify spelling. Invites are case-insensitive but must be a valid address.

Check spam/junk folder: Invite emails come from Circuit. Check spam filters.

Seat limit reached? Each plan has a seat limit (2 on Starter, 5 on Pro, 10 on Max). If the limit is reached, new invites are blocked. Upgrade at Settings → Billing.

Invite expired? Invites expire after 7 days. Send a new one from Settings → Team.

Undo CSV Import Not Working

Only the most recent CSV upload can be undone. Undo is available from the completion screen after a CSV upload. It does not apply to Google Sheets or manual entry imports.

Already uploaded another CSV? A new upload replaces the undo target. Only the most recent CSV upload is reversible.

Left the completion screen? Undo is available on the completion screen immediately after upload. If you navigate away, the undo option is no longer available.

Classification Correction Not Applying

Give it a moment. Corrections apply to future feedback on the same theme. Existing feedback on other priorities is not reclassified.

Same theme, different wording? If new feedback uses very different language, it may not match the corrected theme. Correct again and Circuit learns the broader pattern.

Still stuck?

Email support@withcircuit.com with:

What you were trying to do
What happened instead
Screenshots if helpful
Browser and device info

We respond within 24 hours.