assistant-ui Update

Always verifies against npm ground truth and GitHub commits.

References

./references/ai-sdk-v6.md -- AI SDK v4/v5 → v6 migration (complete guide)
./references/assistant-ui.md -- assistant-ui version migrations
./references/breaking-changes.md -- Quick reference table

Phase 1: Detect Versions

Get Ground Truth

npm ls @assistant-ui/react @assistant-ui/react-ai-sdk ai @ai-sdk/react 2>/dev/null

npm view @assistant-ui/react version
npm view @assistant-ui/react-ai-sdk version
npm view ai version

Version Analysis

Current latest: @assistant-ui/react 0.14.x, @assistant-ui/react-ai-sdk 1.3.x, assistant-stream 0.3.x.

Package	Check For
`ai`	< 6.0.0 → needs AI SDK v6 migration
`@assistant-ui/react`	< 0.14.0 → primitives `components` prop replaced by children render functions; deprecated hooks/aliases removed
`@assistant-ui/react`	< 0.13.0 → `ThreadPrimitive.ViewportSlack` removed (top-anchor changes)
`@assistant-ui/react`	< 0.12.0 → unified state API (`useAui`/`useAuiState`/`useAuiEvent`/`AuiIf`)
`@assistant-ui/react`	< 0.11.0 → runtime rearchitecture
`@assistant-ui/react`	< 0.10.0 → ESM only
`@assistant-ui/react`	< 0.8.0 → UI split (shadcn registry)
`@assistant-ui/react-ai-sdk`	< 1.0.0 → needs AI SDK v6 first

Phase 2: Route to Migration

AI SDK < 6.0.0?
├─ Yes → See ./references/ai-sdk-v6.md
└─ No
   └─ assistant-ui outdated?
      ├─ Yes → See ./references/assistant-ui.md
      └─ No → Already up to date

Migration Order

AI SDK first (if < 6.0.0) - Required for @assistant-ui/react-ai-sdk >= 1.0
assistant-ui second - Apply breaking changes for version jump
Verify - Type check, build, test

Phase 3: Execute

Update Packages

pnpm add @assistant-ui/react@latest @assistant-ui/react-ai-sdk@latest ai@latest @ai-sdk/react@latest

npm install @assistant-ui/react@latest @assistant-ui/react-ai-sdk@latest ai@latest @ai-sdk/react@latest

Apply Migrations

Based on version jump, apply relevant migrations from references.

Verify

npx tsc --noEmit
pnpm build

Troubleshooting

"Peer dependency conflict"

Update all packages together
Check version compatibility in ./references/breaking-changes.md

Type errors after upgrade

Consult breaking changes reference
Check specific migration guide

Runtime errors

Verify API patterns match new version
Check for renamed/moved APIs

update