Precise screenshots
Visible area, full page, a pointed element or a drawn zone — plus a color picker with real WCAG contrast. Annotate with pen, arrow or text.
✦ Solo or as a team · the context compiler
Compile your context.
Compile your context.
Feed your AI.
Your AI can't see your screen — it guesses. Feedzy.ai compiles the living context of your page (element, CSS selector, JS error, detected component) and delivers it ready to paste to Claude, ChatGPT, Cursor or Aider. 100% local, no account.
No account · nothing leaves until you send · auto secret scrubbing
Zero-knowledge
100% local by default
Chrome · Edge · Brave
Claude · ChatGPT · Cursor · Aider — and your IDE
Watch a bug become a prompt.
Compile real context and feed your AI — the extension's exact flow — before you even download it.
No download · everything stays on your deviceHow it works
Talk. Target. Execute.
From your feedback in plain human language to running code: you talk, you target, Feedzy.ai compiles the context — your AI executes.
-
Talk or type
Say your feedback like you would to a coworker, by voice or keyboard. It's your intent, in plain human language — not a magic click.
-
Target & enrich
Point at the element, the area, the error. Feedzy.ai grafts the runtime context onto it: CSS selector, detected component, screenshot, JS and network errors.
-
Execute
Your AI gets a crystal-clear prompt — readable by you, calibrated for it — and gets to work on the first try. No more « which button? », no more retyped stack traces.
How does « Compile » work?
It reads the fiber, not just the DOMOn click, Feedzy.ai generates a unique CSS selector client-side, then reads the React fiber (or the Vue instance / the Angular context) to name the actual component — and in a dev build, down to its file and line.
Works with
It feeds your AI. It doesn't replace it.
Feedzy.ai doesn't lock you in: it's the context layer upstream of all your AIs. Switch models whenever you want — your context follows you.
Web AI
ClaudeChatGPTGeminiPerplexityGrokLe ChatDeepSeek
IDE & dev
CursorAiderclipboardMarkdownIDE bridge — and your own domains
The fuel
Your AI reads your code. It can't see your page.
AI-context tools only read your static code. Feedzy.ai captures the runtime: the living element, the error the moment it happens, what you point at on screen.
Errors caught on their own
JavaScript errors, failing network requests and the interaction trail are attached automatically — never your passwords or your cookies.
Element + detected component
Point at an element: Feedzy.ai captures its CSS selector, its computed styles and the detected React, Vue or Angular component (with the source file in dev).
Voice note
Dictate your feedback: Chrome’s built-in dictation transcribes it, free and keyless — Chrome then sends the audio to Google. To keep everything in, use the ✨ mic with your own OpenAI Whisper key.
Feed your AI or your IDE
The same package, injected in one click into Claude, ChatGPT, Cursor and Aider — or pushed into your IDE’s chat, terminal or a file via the bridge, or copied.
GitHub files
Attach files or folders from your repos to give the AI the code context.
How do you catch the errors?
Interception from document_start onThe monitor hooks into document_start and listens for console.error, window.onerror and promise rejections — even errors that blow up before hydration land in the bucket. The network? fetch/XHR wrapped, failures only — never the body, the cookies or the Authorization.
Security & privacy
Local-first and zero-knowledge: 0 readable data on the server.
"Feed the AI" doesn't mean "dump everything into the cloud." Feedzy.ai feeds your AI all the context — and nothing else. On your machine, under your control.
- You choose what you sendFeedzy.ai strips emails, tokens, cards and IBAN before sending — and re-checks on the way back from the AI (two-way scrub).
- Nothing leaves by defaultLocally, nothing leaves your machine until you send. Encrypted cloud is just an option, opt-in.
- End-to-end encryptedWhen you share with your team, the server only ever sees gibberish — never your data or your keys (OPAQUE, AES-256-GCM).
- Even the AI can stay localPlug in an on-device model (Gemini Nano): you can feed without anything leaving at all.
0
readable data on the server
On your own, nothing leaves your machine. On free multi-device, everything goes through your own folder, encrypted — we see nothing. And you stay in control: recovery key and device revocation included.
One exception, and you are the one who triggers it: if you turn on the hosted MCP relay, you entrust your workspace key to the server so it can decrypt your queue on demand. Opt-in, revocable at any time, and every decryption is logged.
« Password never transmitted »?
OPAQUE authAuthentication uses the OPAQUE protocol: your password never leaves the device, not even as a hash. The server proves it's you without ever seeing it go by. The events, meanwhile, encrypted AES-256-GCM client-side — the key never leaves.
Team
The best prompt isn't written alone.
Not a ticket board, not a process to follow. Everyone brings their feeds, the team refines the prompt together, then feeds it to the AI — once, with the right context.
Everyone's got their feeds
Every member captures their feedback and works through it (or not) at their own pace. Zero forced process, no mandatory columns.
1 / 4
« Desync-proof, guaranteed »?
Determinism, not a promiseFeedzy.ai is event-sourced: a deterministic reducer replays the same events log → the same state on every device and for every teammate. Even undo goes through compensating events. No copy that drifts, because there is no copy — a single source.
Free vs Max Cloud
Everything Feedzy.ai can do.
Not a chat wrapper, not a bug tracker: a context compiler. Hover a row for the explanation.
| Feature | The extension | Max Cloud |
|---|---|---|
| Capture & feedback | ||
| ✓ | ✓ | |
| ✓ | ✓ | |
| ✓ | ✓ | |
| ✓ | ✓ | |
| ✓ | ✓ | |
| Sync | ||
| ✓ | ✓ | |
| — | ✓ | |
| — | 5 GB/seat, pooled | |
| Collaboration | ||
| — | ✓ | |
| — | ✓ | |
| — | ✓ | |
| Security | ||
| ✓ | ✓ | |
| — | ✓ | |
Pricing
The extension is free. 3 € per seat for the cloud, solo or as a team.
Local is, and always will be, free. You only pay for the cloud — online storage, remote access, collaboration. Per seat, volume discount from the 1ˢᵗ license.
The extension
Forever, local, with or without an account.
0 €
- All the capture (screen, zone, element + component, color + WCAG, JS & network errors, voice)
- Feed Claude, ChatGPT, Cursor, Aider + IDE bridge
- Your agent reads your Feeds through the local MCP — and writes back
- Multi-device via your own folder (BYOS)
- End-to-end encryption, on your devices as in your folder
Popular
Max Cloud ✦
people
The cloud, solo or with others — storage, remote access, collaboration.
3 € / month
3 € / person / month
The more of you there are, the cheaper it gets — the discount applies to every person.
- Everything in free
- Solo: online storage + your Feeds on every device you own
- Solo: real-time sync + hosted MCP relay (you then entrust your workspace key to the relay — opt-in, revocable, every decryption logged)
- As a team: collaboration on the prompt + roles & permissions
- As a team: encrypted sharing (ZK) & public widget
Go Max Cloud
Slider: 1 = just you · 2+ = your team.
FAQ
The questions people ask us.
What is Feedzy.ai?
A context compiler: a free Chrome extension that compiles everything your AI needs onto one page — element + CSS selector + detected component, annotated screenshot, color + WCAG contrast, JavaScript and network errors, GitHub files, voice note — and delivers it ready to paste into Claude, ChatGPT, Cursor or Aider.
Is it free?
Yes, the extension is free forever: capture, sending to your AI and multi-device sync through « your own folder ». The Max Cloud version (3 € per person per month, volume discount) adds the cloud: online storage, remote access, real-time sync and — as a team — collaboration on the prompt, sharing and the public widget.
Is my data private?
Yes. Nothing leaves until you send, and secrets (emails, tokens, cards, IBANs) are stripped before sending. Team sharing is end-to-end encrypted: the server never sees your data or your keys (zero-knowledge). With free multi-device, everything goes through a folder you choose, encrypted with AES-256-GCM.
Which AIs does it work with?
Feedzy.ai delivers the context — ready to paste or injected in one click — into Claude, ChatGPT, Cursor and Aider, and even on the domains you add. You're not locked in: switch models whenever you want.
How do I give Cursor or Copilot the context of a bug?
Point at the element and the error in your page: Feedzy.ai compiles the selector, the styles, the component and the stack trace, then sends it into Cursor in one click, or into your IDE’s chat — Copilot Chat included —, its terminal or a file, through the “Feedzy.ai — Pont IDE” extension.
Does Feedzy.ai call an AI on my behalf?
No, by default. Feedzy.ai builds the context package; you're the one who hands it to the AI of your choice, with your key. Your data stays with you, and secrets are stripped before sending.
Do I need to create an account?
No. The extension is free and works 100% locally, with no account and no server. An account lets you buy Max Cloud seats, or join the Workspace of someone who assigns you one: it’s the seat, not the account, that unlocks cloud sync.
Which browsers does it work on?
Any browser based on Chromium 120 or newer: Google Chrome, Microsoft Edge, and Brave.
Start solo in 30 seconds. Move to the cloud whenever you want.
Add Feedzy.ai to Chrome, compile your first context, feed your AI. Max Cloud is waiting for the day you want your feeds everywhere — or your whole team on the same prompt.