Feature: User Attachments (Issue #26)

[Yash3561]

Summary

Added support for users to attach files to their messages. The files are uploaded to the backend and their text content is injected into the prompt sent to the agent.

Implementation Details

Backend

• Added POST /files/upload endpoint.
• Introduced StorageProvider abstract base class to handle file storage.
  • Implemented LocalStorageProvider for saving files to the local disk (uploads/ directory).
  • Used run_in_threadpool for file I/O to avoid blocking the async event loop.
• Updated MessagesUseCase to retrieve file content and append it to the message text.

Frontend

• Added file selection button to the chat input component.
• Implemented useUploadFile hook to handle the upload request.
• Displays uploaded files as chips in the UI.

Notes

• The storage implementation is modular. For production, we can swap LocalStorageProvider with an S3 implementation without changing the core logic.
• Validation is currently set to a 10MB limit and restricts file types to common text/image formats.

Verification

• Added unit tests for the upload endpoint (scripts/test_upload_isolated.py was used for verification).
• Verified the UI components build and render correctly via npm run dev.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​radix-ui/​react-label@​2.1.7 ⏵ 2.1.8
	npm/​@​radix-ui/​react-separator@​1.1.7 ⏵ 1.1.8
	npm/​@​vitest/​coverage-v8@​4.0.6 ⏵ 4.0.18	+1
	npm/​@​radix-ui/​react-slot@​1.2.4
	npm/​@​types/​uuid@​10.0.0
	npm/​@​types/​ws@​8.18.1
	npm/​@​types/​react-dom@​19.1.6 ⏵ 19.2.3			+1
	npm/​agentex@​0.1.0-alpha.9 ⏵ 0.1.0-alpha.14	-5		+1	+4
	npm/​vitest@​4.0.6 ⏵ 4.0.18	-1		+1
	npm/​@​types/​react@​19.1.8 ⏵ 19.2.13
	npm/​@​codemirror/​state@​6.5.2 ⏵ 6.5.4			+1
	npm/​@​types/​node@​20.19.9 ⏵ 20.19.32	+1		+1
	npm/​@​vitest/​ui@​4.0.6 ⏵ 4.0.18			+1	+2
	npm/​@​eslint/​eslintrc@​3.3.1 ⏵ 3.3.3
	npm/​tailwindcss@​4.1.11 ⏵ 4.1.18	+1		-1
	npm/​react@​19.1.1 ⏵ 19.2.4	+1		+1
	npm/​@​codemirror/​autocomplete@​6.19.0 ⏵ 6.20.0	+1		+1
	npm/​@​codemirror/​view@​6.38.6 ⏵ 6.39.12			+1
	npm/​@​tanstack/​react-query@​5.90.3 ⏵ 5.90.20			+1	-1
	npm/​happy-dom@​20.0.10 ⏵ 20.5.0			+1	+3
	npm/​tw-animate-css@​1.3.6 ⏵ 1.4.0
	npm/​@​hookform/​resolvers@​5.2.1 ⏵ 5.2.2
	npm/​@​uiw/​react-codemirror@​4.25.2 ⏵ 4.25.4	+1			-4
	npm/​prettier@​3.6.2 ⏵ 3.8.1	-3		+1
	npm/​prettier-plugin-tailwindcss@​0.7.1 ⏵ 0.7.2				-3
	npm/​@​testing-library/​react@​16.3.0 ⏵ 16.3.2
	npm/​react-dom@​19.1.1 ⏵ 19.2.4	+1		+1
	npm/​eslint-plugin-prettier@​5.5.4 ⏵ 5.5.5
	npm/​react-hook-form@​7.62.0 ⏵ 7.71.1			+1
	npm/​@​vitejs/​plugin-react@​5.1.0 ⏵ 5.1.3	+1			+4
	npm/​jsdom@​27.1.0 ⏵ 27.4.0			+1	+2
	npm/​framer-motion@​12.23.24 ⏵ 12.33.0	+2			+1
See 1 more rows in the dashboard

View full report

[Yash3561]

Hey @MichaelSun48, since you've been leading the core framework development, I'd love your eyes on the StorageProvider implementation here. I wanted to ensure the abstraction was clean enough to support S3/GCP adapters for the Enterprise version without breaking the existing local dev flow.