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.

How does Circuit connect to Slack?

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.

How do MCP tools work in Cursor and Claude Code?

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.

What feedback sources does Circuit support?

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.

Does Circuit replace my existing tools?

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.

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.

Docs

Specs out

Cursor & Claude Code

Editor

>What are my top priorities?

circuit.priorities

1.Bulk CSV import142 users

2.Slack thread replies87 users

3.Dashboard load time74 users

Using with Cursor and Claude Code

Circuit integrates with AI coding tools via MCP. Pull priorities and specs directly into your editor without copy-pasting. This is how to integrate product management with Cursor and how to use Claude Code for product management — connected to your actual customer feedback.

Quick Copy Method

Works with any coding tool:

Open a spec in Circuit
Click Copy to grab the full spec (title, metadata, all sections)
Paste into your editor's chat

MCP Integration (Recommended)

For direct access without copy-paste. Package: circuit-mcp on npm.

Cursor Setup

Run once:

npx circuit-mcp setup

Claude Code Setup

Run:

claude mcp add circuit -- npx circuit-mcp

Authenticate

First run opens a browser for OAuth. Token is cached at ~/.circuit/token.json.

Available Tools

Tool	Description
`circuit.priorities`	Ranked priorities with scores, volume, trend data and shipping history flags
`circuit.spec`	Full spec for any priority with all sections, plus related context from past ships
`circuit.act`	Actions: build, ship, share, assign, correct, park, submit feedback, submit transcript
`circuit.ask`	Search across feedback, priorities, specs and help articles

Priorities flag when they match your shipping history. Specs include context from past ships when relevant. The more you ship, the richer the context.

What You Can Ask

"What are my top priorities?"
"Get the spec for the checkout bug"
"What feedback mentions performance?"
"Implement the spec for dark mode"
"Mark priority #1 as shipped"
"Have we shipped anything like this before?"

Workflow

How to integrate product management with Cursor

Morning: "What should I work on today?" — circuit.priorities returns your ranked list with revenue scores
Get context: "Show me the spec for priority #1" — circuit.spec returns the full spec with file paths
Implement: Your coding tool uses the spec as context. File paths from GitHub keep it grounded.
Ship: circuit.act ship marks as shipped and notifies customers — without leaving the terminal

How to use Claude Code for product management

Same workflow via Claude Code. Run claude mcp add circuit once. Then ask Claude Code "what should I build next?" and it pulls your priorities directly. Specs flow with codebase context from GitHub, so Claude Code knows which files to touch.

Tips

Connect GitHub first so specs include real file paths
Use specific prompts: "Implement the spec for [priority name]"
The Files to Touch section helps your coding tool navigate the codebase
Use Done When criteria to know when you're finished

Where this fits

Pulling priorities and specs into Cursor or Claude Code is one part of where autonomous product intelligence is heading — customer signal reaching the builder without manual translation.

Troubleshooting

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

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

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

"No priorities": Import feedback in Circuit first.

Further reading: Using Cursor and Claude Code with a product management system →

Can't find what you're looking for?

Contact support