[nishantmonu51]

Since #9881 every chat message sent the full page URL as ui_page_path, and the server failed the whole request with InvalidArgument when it exceeded 2048 bytes. Explore and canvas URLs carry dashboard state and are allowed to grow to about 13 KB, so an IN filter with roughly 75 values made chat unusable on that page. The query string also shipped filter values to the LLM for no benefit.

• The page path was only a label in the system message that lists clickable UI actions, and both agents already know what the user is viewing from their own context (explore or canvas name for the analyst agent, current file for the developer agent). The client no longer sends ui_page_path, the server ignores it, and UIContext only carries the actions. The proto field stays for wire compatibility.
• uiContextFromPB now truncates oversized labels and drops malformed actions instead of returning an error; the UI context is best-effort metadata for click_ui and should never fail a chat request.
• The label limit counts characters rather than bytes, matching the browser's truncation, so non-ASCII labels no longer fail the request either.

Steps to reproduce (before the fix):

1. Open an explore dashboard and add an IN filter with about 100 values, until location.href.length is over 2048.
2. Open the chat sidebar and send any message. It fails with invalid UI context: ui_page_path exceeds 2048 bytes.
3. Remove values until the URL is under 2048 and chat works again.

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[AdityaHegde]

1. We would need some kind of priority instead of a hard 100 limit. Definitely needs a follow up.
2. Right now, we would need some kind of signal to know the 100 limit is reached. Issue will get hidden if sometime down the line we hit the limit and new actions are not sent to agent.
3. Lets add deprecated to ui_page_path params in proto.

[nishantmonu51]

Addressed in 005f0c9:

1. Agree the cap needs a priority scheme; I will open a follow-up issue for that.
2. The server now logs a warning with received, kept and limit counts whenever any action is dropped, so hitting the limit is visible in the runtime logs. Tests assert the log.
3. ui_page_path is marked deprecated in both request messages, with the Go, swagger and TypeScript bindings regenerated.