feat(webapp,sdk): dashboard agent plan enforcement, component gallery — and fixes by kathiekiwi · Pull Request #4516 · triggerdotdev/trigger.dev

kathiekiwi · 2026-08-05T22:34:17Z

Plan enforcement for the dashboard agent — message quota and watch limits — plus the component gallery, fixes and test hardening from the same stack (#4548, #4549, #4550, #4552, #4556 merged here).

Plan enforcement (TRI-12863)

Agent message quota. The Free-plan allowance becomes a real server-side limit with a durable counter. New agent_message_usage table keyed (organization_id, period) — deliberately not joined to chats, so deleting a chat can't free quota within the period. Both send paths count one user message (wakes never count) and refuse at the cap with 403 message_quota_reached, which the client renders as an upgrade panel, never a silent drop. The refusal code is a single shared constant on both sides.

Watch limits. A watch whose window exceeds the plan's agentWatchMaxHours, or that would push the org past its agentWatchers count, is refused with watch_limit_reached (409 on the API, an upgrade hint on the card). Plan limits only tighten the existing code ceilings (min(plan, 24h), per-chat cap of 3 still applies). A plan limit of zero means zero, not unlimited. Questions answerable instantly are answered before any plan refusal — a one-shot consumes no slot and never sees an upgrade nag.

Fails open by design. Cloud ships the actual per-plan numbers separately (TRI-12863 P0). Until then absent limits resolve to the unlimited sentinel and the upgrade UI is gated on billing presence — self-hosted sees no cap, no upsell, with tests proving the fallback. Both quotas are nudges, not security boundaries: a failing limit read never blocks a send.

Component gallery

An admin-only gallery of every agent card state: five storybook.agent-* pages (chat UI, view blocks, report, investigation, watch) with their shared shell and manifest, demo fixtures, two demo-only cards, toast examples, and the screenshot script. No LLM and no data — every state renders from fixtures under dashboard-agent/demo/, never reachable from a production path. Designers and reviewers can look at every state, including the report states, without seeding anything.

And fixes

SDK: watch-mode chat subscriptions survive quiet windows (TRI-13065, TRI-13070) — watch mode keeps reconnecting across empty long-poll windows and only stops on abort or a settled session; a passive subscriber can no longer stop a turn it doesn't own (stopOnAbort is explicit, default off). Review findings fixed alongside: a superseded stream's async teardown no longer removes the live successor's abort controller or multi-tab claim, and stopping a generation hands the chat back to the user's other tabs.

Query boundary pinned end-to-end (TRI-11165) — a route-level test drives api.v1.query with a real signed environment JWT (writes refused before ClickHouse, a read passes); readonly=1 made non-overridable; a per-turn cap stops the model burning a turn rewriting a query it can't fix (deterministic SQL errors only — busy/transport rejections don't count).

chat.agent durability regression suite (TRI-11166) — testcontainers-backed coverage of the two audit criticals (cross-tenant isolation, no duplicate mid-stream turn, both control-broken) plus crash-resume, cursor-based refresh, clean rollback of a mid-write turn failure (torn by a real constraint violation), and OOM-restart replay.

Investigation sweep backoff — stale investigations get an attempt counter and backoff so a poison row can't pin the sweep queue head (migration 0005: sweep_attempts, last_sweep_attempt_at).

Screenshots

🤖 Generated with Claude Code

changeset-bot · 2026-08-05T22:34:23Z

🦋 Changeset detected

Latest commit: f03dfd9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 27 packages

Name	Type
@trigger.dev/sdk	Patch
@trigger.dev/python	Patch
@internal/dashboard-agent	Patch
@internal/sdk-compat-tests	Patch
@trigger.dev/build	Patch
@trigger.dev/core	Patch
@trigger.dev/react-hooks	Patch
@trigger.dev/redis-worker	Patch
@trigger.dev/rsc	Patch
@trigger.dev/schema-to-json	Patch
@trigger.dev/database	Patch
@trigger.dev/otlp-importer	Patch
@trigger.dev/rbac	Patch
@trigger.dev/sso	Patch
trigger.dev	Patch
@internal/cache	Patch
@internal/clickhouse	Patch
@internal/llm-model-catalog	Patch
@internal/metrics-pipeline	Patch
@internal/redis	Patch
@internal/replication	Patch
@internal/run-engine	Patch
@internal/run-store	Patch
@internal/schedule-engine	Patch
@internal/testcontainers	Patch
@internal/tracing	Patch
@internal/tsql	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

coderabbitai · 2026-08-05T22:34:25Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

Added client-safe dashboard-agent demo fixtures for investigations, diagnoses, charts, intents, watches, messages, reports, and identifiers. Added reusable chart and intent components. Replaced the agent Storybook route with a manifest-driven gallery for chat, view blocks, reports, investigations, watches, prompts, banners, and wake states. Added dedicated Storybook routes for view blocks, reports, investigations, and watches. Added quota and watch-limit enforcement, query safety handling, investigation sweep recovery, durable chat and tenant-isolation tests, and SDK stream lifecycle updates.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 30.43% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main changes: dashboard agent plan enforcement, the component gallery, and related fixes.
Description check	✅ Passed	The description is detailed and on-topic, and it covers the implementation, testing, changelog content, issue references, and screenshots despite missing template headings.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/agent-storybook-gallery

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pkg-pr-new · 2026-08-08T12:31:09Z

Open in StackBlitz

@trigger.dev/build

npm i https://pkg.pr.new/@trigger.dev/build@c56e3e5

trigger.dev

npm i https://pkg.pr.new/trigger.dev@c56e3e5

@trigger.dev/core

npm i https://pkg.pr.new/@trigger.dev/core@c56e3e5

@trigger.dev/python

npm i https://pkg.pr.new/@trigger.dev/python@c56e3e5

@trigger.dev/react-hooks

npm i https://pkg.pr.new/@trigger.dev/react-hooks@c56e3e5

@trigger.dev/redis-worker

npm i https://pkg.pr.new/@trigger.dev/redis-worker@c56e3e5

@trigger.dev/rsc

npm i https://pkg.pr.new/@trigger.dev/rsc@c56e3e5

@trigger.dev/schema-to-json

npm i https://pkg.pr.new/@trigger.dev/schema-to-json@c56e3e5

@trigger.dev/sdk

npm i https://pkg.pr.new/@trigger.dev/sdk@c56e3e5

commit: c56e3e5

coderabbitai · 2026-08-08T14:56:06Z

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

…4525)

coderabbitai · 2026-08-12T07:53:02Z

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

…f vanishing

Two related fixes to the chat transport's watch/read-only subscription lifecycle. **TRI-13065** — In watch mode the chat stream died at the first long-poll window boundary after a turn completed: the EOF-reconnect path was gated on `isStreaming`, which turn-complete clears, so a watcher stopped hearing later turns. Watch mode now keeps reconnecting across quiet windows and only stops on abort or a settled session. The bounded give-up budget still applies to normal (mid-turn) streams, but not to watch mode, where empty windows are expected. **TRI-13070** — `reconnectToStream` derived mutation rights from mere signal presence (`sendStopOnAbort: !!options.abortSignal`), so a passive/read-only subscriber that passed an abortSignal would append a `{kind:"stop"}` to `.in` on unmount and could stop a turn it didn't own. Subscription lifecycle is not session ownership: `reconnectToStream` now takes an explicit `stopOnAbort` option that defaults to `false`, and the owning turn paths (`sendMessages`, `sendAction`) pass `sendStopOnAbort: true` explicitly. A read-only subscription ending never mutates the session; it still cancels its own request.

Without a billing client there is no plan limit to read, but both cached readers still hit the cache store first. On an install whose cache Redis is unreachable that stalls the caller through the full reconnect cycle (~10s per read), which timed out watch creation.

…the run

…olved limit over the client constant

…ee plan's

…pent

…is spent

…he last turn completed

…es up

…F-16 at ingest

… persist

## Summary 4 new features, 24 improvements, 10 bug fixes. ## Highlights - Allow `trigger deploy` to authenticate with an environment API key from `TRIGGER_ACCESS_TOKEN`. ([#4561](#4561)) ## Improvements - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - The dev environment onboarding now tracks real progress. After you run `init`, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent. ([#4563](#4563)) The `init` scaffold now imports from `@trigger.dev/sdk` instead of the deprecated `@trigger.dev/sdk/v3` subpath. - Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster. ([#4551](#4551)) - The current-worker API now reports each task's queue, so you can see which tasks write to a given queue. ([#4525](#4525)) - Watch-mode chat streams now survive quiet windows and page reloads, and a reply cut off by a lost connection shows an error instead of appearing finished. Aborting a resumed subscription only closes your local stream — call `stopGeneration(chatId)` or pass `stopOnAbort: true` to stop the run. Also fixed a race where quickly restarting a stream could break stop and reconnect, and stopping a chat now hands it back to your other tabs instead of leaving them read-only. ([#4516](#4516)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - The dashboard agent now has a monthly message allowance and plan-based limits on watches. Queries stay read-only with clearer errors when busy, and messages with unusual characters no longer fail to send. ([#4516](#4516)) - Meet the dashboard agent: a chat in every environment that answers questions about your runs, queues, errors and health with real data and links, replacing Ask AI everywhere it used to appear. Investigate a failed run, an error, a backed-up queue or a run that hasn't started to get a worked-through answer — what happened, why, and how to fix it, with every claim linked to the runs, errors and deploys behind it. It reads your data read-only, works on preview and dev branches with that branch's own data, and reads the same everywhere — dashboard, terminal, editor. A very long chat keeps working: the agent summarises the earlier part and carries on. **Watch…** on a run, queue, error or the health report tells you when things change: a run finishes, a queue clears or grows past a number you pick, an error comes back, an environment recovers. The answer arrives in the chat and, if you want, by email, Slack or webhook — and the agent can look into bad news on its own. A watch reaches you on any browser you sign in from, without opening the chat first. A sample of conversations is scored automatically so the agent keeps getting better; only the score and a one-line summary are kept, never your messages, data or code, and we can switch it off for your organization on request. Ask the agent instead of the Docs buttons in page headers — they stay there when the agent isn't available to you. Separately, a queue's wait times, peak depth, throughput and throttling can now be read from the API. ([#4418](#4418)) - Add backend support for delaying cron schedules within a specified window with a minimum of 60 seconds. ([#4566](#4566)) - Reduced recurring background database load from the billing-limit recovery check, so paused environments are reconciled with less overhead. ([#4590](#4590)) - Validating a schedule when deploying or updating a schedule now does less work on projects with many preview branches, so those operations stay fast as branches accumulate. ([#4598](#4598)) - Project pages now load faster for projects with a large number of preview branches, by no longer loading archived branch environments that aren't shown. ([#4595](#4595)) - Database queries that filter on a list of values now reuse cached query plans more consistently, instead of forcing the database to re-plan whenever the list length changes. ([#4480](#4480)) - Routine cleanup of old dashboard agent data now runs on its own schedule. ([#4599](#4599)) - Database connection metrics are now reported for every configured database connection instead of only the primary one, and stay accurate regardless of connection type. ([#4541](#4541)) - Deployment-related API endpoints now draw from their own generous rate limit budget, configurable via the `DEPLOYMENT_RATE_LIMIT_*` environment variables, so runtime API traffic no longer competes with deployments for the same per-environment budget. ([#4565](#4565)) - Deleting or editing a secret environment variable is now fast and no longer slows down as a project accumulates variables. ([#4555](#4555)) - Speed up personal access token lookups by indexing them on their owner ([#4588](#4588)) - Switching project or organization in the sidebar now keeps you on the same page instead of sending you back to Tasks. Pages for a specific run, deploy or other single item open the matching list instead. ([#4585](#4585)) - Reduced database load when loading the dashboard by removing an unused organization member count that was being calculated on every page navigation. ([#4587](#4587)) - The environment variables page now loads a page at a time, keeping it fast for projects with a large number of variables. Search matches variable names across every page. ([#4597](#4597)) - Groundwork for an alternative database connection driver, gated behind configuration and disabled by default, so there is no change to default behavior. ([#4539](#4539)) - Deleting an alert channel is now fast and no longer slows down as a project builds up alert history. ([#4554](#4554)) - Reduced internal overhead on the API under high load. ([#4532](#4532)) - Out-of-date upgrade prompts no longer appear in the dashboard: the "V4" badges and the notices saying preview branches and the queues table need V4 have been removed. The side menu still warns you when a project is on v3, with updated wording and a link to the v4 upgrade guide. ([#4589](#4589)) - Make background worker registration cheaper for projects with many scheduled tasks by scoping declarative schedule reconciliation to the current environment and dropping redundant schedule lookups. ([#4577](#4577)) - Speed up setting and importing environment variables for projects with many variables. ([#4579](#4579)) - Loading the deployments list is now faster, especially when filtering by deployment status on projects with many deployments. ([#4591](#4591)) - Fixed the billing limits page timing out for organizations with many preview branches, especially while a spend limit was being enforced. The page now loads quickly, so you can raise or resolve your limit without delay. ([#4594](#4594)) - Fix the Concurrency page showing the plan's default concurrency for the dev environment instead of the environment's actual limit. ([#4596](#4596)) - Creating an organization sometimes left you back on the creation form even though the organization had already been created, so clicking Create again made a duplicate. Creating an organization now completes and takes you to your new organization. ([#4530](#4530)) - Ensure creating a project completes instead of returning to its creation form after a navigation error. ([#4584](#4584)) - Renaming a project now keeps you on the project settings page and tells you what happened, instead of silently moving you to the tasks page or clearing the form with no explanation. ([#4601](#4601)) - Fixed support threads showing no account details for some customers, so the team can see your plan, organizations and projects when you get in touch. ([#4575](#4575)) - In the light theme, the Format, Clear and Copy buttons on the query editor no longer blend into the query text behind them. ([#4592](#4592)) - The health report now says start latency is "unknown" when there is no data for it, instead of showing a healthy-looking 0ms ([#4544](#4544)) - Realtime streams written inside a chat session run now use the same backend as the session itself, and runs are no longer created against a backend that cannot serve them. ([#4564](#4564)) - The grouped "watch updates" notification now shows the total number of results waiting, instead of only the most recent batch's count. ([#4525](#4525)) <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## trigger.dev@4.5.11 ### Patch Changes - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - Allow `trigger deploy` to authenticate with an environment API key from `TRIGGER_ACCESS_TOKEN`. ([#4561](#4561)) - The dev environment onboarding now tracks real progress. After you run `init`, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent. ([#4563](#4563)) The `init` scaffold now imports from `@trigger.dev/sdk` instead of the deprecated `@trigger.dev/sdk/v3` subpath. - Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster. ([#4551](#4551)) - Updated dependencies: - `@trigger.dev/core@4.5.11` - `@trigger.dev/build@4.5.11` - `@trigger.dev/schema-to-json@4.5.11` ## @trigger.dev/core@4.5.11 ### Patch Changes - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - The current-worker API now reports each task's queue, so you can see which tasks write to a given queue. ([#4525](#4525)) ## @trigger.dev/python@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` - `@trigger.dev/sdk@4.5.11` - `@trigger.dev/build@4.5.11` ## @trigger.dev/react-hooks@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/redis-worker@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/rsc@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/schema-to-json@4.5.11 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.11` ## @trigger.dev/sdk@4.5.11 ### Patch Changes - Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days. ([#4418](#4418)) - Watch-mode chat streams now survive quiet windows and page reloads, and a reply cut off by a lost connection shows an error instead of appearing finished. Aborting a resumed subscription only closes your local stream — call `stopGeneration(chatId)` or pass `stopOnAbort: true` to stop the run. Also fixed a race where quickly restarting a stream could break stop and reconnect, and stopping a chat now hands it back to your other tabs instead of leaving them read-only. ([#4516](#4516)) - Updated dependencies: - `@trigger.dev/core@4.5.11` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

This comment was marked as resolved.

Sign in to view

kathiekiwi changed the title ~~Dashboard agent storybook gallery~~ feat(webapp): storybook gallery for the dashboard agent Aug 6, 2026

kathiekiwi marked this pull request as ready for review August 6, 2026 00:07

This comment was marked as resolved.

Sign in to view

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from bfe64cc to 1b6dfb1 Compare August 6, 2026 00:56

This comment was marked as resolved.

Sign in to view

kathiekiwi changed the base branch from feat/dashboard-agent-flows to feat/dashboard-agent-flows-watch August 7, 2026 12:51

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from 712396b to e110e90 Compare August 8, 2026 12:05

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from 662e92f to 02e1f60 Compare August 8, 2026 12:28

kathiekiwi force-pushed the feat/agent-storybook-gallery branch 2 times, most recently from ec08b16 to c43d49f Compare August 8, 2026 14:30

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from c0f0058 to e7432a8 Compare August 8, 2026 14:30

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from c43d49f to a71b7e0 Compare August 8, 2026 14:57

This comment was marked as resolved.

Sign in to view

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from a71b7e0 to 6587840 Compare August 8, 2026 16:09

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from 3a64fb0 to 4dc89f6 Compare August 8, 2026 17:49

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from 6587840 to fc9ce3b Compare August 8, 2026 17:51

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from 4dc89f6 to 5cddeb8 Compare August 8, 2026 18:08

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from fc9ce3b to 3a8fbcc Compare August 8, 2026 18:08

This comment was marked as resolved.

Sign in to view

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from 5cddeb8 to f1f8c97 Compare August 8, 2026 18:22

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from 3a8fbcc to 305742d Compare August 8, 2026 18:22

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from f1f8c97 to 6fbdbbc Compare August 9, 2026 00:01

kathiekiwi force-pushed the feat/agent-storybook-gallery branch from 305742d to de64d25 Compare August 9, 2026 00:01

kathiekiwi force-pushed the feat/dashboard-agent-flows-watch branch from 6fbdbbc to 59eaf24 Compare August 9, 2026 08:20

chore: merge main into feat/agent-storybook-gallery (post-squash of #…

fa20901

…4525)

This comment was marked as resolved.

Sign in to view

kathiekiwi added 2 commits August 12, 2026 08:04

fix(webapp): let a zero source line reach the URI validator instead o…

8cf6099

…f vanishing

chore: merge review-fix packet (demo line-0 guard)

53d1845

kathiekiwi changed the title ~~feat(webapp): storybook gallery for the dashboard agent~~ feat(webapp,sdk): dashboard agent plan enforcement, component gallery — and fixes Aug 12, 2026

This comment was marked as resolved.

Sign in to view

kathiekiwi added 2 commits August 12, 2026 08:49

docs(webapp): scope the watch-limits release note to what's enforced

0315232

This comment was marked as resolved.

Sign in to view

kathiekiwi added 2 commits August 12, 2026 09:16

docs(sdk): note that aborting a resumed subscription no longer stops …

1b3ba21

…the run

fix(webapp): honor a zero message allowance and prefer the server-res…

4b307dd

…olved limit over the client constant

This comment was marked as resolved.

Sign in to view

fix(webapp): don't tell paid plans their message allowance was the Fr…

a70c71e

…ee plan's

This comment was marked as resolved.

Sign in to view

kathiekiwi added 2 commits August 12, 2026 09:57

fix(webapp): disable suggestion chips when the message allowance is s…

6f03c5e

…pent

fix(webapp): disable the turn-error retry when the message allowance …

1a2e187

…is spent

This comment was marked as resolved.

Sign in to view

kathiekiwi added 6 commits August 12, 2026 10:18

fix(sdk): let a watch subscription re-establish after a reload when t…

c56e3e5

…he last turn completed

fix(webapp): release the upgrade panel when the message allowance fre…

f15ad15

…es up

fix(webapp): normalize dashboard-agent message text to well-formed UT…

01eeade

…F-16 at ingest

fix(dashboard-agent): truncate strings without splitting surrogate pairs

7b07c4f

chore: consolidate release notes

ac029e5

fix(dashboard-agent): normalize message JSON to well-formed UTF-16 at…

f03dfd9

… persist

kathiekiwi merged commit 480bede into main Aug 12, 2026
47 checks passed

kathiekiwi deleted the feat/agent-storybook-gallery branch August 12, 2026 11:59

github-actions Bot mentioned this pull request Aug 12, 2026

chore: release v4.5.11 #4557

Merged

Uh oh!

Uh oh!

Conversation

kathiekiwi commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Plan enforcement (TRI-12863)

Component gallery

And fixes

Screenshots

Uh oh!

changeset-bot Bot commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

coderabbitai Bot commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

❌ Failed checks (1 warning)

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

pkg-pr-new Bot commented Aug 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Aug 8, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

coderabbitai Bot commented Aug 12, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

kathiekiwi commented Aug 5, 2026 •

edited

Loading

changeset-bot Bot commented Aug 5, 2026 •

edited

Loading

coderabbitai Bot commented Aug 5, 2026 •

edited

Loading

pkg-pr-new Bot commented Aug 8, 2026 •

edited

Loading