Repository navigation
Conversation
Search returned thread replies with a `?thread_ts=<root>` permalink and no thread_ts field, so every page containing a reply failed with account_mismatch. conversations.replies also repeats the root beside `limit` replies on every page and returns pages newest first, so threads longer than one page failed as response_incompatible. Accept the exact permalink or the permalink plus a single valid thread_ts, derive the thread from it and keep it in sourceUrl. Allow the root beside `limit` replies, drop it from continuation pages, sort each read ascending and document that a continuation returns older replies. `oldest` is not used because it skips replies. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
Thread transfer impact
This comment will update automatically after the next completed run. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Slack search and thread reads in the work browser go through the DOM. That is slow and breaks when the UI changes. The work browser had also stopped being served: the installed official nightly 0.0.46-nightly.20261013.3053 does not include it, so no
work_browser_*tools were listed.This branch ports the work-browser commits from
feat/work-browser-mcp-nightly(5482f37480, the source of private build work-browser.9) ontov0.0.46-nightly.20261013.3053(6524a8d). The base branchbase/nightly-20261013.3053points at that tag, so this diff contains only the work-browser changes. On top it adds:readBackendsper account and operation (dom|api). The default stays DOM.apiis accepted only forveratoSlack search and read, which passed capability validation. There is no automatic fallback.SlackPageApi.ts) that runs in the existing browser session through the server-owned tab. It verifies identity on every page, allowlists methods and origin, bounds time, size and pages, and returns closed error codes. Cursors and references are bound to the account, identity, backend and query.?thread_ts=<root>.conversations.repliesrepeats the root on every page and returns pages newest first.oldestis not used because it drops replies.Checks, run through the DevBox heavy-check queue:
build-exepassed.Private package
0.0.46-nightly.20261013.3053-work-browser.10is staged in the runtime versions directory. It is not active yet. Activation and the post-restart MCP verification (AC6) are tracked outside this PR.🤖 Generated with Claude Code