Show HN: Coding agent where a second agent QAs every PR in a real browser
A new coding agent called NOTES.ASM automates the process of handling pull requests (PRs) by using an autonomous engineer. Users can simply mention tasks to their editor, and the agent will create tickets, write code, and perform quality assurance overnight. This service is currently in closed alpha, offering free access while it develops and promising discounts for early users when paid plans are introduced.
- ▪NOTES.ASM allows users to mention tasks to an editor, which automatically creates tickets.
- ▪An autonomous agent handles the coding and QA process overnight, providing users with PRs by morning.
- ▪The service is currently in closed alpha and is free during this phase, with future paid plans expected.
2 outlets in our directory ran this story, first to last over 12 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Notesasm |
| Canonical URL | https://www.notesasm.com/ |
| Publication time | Tue, 19 May 2026 18:54:10 +0000 |
| Retrieval time | 2026-05-19T19:04:57.948Z |
| Last seen | 2026-05-19T19:04:57.948Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ONEr1CsVrw_W · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
NOTES.ASM // v0.2.alpha the loop what it does get access app Closed alpha · request access Mention it.Get a PR. Bug. Feature. Refactor. Copy tweak. Doesn't matter. You don't write tickets — your editor does. You don't write code — your overnight engineer does. You stay in flow during the day, wake up to PRs. hire your automated engineer // closed alpha · free while we ship · alpha users get a permanent discount when paid plans land ; 60s DEMO — file ticket → walk away → wake up to PRs ▶ click to play STAGE 01 the loop Three steps. None of them are "write the ticket." 01 / TALK Mention it to your editor Working in Claude Code and you think of the next thing — a bug, a feature, a refactor, a copy change. Just say it. Claude files the ticket. Zero context-switch.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Notesasm.
Discussion
0 commentsMore from Notesasm
