wardethan2000-eng keeps chat working material out of the matter file

The fork lets a team add a file to a project chat as context without automatically making it part of the formal matter record.

chat-uiworkflow

That is a useful distinction for legal teams: a lawyer can share working material with an AI-assisted conversation while keeping the matter file reserved for documents that should actually be retained there.

The change also makes file dropping more dependable across browsers, including for documents, spreadsheets and workflow uploads. Files attached to the chat are included when the system builds context for that conversation, so they can inform the response without being filed into the matter.

There is one caveat worth checking on GitHub: the change includes earlier edits alongside the attachment work. Before adopting it, a firm should be clear on who can access chat-only files, how long they are stored, and when they are removed.

So what Legal-ops leads and product teams should care if they want faster AI-assisted discussion without quietly turning every reference document into a matter record.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from wardethan2000-eng/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`464b7aa0`	feat: attach files to a matter chat without filing them in the matter	Ethan Ward	2026-08-19	↗ GitHub
commit body Matter chats had no attach button, so the only way to give the assistant a file was to add it to the matter Documents list first. Now the button is there, and a file dropped on the chat side stays with that chat - drop it on the file list or the Documents tab to file it in the matter. The drop panel is limited to the chat side so it no longer covers the file list, and the backend merges chat-only attachments into a matter chat context, which previously saw matter documents only. Note: backend/src/lib/chat/contextBuilders.ts and routes/projectChat.ts also carry earlier uncommitted edits from another session on this shared tree; they are included here because they cannot be separated by path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PoCRDAPyEq4wwBVFFbDzck
`598d1c6a`	fix: accept dragged files the browser labels a different way	Ethan Ward	2026-08-19	↗ GitHub
commit body A drag was only recognised when the browser labelled it exactly "Files". Some Linux file managers, and some apps, hand a dragged file over as "text/uri-list" or "application/x-moz-file" instead, and those drags were ignored outright - no drop panel, no upload, nothing, which reads as drag-and-drop simply not working. Ignoring the drag also let the browser take it instead and leave the app to open the file, losing the page. All five places that accept dropped files now share one test, and a drag that carries only a link says so instead of appearing to do nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PoCRDAPyEq4wwBVFFbDzck

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1250.md from inside the repo you want the changes in.

⬇ Download capture-thread-1250.md