20e66adae3* studio/chat: persist Anthropic container id on first turn of new thread The container_ready SSE handler updated thread record via db.threads.update, which silently affects 0 rows when the Dexie row hasn't been inserted yet. On the first turn of a brand-new thread the SSE event can arrive before assistant-ui persists the row, so the new container id was dropped, and the next turn re-read null and let Anthropic auto-create a fresh container instead of reusing the one from turn 1. Call ensureThreadRecord first so the row exists before the update lands. * studio/chat: temp diag log for container persistence races * studio/chat: drop temp diag logging * studio/chat: retry container persist instead of forcing thread row Drop ensureThreadRecord + circular runtime-provider import. Retry the update for up to 500ms so assistant-ui's DexieAdapter.initialize wins the race and creates the thread row with the right modelType (base / lora / model1 / model2), then our update lands on a subsequent attempt. Addresses gemini-code-assist review on #5526. |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .gitignore | ||
| .gitkeep | ||
| .npmrc | ||
| biome.json | ||
| components.json | ||
| data-designer.openapi (1).yaml | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||