Skip to content

Open-source AI browser agent for Chrome and Firefox (monorepo) 🧠

Document record-bound deletions and their limits

Claude4d38da94e907
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6c636ee9a..c0eab3c85 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -22,6 +22,7 @@ This changelog was generated from the repository Git history and release tags. V
- Stop also pauses right-click menu and selection-shortcut requests made before or during the stopped task. They no longer start on their own afterwards, including after reopening the panel or in another panel; they wait in the queue, marked as paused, until you send or delete them.
- Clicks, keys and text are never sent twice when the browser loses an acknowledgement after delivery; they are reported as sent with an unknown outcome. Continue and Retry no longer repeat an unconfirmed trusted click. Stopping while a field is being filled no longer submits it. Buttons that lift or change border on hover can be clicked.
- Firefox: a page's own fractional scrolling is no longer treated as a window or zoom change, so it no longer invalidates certified decisions where Chrome keeps them; real resizes, zoom and user scrolling still do.
+- A Delete or Remove you ask for on an ordinary row without its own link (a cart item, a mail row, a table row) is no longer always refused. It proceeds when your latest request asks for the deletion and names that row by a word only that row shows, including the confirmation dialog the click opens. The same row is never deleted twice; toolbar and bulk deletions, menus without a linked button, and posts with a permalink keep their previous checks.
- Ordinary controls (filter chips, folder links, menus, tabs, toggles, draft attachment and media removal, composer tools) work before and after a correction; X and Bluesky no longer reject them as unidentified publication actions. After a correction, identical resubmissions are reported as already done, a corrected in-place save or a requested post on another platform is allowed once the earlier result is known, and requests to remove characters or hashtags are no longer treated as deleting the post. A submit-probe exception that left real publish controls unresolved is fixed.
- A correction sent while a run is working is no longer lost when the extension background restarts before the run uses it. The resumed run applies it first, once, in the order it was sent; if the run does not resume, the correction returns to the queue marked as paused, as after Stop. Clearing the conversation or closing the tab discards it.
diff --git a/docs/architecture.md b/docs/architecture.md
index aa7e7d5b6..9f6cc0d96 100644
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -101,6 +101,28 @@ result and authorization under the latest request, and a different target
words or hashtags from a post is an edit; only removing the post or record
makes deleting the original a prerequisite.
+A deletion of a record that has a permalink must name that URL in the latest
+request. A requested deletion of a record without one (a cart item, a mail or
+table row) is bound to the record instead. The page probe takes the nearest
+row, list item or article holding no other visible deletion control, or else a
+bounded container that stops at lists, landmarks, editors, headings, other
+records, other deletion controls (including hover-only ones) and 2,000
+characters, and keeps its visible text without the control's own caption. A
+menu item borrows the record of its expanded aria-controls or popover launcher.
+A confirmation dialog borrows the record of the agent's own authorized click
+only when it opened after that click was checked, within 30 seconds, and holds
+that one deletion control. The latest request must ask for a deletion (not a
+text edit) and name the record by a whole word that appears in its text and in
+no sibling record. The authorization check receives the record and the dialog
+text as untrusted data, and its quoted evidence must contain such a word. The
+same record is never deleted twice at the same step in a task, even after a
+reload, and a changed record changes the checked action. Toolbar, bulk and
+selection deletions, menus without a linked launcher, records with permalink
+evidence, and confirmation dialogs that cannot be linked get no record and stay
+blocked. Matching is by whole words, so inflected forms and requests in
+languages without word spacing usually need the item's name as shown.
+Completion after such a deletion uses the ordinary post-submit checks.
+
When a runtime check ends a run, the chat shows a plain-language answer: what
happened and what to check next. The exact diagnostic stays in verbose tool
rows, later model turns and traces.
diff --git a/docs/social-publication-contract.md b/docs/social-publication-contract.md
index ab181cbaa..3cf1b3b40 100644
--- a/docs/social-publication-contract.md
+++ b/docs/social-publication-contract.md
@@ -36,6 +36,7 @@ An exhausted publication check stops the run with a clear failure message and ap
- Recognize Bluesky desktop composer launchers as non-submitting controls outside forms/dialogs. Actual publish buttons retain the full contract checks.
- Ordinary X/Bluesky controls (menus, tabs, settings toggles, reply openers, composer tools with non-publish ids) pass without a contract; unidentified controls are reported as unidentified and stay blocked. An unmodified Enter in the app-marked post editor edits the draft.
- Repeating an identical post under a revised task is blocked and reported as already published (verified) or already attempted under the earlier instruction.
+- Deleting a post whose record shows its permalink (X, Bluesky, LinkedIn, GitHub release or commit links) or a native Mastodon status keeps the exact URL rule. The visible-text binding for requested deletions of ordinary rows (see `architecture.md`) never applies to records with permalink evidence.
- Markdown blockquote markers copied from a chat answer are formatting, not post text: an exact body whose continuation lines all carry `>` markers is published as the rendered text. Greentext (every line quoted, no empty quoted line) keeps its characters.
- Recognize the modal Cancel and Keep editing controls as non-submitting recovery actions, rejecting conflicting publish labels, test IDs, or form ownership.
- A corrected replacement after an uncertain text write can proceed only after a read-only digest proves the original replacement landed in the same document and field. Changed, incomplete, or unavailable readbacks retain the block; generic page reads never clear it.