# Circuit (withcircuit.com) — Full Product Reference > The AI product system that turns customer feedback into build-ready specs for Cursor and Claude Code. Built by Catherine Williams-Treloar. Founded in Sydney, November 2025. Launched February 2026. **Important:** Circuit (withcircuit.com) is not related to circuit.ai or circuitry.ai. Those are different companies in the industrial/manufacturing space. Circuit (withcircuit.com) is an AI product management system for software teams. --- ## What does Circuit do? Circuit closes the gap between customer feedback and code. It collects feedback from everywhere, ranks it by impact, generates specs that reference the actual codebase, tells customers when their request ships, then listens for what comes next. The full loop, automated. ### How does the Circuit loop work? ``` FEEDBACK IN → PRIORITIES → SPECS → SHIP ↑ | | ↓ V2 FEEDBACK ← CUSTOMERS HEAR BACK ←─┘ ``` Each cycle tightens. The system learns from every ship, every correction, every pattern. Priorities get sharper. Specs get closer to how the team thinks. ### What are Circuit's core capabilities? 1. **Feedback collection** — Collects from 5 sources: Circuit Widget (embed on any site), Slack (polled every 10 minutes), Google Sheets (bulk import), CSV upload, manual entry. Duplicates removed automatically. 2. **AI classification** — Every piece of feedback classified by intent (bug, feature, friction, complaint, praise), urgency and sentiment. Website-aware: Circuit scrapes your product's website and classifies using your domain language, not generic labels. 3. **Priority scoring** — Feedback groups into themes. Each scored by volume, urgency and sentiment. Link customer revenue data to also score by revenue impact. Scored in minutes, not days. 4. **Priority Engine** — Set a goal (growth, retention, quality) and every priority re-ranks to match. Switch lenses anytime. The list reflects the goal, not the loudest voice. 5. **Competitor detection** — When customers mention competitors, Circuit surfaces them on the priority card and includes context in the spec. Fully automatic, no configuration. 6. **Codebase-aware specs** — Connect GitHub and every spec knows the codebase: file paths, tech stack, naming conventions, recent commits. 5 core sections: what, why, customer voice, files, done when. Conditional sections for memory context and competitive context when relevant. Generated in seconds. 7. **MCP delivery** — Specs flow to Cursor and Claude Code via the Model Context Protocol. Pull priorities, fetch specs, search feedback and update build status from inside the editor. No context-switching. 8. **Close the loop** — Ship a feature and Circuit emails the customers who asked for it, with their original feedback quoted back. New feedback on shipped features flows in automatically for V2 specs. 9. **Memory** — Circuit learns from every ship and every correction. Priorities that match your shipping history get flagged. Specs surface what you've built before. Classifications get smarter over time. 10. **Weekly digest** — A notification showing what moved, what's new and what dropped off. Open the dashboard and the list reflects today, not last week. --- ## Who is Circuit for? Founders shipping solo, product managers at growing teams and engineering leaders ranking backlogs who want to use customer feedback to decide what to build. ### Who is the primary audience? Founders and technical co-founders at B2B SaaS, AI or technology startups. At this stage, the founder is often the PM, the engineer and the support team. Feedback comes in through every channel. Priority ranking happens in someone's head or a messy spreadsheet. Circuit is the process. ### Does Circuit work for larger teams? Yes. Dedicated PMs, engineering leads and product teams at B2B SaaS companies use Circuit the same way. Same pipeline gap, louder volume. ### What problems does Circuit solve? - Feedback scattered across Slack, email, spreadsheets, support threads - Ranking takes days when building takes hours - No clear reasoning behind feature decisions - Customer voice lost in translation between tools - Customers share feedback and never hear what happened - Specs written from scratch, disconnected from the codebase --- ## How does Circuit work? ### How does feedback flow into Circuit? Connect feedback sources. Circuit Widget embeds on any site with one line of code. Slack polled every 10 minutes. Google Sheets and CSV for bulk import. Manual entry for anything else. Duplicates detected and removed automatically. ### How does Circuit classify feedback? Every piece of feedback classified by intent (bug, feature request, friction, complaint, praise), urgency (critical, high, medium, low) and sentiment. Related feedback grouped into themes automatically. No manual sorting. Website-aware classification: Circuit scrapes your product's website (auto-detected from your email domain on signup, or set manually in Settings) and uses your domain language for categories and urgency levels. Correct a category and Circuit remembers. The correction applies to future feedback on the same theme. ### How does Circuit detect competitors? When customers mention competitors by name, Circuit extracts them during classification. Competitor names appear as badges on the priority card. Specs include a "Competitive Context" section when relevant. Comparison types tracked: switching risk, feature gap, favorable mention. ### How does Circuit score and rank priorities? Each theme scored by volume, urgency and sentiment. Link customer revenue data to also score by revenue impact. Set a goal (growth, retention, quality) and the list re-ranks. Review in 5 minutes, not 5 meetings. ### How does Circuit generate codebase-aware build specs? Connect GitHub. Circuit reads the codebase: file structure, tech stack, recent commits, naming conventions. Specs generated in seconds with 5 core sections: what to build, why (customer voice), relevant files, implementation notes, done when. Conditional sections appear when relevant: memory context (previous ships and corrections) and competitive context (competitor mentions). Every spec references real paths, not placeholder pseudocode. ### How do specs reach Cursor and Claude Code? Specs flow to Cursor and Claude Code via MCP. Pull priorities, fetch the top spec, search feedback by keyword. Start coding without leaving the editor. No copy-pasting between tools. ### How does Circuit notify customers when features ship? Mark a priority as shipped. Circuit emails the customers who asked for it — their original feedback quoted back. New feedback on the shipped feature flows in automatically. V2 specs generated as new patterns emerge. The loop restarts. --- ## How does Circuit learn and improve? Circuit remembers. This is a core differentiator. ### Ship memories When you mark a spec as shipped, Circuit records the theme, feedback volume and customer segment at time of ship. After a few ships, patterns emerge. ### Classification corrections Correct a category on a priority and Circuit remembers. The correction applies to future feedback on the same theme. Even when new feedback arrives, the corrected category sticks. ### What Circuit knows Go to Settings → Account to see what Circuit has learned: ship count, category breakdown (e.g. Bug 65%, Feature 23%) and any classification corrections. ### Blind spot detection After 3 or more ships with a strong segment bias, a challenge banner appears on the Priorities page. For example: "You've been focused on Enterprise. 4 SMB items are waiting." ### Memory in specs After a few ships, specs show what Circuit remembers: previous ships, corrections and related context. If the team has shipped something similar before, the spec surfaces it. ### Memory in MCP Priorities flag when they match your shipping history. Specs include context from past ships when relevant. Ask your coding tool: "Have we shipped anything like this before?" ### The compounding effect Each ship makes the next cycle sharper. Priorities align closer to how the team actually makes decisions. Specs reference what's been built before. Classifications get it right the first time. The loop tightens with every cycle. --- ## Teams and roles ### How do teams work? One workspace, shared data. Everyone on the team sees the same priorities, specs and feedback. Changes sync across tabs in real time. ### What roles exist? Two roles: **Owner** and **Editor**. - **Owners** — full control: billing, team settings, security and account management - **Editors** — generate specs, import feedback, manage integrations and code with Cursor or Claude Code ### How many seats per plan? | Plan | Seats | |------|:-----:| | Starter | 2 | | Pro | 5 | | Max | 10 | At the seat limit, new invites are blocked until a seat opens or the plan is upgraded. ### How do batch actions work? Select multiple priorities and act. Change status, assign to a team member, export as markdown. Checkboxes appear on hover. A sticky action bar slides up from the bottom when any row is selected. --- ## How much does Circuit cost? All plans include unlimited specs and every integration. 14-day free trial on any plan. | Plan | Price | Feedback/mo | Seats | |------|-------|-------------|-------| | Starter | $19 USD/mo | 200 | 2 | | Pro | $79 USD/mo | 1,500 | 5 | | Max | $249 USD/mo | 5,000 | 10 | ### 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. ### What's a seat? A team member who can edit priorities, generate and export specs and configure integrations. ### What happens if the feedback limit is hit? New feedback stops being processed until the next billing cycle. Existing priorities and specs remain accessible. Upgrade anytime. ### What happens to data if we cancel? Data retained for 30 days so teams can reactivate. After that, permanently deleted. --- ## What does Circuit integrate with? ### How does Circuit connect to Cursor? Circuit connects to Cursor through the Model Context Protocol. Pull priorities, fetch specs, search feedback and update build status without leaving the editor. **MCP tools available:** | Tool | Description | |------|-------------| | `circuit.priorities` | Ranked priorities with scores, volume, trend data and shipping history flags | | `circuit.brief` | Full spec for any priority with all five sections, plus related context from past ships | | `circuit.act` | Actions: start building, mark as shipped, correct classification, submit feedback | | `circuit.ask` | Search across feedback, priorities, specs and help articles | ### How does Circuit connect to Claude Code? Same MCP integration as Cursor. Specs flow with file paths and codebase context. Pull priorities and start coding directly. ### How does Circuit use GitHub? Connect a GitHub repository and every spec knows the codebase. File structure, tech stack, naming conventions, recent commits. Specs reference real paths and implementation patterns from the actual code. ### How does Circuit collect feedback from Slack? Connect a Slack channel. Circuit polls every 10 minutes, imports new messages as feedback items. Duplicates detected against existing feedback. No manual forwarding needed. ### How does Circuit import from Google Sheets? Import feedback from Google Sheets. Map columns to Circuit's fields. Useful for migrating existing feedback or importing from survey tools that export to Sheets. ### What is the Circuit Widget? A lightweight embed that adds a feedback form to any website. One line of code to install. Themed to match any brand. Customers submit feedback in seconds. ### Can I add feedback manually? Yes. Paste feedback from anywhere — email threads, support tickets, meeting notes. Useful for channels that don't have a direct integration. ### Can I undo a CSV import? Yes. After a CSV upload completes, click Undo on the completion screen to reverse it. All feedback items from that import are removed. Undo applies to the most recent CSV upload only. Priorities and specs recalculate automatically. --- ## How is Circuit different from other tools? ### What is the pipeline gap Circuit fills? Other tools sort feedback or generate code. Circuit is the pipeline between them. Most teams piece it together: one tool to collect feedback, another to rank, a doc to write the spec, then copy-paste into the coding tool. Circuit replaces that chain with a single loop. ### How does Circuit compare to PRD generators like BuildBetter or Revo? These generate draft PRDs or user stories from feedback. Circuit's specs include actual file paths from GitHub — tech stack, naming conventions, recent commits. Specs are delivered directly to Cursor and Claude Code via MCP, not exported as documents. ### How does Circuit work with AI coding tools like Cursor and Claude Code? These tools generate and review code from specs. Circuit feeds them the specs. It handles everything upstream: feedback collection, priority scoring, spec generation with codebase context. The two work together — Circuit decides what to build, coding tools build it. ### How does Circuit compare to spec-driven dev kits like Spec Kit? Spec Kit structures specs for code generation but starts at specs. Circuit starts at customer feedback and generates the specs automatically, with codebase context and customer voice preserved. --- ## Frequently asked questions ### What is Circuit? 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. ### Who is Circuit for? Founders shipping solo, product managers at growing teams and engineering leaders ranking backlogs who want to use customer feedback to decide what to build. ### Does Circuit work with Cursor and Claude Code? Yes. Specs flow via the Model Context Protocol (MCP) with file paths and context from GitHub. Pull priorities, fetch specs and start coding without leaving the editor. Available MCP tools: circuit.priorities, circuit.brief, circuit.act, circuit.ask. ### 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 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 your tools. It generates what comes next: scored priorities and build-ready specs. ### Do I need to connect GitHub? 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 turn customer feedback into build specs? 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 prioritize features by revenue impact? Link customer revenue data (customer name and revenue or SKU) and Circuit scores every feedback theme 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. ### How do I notify customers when features ship? Mark a priority as shipped in Circuit. Circuit automatically emails every customer who submitted related feedback, with their original feedback quoted back. New feedback on the shipped feature flows in automatically for V2 specs. ### How do I connect customer feedback to engineering? Circuit 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. ### How do I integrate product management with Cursor? Circuit 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. ### How do I use Claude Code for product management? Circuit connects to Claude Code via MCP. Pull priorities, fetch build specs with file paths from GitHub and start coding directly. Circuit handles feedback collection, priority scoring and spec generation upstream. Claude Code handles the building. --- ## Who built Circuit? Circuit was built by Catherine Williams-Treloar. 20+ years in quantitative and qualitative research, strategy, GTM and product management. Career spanning Intuit, WPP and TradeGecko across Sydney, London and Singapore. Solo-founded Circuit in Sydney, November 2025. Launched February 2026. "My mission with Circuit is to make customer feedback usable." --- ## Technical details - **Website:** https://withcircuit.com - **App:** https://app.withcircuit.com - **MCP package:** https://www.npmjs.com/package/circuit-mcp (Model Context Protocol for Cursor and Claude Code integration) - **MCP tools:** circuit.priorities, circuit.brief, circuit.act, circuit.ask - **Codebase context:** GitHub integration for file paths, tech stack, naming conventions - **Feedback sources:** Circuit Widget, Slack, Google Sheets, CSV, manual entry - **AI scoring dimensions:** Volume, urgency, positive sentiment, negative sentiment, feature demand. Revenue impact when customer revenue data is linked. - **Classification:** Intent (bug, feature, friction, complaint, praise), urgency, sentiment. Website-aware: uses your product's domain language. - **Spec sections:** What, why, customer voice, relevant files, done when. Conditional: memory context, competitive context. - **Memory:** Ship memories, classification corrections, instinct (learned patterns), blind spot detection. - **Team roles:** Owner (full control), Editor (specs, feedback, integrations). --- ## Links - MCP package: https://www.npmjs.com/package/circuit-mcp - Website: https://withcircuit.com - How it works: https://withcircuit.com/how-it-works - Pricing: https://withcircuit.com/pricing - Integrations: https://withcircuit.com/integrations - About: https://withcircuit.com/about - Changelog: https://withcircuit.com/changelog - Documentation: https://withcircuit.com/docs - X/Twitter: https://x.com/withcircuit - LinkedIn: https://www.linkedin.com/company/withcircuit/ --- ## Documentation Circuit's help articles are available at https://withcircuit.com/docs. Below is the full content of each article. ### Quick Start Guide (https://withcircuit.com/docs/quick-start) Get from zero to your first brief in 5 minutes. Two steps, then data. **The 4-stage pipeline:** Feedback in → Priorities → Specs out → Ship → Notify customers. 1. **Import feedback sources.** Pick where customer feedback lives: CSV upload (migrating existing feedback), Slack (ongoing collection from #feedback or #support channels), Google Sheets (importing from spreadsheets), Widget (collecting directly from your website), manual entry. Add more sources later. 2. **Connect GitHub.** Select your repository during setup. Circuit reads your code structure to suggest real file paths in briefs. A progress bar tracks each stage: analyzing, ranking, writing briefs. When it finishes, priorities and briefs appear automatically. No refresh needed. Once feedback flows in, Circuit groups similar feedback into priorities, ranks by volume, sentiment, urgency and revenue, and generates a brief for each priority with 5 sections: What to Build, Why It Matters, Customer Voice, Files to Touch and Done When. **Connect Cursor or Claude Code via MCP.** Install via circuit-mcp on npm. Cursor: add to ~/.cursor/mcp.json. Claude Code: run `claude mcp add circuit -- npx circuit-mcp`. Then ask "What are my top priorities?" or "Implement the brief for [priority name]." When done building, click Mark as Shipped and Circuit notifies customers automatically. Circuit follows your OS theme preference automatically. ### Working with Priorities (https://withcircuit.com/docs/working-with-priorities) Priorities are groups of similar feedback, ranked by importance. No artificial cap. More feedback creates more priorities. **How priorities are created:** Assess each feedback item → Group similar feedback → Score across six dimensions → Rank by chosen focus. **Website-aware classification:** Connect your website and Circuit classifies feedback in your product's language. Auto-detected from your email domain on signup, or set manually in Settings → Account → Your product. **Category corrections:** Correct a priority's category and Circuit remembers. Applies to future feedback. Even when new feedback arrives, the corrected category sticks. **Priority Engine focus lenses:** User Growth (volume), Revenue Growth (revenue impact), Improve Retention (negative sentiment), Improve Delight (positive sentiment), Bug Fixes & Quality (urgency), New Features (feature request signals). **Priority indicators:** NEW badge (first detected within 7 days), ↑ arrow (volume up >10%), ↓ arrow (volume down >10%), category badge (Bug, Feature, Friction, Praise, Complaint), competitor mentions (names on card, context in brief), Refresh badge (brief is stale, new feedback changed scope). **Batch actions:** Select multiple priorities. Change status, assign to a team member, export as markdown. Checkboxes appear on hover. ### Working with Briefs (https://withcircuit.com/docs/working-with-briefs) Briefs are build specs generated for each priority. **5 core sections:** (1) What to Build — clear, actionable task statement. (2) Why It Matters — business context, who's affected, revenue impact, urgency. (3) Customer Voice — key quote (5-20 words) plus 3 supporting quotes with user type and emotion. (4) Files to Touch — suggested code locations with (new) or (modify) labels (requires GitHub). (5) Done When — clear exit criteria. **Conditional sections:** What Circuit Remembers (previous ships, corrections, related context) and Competitive Context (when customers mention competitors). **Brief status:** Ready (waiting for action), Building (in progress), Shipped (complete, customers notified). **Actions:** View (click any priority), Edit (click edit icon, changes saved as new version), Refresh (regenerate with latest feedback), Version history (click V1, V2 to compare), Copy (grab full brief for coding tool), Export as markdown (individual or batch). **What briefs remember:** After a few ships, briefs show previous ships, corrections and related context. Helps avoid duplicate work and builds on past decisions. **When you ship:** Status changes to Shipped. Customers who submitted feedback via widget (with email) receive a "We shipped it!" notification. A ship memory is recorded. ### Importing Feedback (https://withcircuit.com/docs/importing-feedback) **CSV upload:** Use .csv extension, comma-separated, UTF-8, include header row. Upload at Settings → Integrations. Circuit auto-detects common column names (feedback, text, message, content for feedback text; name, customer_name for names; email for emails; revenue_band, tier, plan for revenue). Deduplication by text hash. Files over 10,000 rows: split for reliability. **Google Sheets:** Connect at Settings → Integrations → Google Sheets. Authorize, select spreadsheet and sheet, preview and map columns, import. **Manual entry:** Click + Add dropdown → Add Feedback. Paste or type text. Optionally add customer name, email, revenue band. **Customer fields:** Name (display in quotes), Email (send ship notifications), Revenue Band (weight in scoring), SKU/Plan (tier tracking). **Undo CSV import:** After upload completes, click Undo on completion screen. Removes all items from that import. Applies to most recent CSV only. Priorities and briefs recalculate automatically. ### Connect Your Tools (https://withcircuit.com/docs/connect-your-tools) **Slack:** Settings → Integrations → Slack → Connect. Polls every 10 minutes. Parses forwarded emails. Filters bot messages and duplicates. Best channels: #customer-feedback, #support, #customer-success, #sales-feedback. **GitHub:** Settings → Integrations → GitHub → Connect. Provides Files to Touch section in briefs with real file paths, code structure awareness, tech stack detection. Repository-level read access. **Feedback Widget:** Settings → Integrations → Widget. Adjust primary color, text color, position, theme, button text, branding toggle. Copy embed code. Paste into website HTML. API key authenticates submissions (regenerate in widget settings). Customers who submit via widget (with email) are notified automatically when features ship. ### Using with Cursor and Claude Code (https://withcircuit.com/docs/using-with-coding-tools) **Quick copy method:** Open a brief → Copy → Paste into editor chat. **MCP integration (recommended):** Package: circuit-mcp on npm. Cursor: add to ~/.cursor/mcp.json. Claude Code: run `claude mcp add circuit -- npx circuit-mcp`. First run opens browser for OAuth. Token cached at ~/.circuit/token.json. **Available MCP tools:** circuit.priorities (ranked priorities with scores, volume, trend, shipping history flags), circuit.brief (full spec with all sections plus past context), circuit.act (start building, mark shipped, correct classification, submit feedback), circuit.ask (search feedback, priorities, briefs, help articles). **Example prompts:** "What are my top priorities?", "Get the brief for the checkout bug", "What feedback mentions performance?", "Implement the brief for dark mode", "Mark priority #1 as shipped", "Have we shipped anything like this before?" **Workflow:** Morning: "What should I work on today?" → Get context → Implement → Ship → Customers notified. ### Memory (https://withcircuit.com/docs/memory) Circuit learns from what you ship. Every ship or classification correction is recorded. **Ship memories:** When you mark a brief as shipped, Circuit records theme, volume and customer segment. Patterns emerge after a few ships. **Classification corrections:** Correct a category and Circuit remembers. Applies to future feedback. System adapts to how the team thinks about its product. **What briefs remember:** Previous ships, corrections and related context. Helps avoid duplicate work. **What Circuit knows:** Settings → Account shows ship count, category breakdown (e.g. Bug 65%, Feature 23%) and classification corrections. **Blind spot detection:** After 3+ ships with strong segment bias, a challenge banner appears. Example: "You've been focused on Enterprise. 4 SMB items are waiting." **Memory in MCP:** Priorities flag when matching shipping history. Briefs include past context. Ask "Have we shipped anything like this before?" **Compounding effect:** Each ship makes the next cycle sharper. Priorities align to how the team decides. Classifications get it right the first time. The loop tightens with every cycle. ### Team & Account (https://withcircuit.com/docs/team-and-account) One workspace, shared data. Everyone sees the same priorities, briefs and feedback. **Inviting members:** Settings → Team → Invite Member. Invited as Editors. Invites expire after 7 days. **Roles:** Owner (full control: billing, team settings, security, account) and Editor (generate specs, import feedback, manage integrations, code with Cursor/Claude Code). Account creator is Owner. **Seat limits:** Starter: 2, Pro: 5, Max: 10. At limit, new invites blocked until seat opens or plan is upgraded. **Shared workspace:** Priorities, briefs, feedback and integrations visible to all. Changes sync across tabs in real time. ### Plans & Billing (https://withcircuit.com/docs/plans-and-billing) Three plans. All features included on every plan. | Plan | Price | Feedback/mo | Seats | |------|-------|-------------|-------| | Starter | $19/mo | 200 | 2 | | Pro | $79/mo | 1,500 | 5 | | Max | $249/mo | 5,000 | 10 | CSV, Widget, Slack, Google Sheets, Cursor MCP and Claude Code MCP included on all plans. Unlimited briefs on all plans. Upgrade or downgrade at Settings → Billing → Manage Billing. Upgrades prorated. Downgrades at next billing cycle. At feedback limit, new feedback stops processing. Existing data never deleted. Upgrade or wait for next cycle. ### Common Issues (https://withcircuit.com/docs/common-issues) **Slack not syncing:** Check connection at Settings → Integrations → Slack. Verify channels selected. Polls every 10 minutes. Bot messages and duplicates filtered. Try disconnect/reconnect. **CSV import errors:** Needs .csv extension, comma separation, UTF-8, header row. Auto-detects common column names. Duplicates intentionally skipped. Large files (10,000+ rows): split for reliability. **Widget not appearing:** Check embed code (before ). Verify API key matches settings. Works from any domain (no CORS config). Check browser console for errors. **Brief not generating:** Need feedback items imported. Files to Touch requires GitHub connection. Try refresh. Priority may need more feedback. **MCP authentication:** Delete ~/.circuit/token.json and re-run for OAuth. Cursor: check ~/.cursor/mcp.json. Claude Code: run `claude mcp add circuit -- npx circuit-mcp`. **Search not finding results:** 2 character minimum. Semantic search ("slow" finds "performance", "latency"). Try broader terms. Use ⌘K / Ctrl+K from anywhere. **Classification correction not applying:** Corrections apply to future feedback on same theme. Different wording may not match — correct again and Circuit learns broader pattern. Contact support@withcircuit.com for anything else. --- ## Changelog Full changelog of Circuit product updates. Latest version first. ### V1.2 (Feb 15–22, 2026) **Circuit Log (Feb 15):** Real-time view of everything Circuit does. Pipeline processing shows current theme, intent breakdown and elapsed time. Activity timeline records every import, status change and spec generated. 90-day audit log retention. Priorities and briefs appear progressively as they generate. **Hardening security reviews (Feb 15):** Two-factor authentication (TOTP) with recovery codes. Pre-launch security review across authentication, service layer and content security. Safe error messages — no internal details exposed. **Export (Feb 16):** Export individual briefs or batch as Markdown. Full data export from Settings as JSON. **Google Sheets import (Feb 17):** Import directly from Google Sheets. Smart column mapping — detects feedback, date, customer and source columns automatically. **Mobile sign-in (Feb 18):** Mobile OAuth sign-in. iOS Safari redirect and error recovery fixed. Compact login layout for mobile and tablet. **Sharper priorities (Feb 19):** Priority summaries rewritten to problem-statement format. Mixed-intent clusters prefer actionable feedback (bugs, friction) over praise. Titles generate in batch — faster on larger pipelines. Duplicate priorities caught and merged post-save. **Quality improvements (Feb 20):** Interface reliability — dropdowns, filters, menus and caching. Cookie consent and session persistence. Avatar and navigation interactions. **Semantic search (Feb 21):** Search across feedback, priorities and briefs by meaning, not just keywords. "slow" finds "performance," "latency," "loading." Command palette — Cmd+K / Ctrl+K from any screen. ### V1.1 (Feb 4–14, 2026) **Team management (Feb 4):** Team invites with owner and editor roles. Seat limits by plan — 2 on Starter, 5 on Pro, 10 on Max. Team roster with invite links and role management. **Getting started (Feb 8):** Streamlined onboarding — import sources, connect GitHub, go. Live processing banner with stage-by-stage progress. Quick walkthrough covers priorities, filters, briefs and key actions. Data syncs silently across tabs. Theme follows OS preference automatically. **Smarter priorities (Feb 9):** Website-aware classification — urgency and themes use your domain language. Correct a category and it sticks. Competitor mentions surfaced on priorities and in briefs. Stale brief detection — Refresh badge appears when new feedback changes scope. No artificial cap on priorities. Classification, theme and brief generation rewritten for quality. **Memory (Feb 10):** Ship a brief and Circuit writes a memory — theme, volume, segment at time of ship. Correct a classification and Circuit remembers. Briefs show what Circuit remembers. MCP tools enriched — priorities flag shipping history, briefs include past context. **Batch actions (Feb 14):** Batch status change, assign, export. Markdown export — individual briefs or batch. Undo CSV import from completion screen. ### V1.0 (Feb 1–7, 2026) **Launch (Feb 1):** Feedback collection from 5 sources. AI scoring: volume, urgency, revenue impact, positive sentiment, negative sentiment, feature demand. Automatic duplicate detection. Intent classification: bug, feature, friction, complaint, praise. Trend indicators and category tagging. Weekly digest notification. **Circuit Widget (Feb 1):** Embeddable feedback widget with one-line install. Adjustable theme. Feedback intake supports widget, Slack, CSV, Sheets and manual entry. **Priority Engine (Feb 3):** Goal-based re-ranking across all priorities. Six focus lenses: User Growth, Revenue Growth, Improve Retention, Improve Delight, Bug Fixes & Quality, New Features. Score breakdown visible on each priority card. **Codebase-aware specs (Feb 3):** GitHub integration for codebase context. Specs include file paths, tech stack and naming conventions. 5 spec sections: what, why, customer voice, files, done when. Spec regeneration preserves manual edits. **MCP for Cursor and Claude Code (Feb 5):** MCP server for Cursor and Claude Code. Pull priorities, fetch specs and list recent changes from the editor. Spec format built for AI coding agents. **Versioning, privacy and dark mode (Feb 6):** Brief versioning — every edit saved, revert to any version. PII protection — customer names, emails and phone numbers stripped before AI calls. Dark mode follows system preference or toggle in Settings. **Close the loop (Feb 7):** Shipped notification emails with original feedback quoted. Per-priority customer list with feedback source and date. Priority status now tracks ready, building and shipped. --- ## Brand disambiguation **Circuit (withcircuit.com)** is an AI product management system for software teams. It is not related to: - circuit.ai — an industrial/enterprise AI company - circuitry.ai — a manufacturing decision intelligence company The correct identifier is **Circuit (withcircuit.com)** or **Circuit by withcircuit**.