Filing into issue trackers
On this page
ADR 0003 built the outbound integrations layer and, in the same breath, ruled out the trackers: storing a GitHub token against a room id would mean anyone holding the share link could write to the repository, and a leaked link would be a leaked credential. That reasoning was right and it has not changed.
What changed is the shape of the answer. A destination's configuration has two halves, and only one of them is the room's business. Where to file is not a secret and the room keeps it; what authorises the filing is, so it stays in the browser of the person doing it. The reviewer who found the bug is the one best placed to describe it, and now they can, without an account and without handing their token to anyone.
New
- File a thread into GitHub, Linear or Jira. Open an annotation and file it as an issue, one at a time and only when you ask. The issue carries the annotation's own words, who wrote it, the priority and the page it was left on, so it reads on its own without anyone opening the link first. The created issue's URL is posted back into the thread as a reply.
- Your token stays in your browser. A share link is meant to be handed around, so a room storing an API token would make every link a tracker credential. The room keeps only the harmless half — the repository, the project key, the Jira site. The token lives in your own browser, is asked for once, and rides only the single request that files the issue.
- Open the board with ⌘B. The full-screen triage board now has a shortcut, so you can jump between reading one thread and sorting all of them without reaching for the panel first. Press it again to go back.
Improved
- Priority is legible. Priority used to be a tinted capsule that set its label in the accent colour — 2.5:1 for medium on a light panel, and the loudest object in a comment row for something you rarely read first. The signal icon now carries the colour and the word is set in the same muted ink as the status beside it.
Fixed
- Agents can reply to any annotation. An agent's reply or resolve summary only landed on comments. On an area, a selection or an inspected element — which is most of what a real room contains — it was silently dropped. Every annotation owns a thread, so every annotation now takes a reply.
- A disconnected agent says so. Writing to a room whose connection had dropped came back as "annotation not found", which sent the agent hunting for an id that was perfectly fine. It now names the disconnection and says to reconnect.
- Dialogs dim the whole screen. The share and support dialogs darkened the page but left the side panels at full brightness, so the overlay had two bright holes in it.
- The board's first card is whole. The top edge of the first card in each column was shaved flat by the column's own scroll area, so one corner of every column looked broken.
More releases
Try MarkLayer
Paste any URL at marklayer.app and annotate the live page in your browser. No install, no account, no sign-up. Recipients of your share links don't need to install anything either.
Annotate a page