Circuit (withcircuit.com) is autonomous product intelligence — the continuous 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, product managers and engineers at growth and scaling companies. If you're the person who reads customer signal on Monday and ships by Wednesday, Circuit was made for you.

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 a Circuit Surface?

A lightweight embed for any website — five surface types: Bubble, Embed, Banner, Thumbs and Trigger. Customers submit feedback in seconds. 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 Surface submission, a Slack message, a CSV row, a transcript segment, 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 specs for Cursor or Claude Code?

Circuit (withcircuit.com) automates the feedback-to-spec pipeline. Feedback flows in from Circuit Surfaces, Slack, Google Sheets, CSV, transcripts 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 — no copy-pasting, no context switching.

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 my codebase?

Circuit (withcircuit.com) bridges customer feedback and your codebase through codebase-aware product 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.spec 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.

How long does it take to get priorities from feedback?

Connect a source and the first batch processes in 15-20 minutes. After that, new feedback scores in real time. Most teams have a ranked backlog within the hour.

How does Circuit generate specs from my codebase?

Connect GitHub. Circuit reads 9 signals — file signatures, .cursorrules, testing patterns, directory structure, open issues, recent PRs, tech stack, CI config and README. Every spec includes real file paths and follows your team's coding conventions. An AI product spec generator grounded in how you actually build.

Can I change how priorities are ranked?

Yes. The Priority Engine scores across 6 lenses — volume, urgency, revenue impact, positive sentiment, negative sentiment and feature demand. Set a goal and every priority re-ranks to match. A feature prioritization framework that reflects what the team cares about today.

What happens after a feature ships?

Mark it shipped. Circuit emails the customers who asked for it — their original feedback quoted back. New feedback on the same theme feeds a V2 spec automatically. The loop continues.

Is feedback data used to train AI models?

No. Circuit uses AI for classification and spec generation but customer data is never used to train models. Feedback stays within the processing pipeline and is not shared with third parties for training purposes.

Where is Circuit data stored?

Data is stored on encrypted infrastructure with Supabase (Postgres). All connections use TLS. Backups are encrypted at rest.

Does Circuit access my full codebase?

No. Circuit reads 9 specific signals from your GitHub repository — file signatures, testing patterns, directory structure and a few others. It does not clone, store or index your full codebase. Read-only access, scoped to what specs need.

Who can access my team's data?

Only authenticated team members with the roles you assign. Circuit supports email-based 2FA. No Circuit staff access customer data without explicit permission.

Works with your stack

Circuit connects where feedback lives and where code ships.

Get started free →

Where AI specs go

Cursor and Claude Code via MCP

Circuit is the feedback MCP for Cursor and Claude Code — the feedback to spec pipeline, delivered via the Model Context Protocol. Pull priorities, fetch specs, search feedback and take actions from inside your coding tool. Use circuit.act to mark as shipped, notify customers, submit feedback or submit a transcript. Ship from terminal.

See how specs are generated →

Setup

•Cursor: Add Circuit MCP to your Cursor config
•Claude Code: Run claude mcp add circuit
•First run opens a browser for OAuth authentication
•Token cached locally for 30 days

View circuit-mcp on npm →

4 MCP tools

circuit.prioritiesRanked priorities ready to build

circuit.specFull spec for any priority with all 5 sections

circuit.askSearch feedback and priorities for context

circuit.actShip from terminal: mark shipped, notify customers, submit feedback or transcripts, assign, correct, park

Example: asking for priorities in Cursor

> What should I build next?

circuit.priorities → 3 results

Keyboard shortcuts — Score: 87
mentions · urgency: high · revenue: $18k MRR

CSV column mapping — Score: 71
mentions · urgency: medium · revenue: $12k MRR

Dark mode — Score: 64
mentions · urgency: low · revenue: $9k MRR

GitHub. Codebase comprehension for every spec

Connect your repo and Circuit reads the codebase to generate specs that reflect how your team builds — not just file paths, but what's inside them. Specs can only reference files that exist in your codebase. The system won't generate paths it hasn't seen. Circuit reads your .cursorrules and CLAUDE.md before generating, so the spec your coding tool receives already follows your team's rules. Create GitHub issues directly from any spec. The result is a codebase-aware product spec — not a generic template.

What Circuit reads

File signatures — exports, types and key functions from relevant source files
.cursorrules / CLAUDE.md — specs follow your team's coding rules
Testing patterns — a sample test file so specs match your testing style
Directory structure — compact file tree for accurate path suggestions
Open issues — avoids duplicating existing tracked work
Recent merged PRs — informs which files are suggested as relevant
Tech stack — detected framework, language and environment
CI/CD + config files — workflow names and config files present
README — project overview when no AI config files exist

All read-only. Circuit never writes to your repository.

What specs include

Actual file paths marked as new or modify, coding conventions that follow your .cursorrules and CLAUDE.md rules, and a Heads Up section when similar open issues already exist in your repo.

As your team refines .cursorrules and CLAUDE.md over time, Circuit's specs improve automatically — both systems read from the same source of truth.

Where feedback comes from

Slack. Automatic feedback collection

Connect your workspace and Circuit monitors selected channels with no manual forwarding. OAuth connection with AI-suggested channel selection. Polled every 10 minutes. Messages parsed for customer metadata and revenue band.

Slack setup guide →

Google Sheets. Bulk import

Connect Google Drive, select a spreadsheet, review the auto-detected column mapping and import. Useful for historical feedback or tools that export to Sheets.

Google Drive setup →

CSV. Drag and drop

Upload any CSV. Circuit auto-detects delimiter, encoding and headers. Map columns, review and import.

Surfaces. Five ways to collect feedback on your site

One script tag, five surface types. No authentication needed for submitters. Each surface is a 1-line embed with a live preview editor and per-surface analytics.

Surface types

BubbleMost responses. Best for open-ended feedback.
EmbedSubtle. Works well in docs and help pages.
BannerHigh visibility. Good for announcements or surveys.
ThumbsThumbs up/down with optional written follow-up. Per-feature tracking with data-context.
TriggerZero footprint. Best in forms or settings.

Use data-context to tag feedback by page, flow or feature — filter it in Surface Analytics later. Call .identify() from your JS to pass customer email and revenue tier automatically.

Feedback Surface docs →

Transcripts. Customer calls into priorities

Upload call recordings or interview transcripts and Circuit extracts feedback segments automatically — up to 25 per call, with speaker attribution. Supports Otter.ai, Fireflies, Grain and Whisper exports. Import directly from Google Drive. A research interview feeds the same priority pool as widget feedback.

Manual entry

Paste feedback from anywhere. Email threads, support tickets, meeting notes. Processed through the same AI pipeline as every other source.

API. Submit feedback programmatically

Single and batch endpoints for submitting feedback from your own backend, support tools or data pipelines. Supports deduplication, customer metadata and revenue tier. See API docs →

Automation and events

Webhooks. Connect anything else

Send events to any HTTP endpoint, Slack channel, Linear, GitHub or PagerDuty.

Available events

•Spec generated
•Build status changed (ready → building → shipped)
•New priority created
•Priority volume spike (>20% increase)
•New feedback received

Test any hook before going live with full execution history, timestamps and status codes. All integrations included on every plan.

See pricing →

FAQ

Add the Circuit Slack integration. Circuit polls your selected channels every 10 minutes, classifies each message by intent, urgency and sentiment, and feeds it into the priority pipeline. No manual sorting.

Install circuit-mcp from npm. Four tools: circuit.priorities (ranked list), circuit.spec (full spec with file paths), circuit.act (ship, assign, correct) and circuit.ask (search feedback). Specs arrive where code gets written.

Six sources: Circuit Surfaces (embed on any site), Slack, Google Sheets, CSV upload, transcript upload (Otter, Fireflies, Grain, Whisper) and manual entry. All feed the same pipeline.

No. Circuit reads from Slack, spreadsheets and support threads — wherever feedback already lives. It adds the layer that was missing: scored priorities and codebase-grounded specs.

Connect your stack.

Get started