feat(APP-1004): address the assistant design feedback round 2 - #1350
Merged
tyhonchik merged 3 commits intoSep 4, 2026
Conversation
tyhonchik
force-pushed
the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
from
August 31, 2026 12:39
cb8466f to
37fc879
Compare
|
E2E results (preview) Smoke
|
tyhonchik
force-pushed
the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
from
September 2, 2026 15:13
37fc879 to
ab22ab3
Compare
tyhonchik
force-pushed
the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
from
September 2, 2026 15:21
ab22ab3 to
e359bab
Compare
tyhonchik
force-pushed
the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
from
September 2, 2026 16:05
e359bab to
15a897f
Compare
tyhonchik
force-pushed
the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
from
September 2, 2026 16:07
15a897f to
559ebaf
Compare
The header and composer controls (new chat, collapse, back, add attachment) become gov-ui-kit buttons and drop their tooltips, the "Email support" escape hatch follows the app's plain link style — no underline, an external-link icon, opening in a new tab — and typing in a fresh chat no longer bounces the layout: the suggestion chips retire through visibility instead of unmounting. The ticket card gains a bottom margin so text following it in the same message no longer sits against its edge. Nothing links to Linear anymore: the createLinearTicket tool output drops the issue URL at the contract level — users have no access to the workspace, and anything in the output also reaches the model, which would narrate the link into the chat. The success card and the past-requests view quote the ticket reference instead; stored tickets and history entries from before the change still parse, the stale field is stripped.
…e it when none do The AI Gateway fails a call over to the next model when the upstream errors. The failure actually seen in production is the opposite: the provider accepts the call and goes quiet, so nothing errors and nothing fails over. The assistant logs have the same prompt on the same provider answering in 1.0s, 1.7s and 2.3s, then once in 47.8s, then once not at all. No AI SDK timeout helps either — every one of them (totalMs, stepMs, firstChunkMs, chunkMs) aborts the shared signal, and an abort is not an error, so neither the SDK's retries nor the Gateway's fallback react to it. So the stall becomes a failover here: a turn now runs on the first model that actually starts answering. A model that produces no content within its deadline is abandoned for the next one, which is invisible to the user (no content had arrived) and cannot duplicate a ticket (no tool had run). The chunks read while waiting are replayed in front of the returned stream. The deadline is measured by reading the attempt — streamText produces nothing until its stream is pulled, so an onChunk callback would never fire in time. When every model stays silent, the wall-clock cap ends the turn, and that no longer fails silently either. The SDK closes such a stream with an `abort` chunk, which the widget renders as nothing at all: an empty message, no error, nothing in Sentry. It is now rewritten into a `timeout` error the widget can show, reported, and the turn is refunded so a retry does not cost the user twice. A stop from the composer aborts the stream the same way and is left alone. Also updates the support-chat smoke test to the ticket card this branch ships: the identifier is a reference now, not a link out to Linear.
tyhonchik
force-pushed
the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
from
September 4, 2026 13:49
578286d to
f2421c3
Compare
tyhonchik
deleted the
app-1004-ai-assistant-iteration-based-on-feedback-v2
branch
September 4, 2026 15:05
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
4 participants
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.
This addresses Evan's second feedback round on the support assistant (APP-1004, comment). Previously the panel's icon controls were bespoke tooltip buttons, the email escape hatch was an underlined in-tab link, typing the first character of a fresh chat bounced the welcome layout, and the created-ticket card linked out to Linear. Now every control is a gov-ui-kit button, the link follows the app's plain link style in a new tab, the layout holds still, and nothing in the chat references Linear URLs — the ticket travels as a reference, not a link.
Changes
createTicketToolOutputSchemadropsurlat the contract level: users have no access to the workspace, and anything in the tool output also reaches the model, which would narrate the link into the chat. The service (createLinearTicket,linearGateway,sessionStore), the success card and the past-requests view now carry only the ticketidentifier, rendered as aTag. Stored tickets and localStorage history entries from before the change still parse — the stale field is stripped, not rejected.Button(tertiary/sm, icon-only) and lose their tooltips — the accessible name moves toaria-label. The send/stop controls keep their bespoke shape (no matchingIconTypefor the arrow/square glyphs).LINK_EXTERNALicon,target="_blank"— clicking it no longer risks navigating the app tab. Styled after the gov-ui-kitLinkrather than using it: its smallest type scale is too large for the caption line under the composer.visibilitywith their height kept.mt-3only, so assistant text following it in the same message sat against its border; it now carries symmetricmy-3withfirst:mt-0 last:mb-0.Note
Point 1 of the feedback (header not lined up with the navbar) is already fixed on
mainby #1303, which merged after the comment was written — measured live with Playwright on a DAO page: both bottom borders sit at exactly 91px. No change here.The PR spans both release scopes, so it carries two changesets:
@aragon/assistant-chatminor +@aragon/apppatch, and@aragon/assistantpatch +@aragon/assistant-contractsminor. Until the assistant service redeploys it keeps sendingurlin the tool output — the widget ignores the extra field, so the two can ship in either order.🤖 Generated with Claude Code