Sonarly Claude Code
c7a979fd3b
https://sonarly.com/issue/36680?type=bug When a user uploads a file and sends a message while an AI stream is active, the file IDs are not passed to the queueMessage mutation, causing files to be lost from the queued message. Fix: Fixed two related bugs causing uploaded files to disappear from AI chat messages: **Primary fix (useAgentChat.ts):** When sending a message fails, the error handler now restores the uploaded files that were cleared optimistically. Before this fix: 1. User uploads file → stored in `agentChatUploadedFiles` 2. User sends message → files cleared from state (line 137) 3. Send fails (network error, validation error, etc.) → error handler restores text but NOT files 4. User sees files permanently lost The fix captures a snapshot of uploaded files before clearing (line 135), then restores them in the error handler (line 190). This matches the team's pattern of restoring content on error (already done for text on lines 182-188). **Secondary fixes (useAiChatFileUpload.ts):** Converted two state updates from direct array operations to functional updates to prevent stale closure bugs: - Line 40-42: When a file upload completes, remove it from "uploading" state using `setAgentChatSelectedFiles((prev) => prev.filter(...))` instead of filtering the captured closure value - Line 75: When adding successful uploads, use `setAgentChatUploadedFiles((prev) => [...prev, ...successfulUploads])` instead of spreading the captured closure value These prevent race conditions when multiple files are uploaded concurrently or when state is modified between render and callback execution. The functional update pattern is already used elsewhere in the codebase (e.g., `setAgentChatDraftsByThreadId` in useAgentChat.ts lines 183-188). All changes follow the team's established patterns: functional state updates, minimal scope, defensive error handling.
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
TypeScript
Nx
NestJS, with BullMQ, 
PostgreSQL, 
Redis
React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
Star the repo · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute