Ship features. Not bug reports.
Circle polish issues while you build. An AI agent proposes fixes on isolated branches. You review and merge without context-switching. Your backlog stays focused on what matters.
Your backlog is full of stuff nobody wants to work on
You're building a feature. You notice the padding is off on the settings page. You tell yourself you'll fix it later. Later never comes. It goes on the backlog. A PM sees it, creates a ticket, assigns it to someone. Three days later, someone spends five minutes fixing it. The ticket took longer to triage than the actual work.
Or worse: you stop mid-feature to fix it. Now you've lost 20 minutes of context, and the feature work sits in a dirty commit history with "fix padding" mixed into "add user dashboard."
Note8 cuts the loop. Circle it while you're there. Keep building. A proposed fix shows up on its own branch. Review it when you're ready. Merge or reject in 30 seconds.
No tickets. No backlog pollution. No context-switching tax.
Catch bugs during development, fix them without stopping
1. Embed the widget on your staging site
One script tag. Works on localhost, preview deploys, staging, production—anywhere with a URL.
Developers and stakeholders both use the same widget. No separate "internal feedback" vs "user feedback" tools.
Widget captures screenshots, annotations, element selectors, console errors, and voice notes.
2. Circle issues without creating tickets
See a hover state bug while testing a feature? Click the feedback button, draw on it, submit.
Widget captures the exact element, viewport size, browser, and URL automatically.
Feedback goes to your dashboard, not your issue tracker. Skip the ticket ceremony.
3. AI agent proposes fixes on isolated branches
Agent daemon polls for new feedback, spawns your coding assistant (Claude Code, Cursor, Gemini CLI).
Every fix lives on its own git branch. Nothing touches main.
Review the diff in GitHub/GitLab. Merge, reject, or ask for changes. The agent never commits without your approval.
Why dev teams choose Note8
Developer-friendly feedback capture
Fixes on isolated branches, never on main
Works with your existing dev workflow
Self-service for non-technical stakeholders
The old way vs the Note8 way
| The Old Way | The Note8 Way |
|---|---|
| Developer sees a bug while testing | Developer sees a bug while testing |
| Opens Jira/Linear, creates ticket, fills 8 fields | Clicks feedback button, draws on the problem, hits submit |
| Assigns to self (or forgets to assign, ticket sits) | Agent proposes a fix on its own branch overnight |
| Loses context from feature work, switches to bug | Keeps building feature, reviews fix later |
| Fixes bug, commits, pushes | Reviews diff, merges in 30 seconds |
| Goes back to feature work (context re-load cost: 15 min) | Continues feature work without interruption |
| Total time: 30 min (20 min context-switching, 5 min fix, 5 min ticket) | Total time: 5 min (review + merge) |
The agent that respects your git workflow
Run the Note8 agent daemon on your machine or a dev server. It polls for new feedback and spawns your AI coding assistant to propose fixes.
What makes it developer-friendly:
Runs locally.
Your code never leaves your machine. Note8's cloud service stores feedback (screenshots, comments), not your codebase.
Uses your tools.
The agent spawns Claude Code, Cursor, or Gemini CLI—whichever you have installed. It uses your API keys, not ours.
Respects your hooks.
Pre-commit hooks, linters, test suites all run normally. The agent doesn't bypass your quality gates.
Git-safe branching.
Every fix is a new branch. Nothing merges without your approval.
Configurable daily cap.
Set a max number of fixes per day to control API costs.
Agent workflow modes
Review Branch
All approved fixes merge into a shared review branch. Live preview site runs the review branch so you can see all fixes working together before shipping to production.
Best for: Teams that want a staging environment with all pending fixes combined.
Isolated
Each fix gets its own branch and PR. No shared preview branch. Review fixes independently.
Best for: Teams with strict PR review requirements or complex CI/CD pipelines.
Collaborative
Agent works on your current branch in the project directory. No worktrees, no separate branches.
Best for: Solo developers who want fast iteration without branch overhead.
Direct
Agent works directly in the project directory without branching. High risk, high speed.
Best for: Prototyping or throwaway environments only.
See all fixes running together before you ship
When you use the review-branch workflow, the agent runs a live preview site on your machine. All approved fixes are merged into the review branch. The preview site shows how they work together.
*.preview.note8.dev)Use case:
QA tester finds 10 bugs on Friday. Agent proposes 10 fixes over the weekend. Monday morning, you review the preview site, see all 10 fixes working, merge the review branch to main. Ship.
"Fix this later" that actually happens
You're deep in a feature. You notice the mobile nav is broken, but you're mid-refactor and don't want to lose focus. What do you do?
Before Note8:
Make a mental note. Forget about it. Ship the feature with a broken mobile nav. User reports it. You fix it in a hotfix. Embarrassing.
With Note8:
Click the feedback button. Take a screenshot. Circle the broken nav. Submit. Keep building the feature. Agent proposes a fix on its own branch. You merge it before shipping.
No context loss. No mental stack overflow. No shipping broken UI.
This is the "fix this later" button that actually works. Developers use it for:
Give your PM and designer the feedback button
Your PM tests the staging site and finds a bug. What happens?
Before Note8:
PM pings you in Slack. "The delete button isn't working." You ask "which page?" PM sends a screenshot. You ask "what did you click?" PM describes the steps. You try to reproduce. Can't reproduce. You ask for more details. PM is in a meeting. Bug sits for 3 hours. You finally reproduce it. Fix takes 2 minutes.
With Note8:
PM clicks the feedback button, circles the delete button, records a 10-second voice note explaining the steps, submits. You see the screenshot, the element selector, the voice transcript. You reproduce it immediately. Fix in 2 minutes. Total time: 5 minutes, not 3 hours.
Stakeholders get:
Developers get:
Flat per-seat pricing. No surprises.
Stakeholders (PMs, designers, QA) don't count as seats. They submit via the widget and track status via the feedbacker portal. You only pay for developers who need dashboard access.
3-person startup
2 devs, 1 PM, 1 designer, 1 QA
Team plan, no extra seats, annual billing
8-person team
5 devs, 3 stakeholders
Team plan at capacity, annual billing
12-person team
8 devs, 4 stakeholders
$29 + 3 extra seats ($12), annual billing
14-day trial · Credit card required · Cancel anytime
Cheaper than Marker.io, BugHerd, and Userback at every team size
Most visual feedback tools charge per seat for everyone—including stakeholders who just submit bugs. Note8 charges only for developer seats. Your PM, designer, and QA tester submit feedback for free.
Comparison at 5 people (annual pricing):
| Tool | 5-person team (annual) | Note8 Savings |
|---|---|---|
| Note8 | $29/mo | — |
| Marker.io | $47/mo | $216/year |
| BugHerd | $42/mo | $156/year |
| Userback | ~$35-45/mo | $72-192/year |
At 15 people (10 devs, 5 stakeholders):
| Tool | 15-person team (annual) | Note8 savings |
|---|---|---|
| Note8 | $49/mo (5 included + 5 extra seats) | — |
| Marker.io | $149/mo (all 15 users need seats) | $1,200/year |
| BugHerd | $100/mo | $612/year |
| Userback | ~$105-135/mo | $672-1,032/year |
And Note8 includes AI-powered fix automation. Competitors don't.
View full comparison pages for detailed breakdowns
Fits into your existing stack
Note8 doesn't replace your tools. It plugs into them.
Git platforms
GitHub: Automatic PR creation, view/merge/close PRs from Note8 dashboard, branch linking
GitLab / Bitbucket: Agent creates branches and commits locally, you push manually or let the agent push
AI coding assistants
Claude Code, Cursor, Gemini CLI: Agent spawns whichever you have installed
MCP (Model Context Protocol): Claude Desktop and Cursor can query Note8 feedback directly without the agent daemon
Deployment platforms
Embed the widget on Vercel preview deploys, Netlify deploy previews, Cloudflare Pages branches
Widget validates origin against your allowed origins list (prevents unauthorized embedding)
CI/CD
Agent respects your pre-commit hooks, linters, and test suites
Fix branches run through your normal CI pipeline before you merge
Real problems dev teams solve with Note8
Scenario 1: QA finds 20 bugs the day before launch
Before:
QA files 20 tickets. Engineering lead triages. Assigns bugs to 5 developers. Everyone stops feature work. Bugs get fixed in a day, but planning/triage took 3 hours.
After:
QA clicks through the app with the Note8 widget, submits 20 issues in 30 minutes. Agent proposes 15 fixes overnight. Engineering lead reviews the preview site, merges 12, manually fixes 3, closes 5 as won't-fix. Launch happens on time.
Scenario 2: Designer wants to review implemented work
Before:
Designer reviews staging, takes screenshots, pastes them into Figma with annotations, shares with developer. Developer interprets the feedback, fixes issues, asks designer to review again. Three rounds of back-and-forth.
After:
Designer clicks through staging with the widget, circles spacing issues and color mismatches, submits. Developer sees exact pixel coordinates and element selectors. Fixes in one pass. Designer reviews preview site, approves, launch.
Scenario 3: Developer finds a bug mid-feature
Before:
Developer is refactoring auth. Notices the logout button doesn't work on mobile. Stops refactoring, switches to mobile-nav branch, fixes logout, commits, switches back to auth refactor. Loses 20 minutes to context-switching.
After:
Developer clicks feedback button, screenshots the mobile nav, circles the logout button, submits. Keeps refactoring. Agent proposes fix on separate branch. Developer reviews and merges after the refactor is done. Zero context loss.
Common questions from developers
Start shipping faster today
14-day free trial. Credit card required. Cancel anytime. Unlimited feedback, unlimited projects (Team plan). The agent is optional—start with just the widget and add automation when you're ready.
14-day trial · Credit card required · Cancel anytime