Notesasm
Show HN: Coding agent where a second agent QAs every PR in a real browser
Last verified:
What is Notesasm?
Notesasm is an autonomous development assistant that converts casual notes or in-editor mentions into tracked engineering work and pull requests. It integrates with developer tooling (editors, Claude Code via MCP, GitHub, and browser QA) to capture fixes and feature requests, autonomously clone a repository, implement changes, run real-browser quality assurance, and open a PR with screenshots and video. The product is designed to learn a project's workspace, respect ticket dependencies, and retry failed QA attempts up to configurable limits while keeping code within the user's repository via ephemeral clones. Notesasm targets individual developers and engineering teams who want to capture spontaneous ideas or quick bug reports without context switching, and to offload routine implementation and verification tasks to an autonomous agent that works on the user's schedule.
Notesasm pricing
Pricing model: Freemium
Website describes availability during a closed alpha and mentions a free access phase for early users; detailed public pricing tiers and paid plan feature lists are not published on the site. The product currently offers free access for closed-alpha users who sign up or request a demo, and future paid plans (details unspecified) are implied but not listed with exact pricing or feature breakdown on the website.
Notesasm pros
- Files tickets directly from your editor without context switching
- Integrates as an MCP server for Claude Code sessions
- Autonomous agent clones your repo to make real changes
- Runs real-browser QA on preview deployments
- Opens pull requests with screenshots and video evidence
- Learns and adapts to your workspace over time
- Respects ticket dependencies when scheduling work
- Self-corrects and retries failed QA attempts
- Keeps code in your repository using ephemeral clones
- Generates PRs that include QA artifacts for easier review
- Allows scheduling (night shifts) for predictable unattended work
- Provides a dashboard to generate tokens and manage integration
- Minimizes manual hand-off between reporting and implementation
- Supports tying into GitHub so changes live in the same source control
- Designed for low-friction setup with a single MCP add command
Notesasm cons
- Limited to workflows compatible with Claude Code / MCP integrations
- Requires access to repo and deployment previews for QA
- Alpha/closed access may restrict availability
- May need configuration for complex monorepos or uncommon build systems
- Autonomous changes still require human review before merge
- Ephemeral clones mean debugging requires reproducing locally sometimes
- Real-browser QA may increase resource usage and require credentials
- Behavior depends on quality of prompts/mentions left in-editor
- Retries limited (e.g., up to three) which may still leave flakiness
- Tight coupling to specific LLM providers may limit flexibility
Frequently asked questions about Notesasm
How do I create a ticket from my editor?
Within a Claude Code session or any configured MCP client you mention the desired fix or feature (for example, “create a ticket on notesasm: fix the regex for quoted emails”), and Notes ASM records that note as a ticket for later autonomous processing.
Which LLMs or integrations does Notes ASM work with?
Notes ASM is built to integrate with Claude Code via MCP and connects with supported LLM providers; the site emphasizes integration with Anthropic/Claude for the autonomous agent flow.
How does Notes ASM make changes to my repository?
When scheduled, the agent creates an ephemeral clone of your repository, implements the requested changes, runs the project's tests and QA workflows, and then opens a pull request in your repository so code stays under your control.
What kind of QA does Notes ASM run?
Notes ASM performs real-browser quality assurance against preview deployments and captures screenshots and video as evidence; it will retry failed QA up to its configured retry limit to self-correct before surfacing the PR for review.
Is Notes ASM safe to give access to my private repo?
The platform uses ephemeral clones so code changes are made in isolated clones and pull requests are opened back into your repository; however, you must grant the integration repository access and create a token from the dashboard to authorize the service.
Can Notes ASM handle complex or multi-repo projects?
Notes ASM is designed to learn your workspace and respect ticket dependencies, but complex monorepos or unconventional build processes may require additional configuration or initial setup to ensure the agent can run builds and QA correctly.
How do I control when the agent runs (e.g., night work)?
You can schedule autonomous runs (referred to as predictable night shifts) so the agent performs work on your timetable, allowing fixes and PRs to be produced while you sleep or outside working hours.
What happens if the autonomous QA keeps failing?
The agent will attempt self-correction and retry QA a limited number of times (the site describes retries up to a configured count); if QA still fails, the ticket or attempt will be surfaced for human review and further direction.
How do I get started or sign up?
Sign-up during the closed alpha is available from the site—users request access or a demo and can generate an authorization token from their dashboard to connect the MCP integration used in Claude Code.
Is there public pricing and a paid plan today?
At the time of the site information, Notes ASM is in a closed alpha with free access for early users; the site does not list public paid plans or pricing breakdowns yet and indicates that detailed commercial plans will be published later.