Every draft has one load-bearing claim that won't survive contact. Find it before they do. Highlight your essay, thesis, case, or pitch, and Counter attacks the weak link the way an admissions officer, editor, or opposing counsel will. Read the takedown, or defend it out loud.
chrome://extensions with Developer mode on. Step-by-step below. Or try the voice round in the browser without installing anything.Counter has one job: go after the weakest thing you wrote, before the people who matter do. It doesn't flatter and it doesn't fix your prose. It finds the crack and pushes. Two ways to take the hit: on the page, or out loud.
Highlight a paragraph anywhere: the web, a PDF, Google Docs. Counter names the weakest load-bearing claim, stacks three rebuttals under it, and hands you the question your reader asks first.
Same passage, voice mode. Dr. Iyer asks one precise question and waits. No pile-on, no five-at-once, no rambling. The way a real viva or panel actually runs.
Admissions officer, op-ed editor, thesis committee, opposing counsel, VC, or a plain skeptic. Each one presses exactly where that reader presses.
Highlight a paragraph in your draft, or paste it straight into the side panel.
Counter it in writing, or hit Quiz me out loud. One tap unlocks the mic and the examiner opens the round.
In writing: the weakest claim, three rebuttals, the first question. Out loud: precise probes you answer by voice, one at a time.
What was sharp, what to tighten, and the question you weren't ready for. Then run it again before it counts.
If you've ever written something that someone else gets to poke holes in, you know the gap between "I wrote this" and "this holds up." Counter closes that gap, on the page or out loud.
Counter has one job, two ways to do it: counter your draft in writing, or quiz you on it out loud. Either way the AI is set up as the reader you'll actually face, an examiner or editor that presses on the weak link instead of flattering you. The point is pressure on the load-bearing claim, not a pat on the head.
The current version reads your active Doc and uses it as the source for a viva. The next version (in development) lets you ask the AI to sharpen specific paragraphs and apply the change to your real Doc with one tap. Tracked changes are coming. You always confirm before anything writes.
Yes. The AI speaks any of the supported languages, including Hindi, Marathi, Bengali, Tamil, Telugu, Kannada, Malayalam, Punjabi, Gujarati, Urdu, Spanish, French, German, Mandarin, and Arabic. Toggle the language inside the side panel.
Free tier: 5 drills, plus 5 more when you sign in (10 total). Individual: $5/year for 250 drills/month, six AI brains, and HD voice. Lifetime: $14.99 once for 250 drills/month forever, no recurring charge. Bring-your-own-key (Anthropic Claude only): $1/month for unlimited. Everything is free while Counter is in beta.
Only the text you explicitly select or paste. The extension doesn't read pages you haven't acted on, doesn't track browsing history, doesn't sell data. Voice audio streams directly from your browser to the AI provider via WebRTC; our servers are not in the audio path. Full privacy policy here.
Yes. Docs uses canvas rendering, so the standard right-click is intercepted. Counter handles this with a floating "Quiz me" pill that surfaces after you copy any selection (Ctrl/Cmd+C). The keyboard shortcut also works.
Counter is built by DebateIt. The same engine that powers debateai.com's voice round and six-brain panel. The founder is a national APDA debate champion. The AI cross-examination logic comes from somebody who actually won at the top of the format.
Counter isn't on the Chrome Web Store yet. The build below works exactly the way the listed version will once we ship to the store; sideloading just skips the review queue.
chrome://extensions into the address bar (Chrome won't let you click a link to it). Flip Developer mode on (top-right toggle).
⌘C (or Ctrl+C), then click the button. The side panel opens with your paragraph pre-loaded, ready to counter in writing or defend out loud.
Google Docs integration is partial. Right-click + context-menu drills work everywhere. The "open the active doc via the Docs API" path needs an OAuth client ID that isn't shipped in the public build (security). You'll see a "Connect Docs" button in the side panel that surfaces a setup hint instead of opening the consent screen. Everything else works.
Found a bug? Drop it in Discord or use the in-page feedback form on the main site. This is the active testing window.