gercyc gives workflows their own filing cabinet

Workflows in this fork can now carry their own persistent attached files, instead of treating documents as one-off inputs.

workflowknowledge-management

gercyc has built a net-new feature that lets each workflow hold onto a set of attached assets that stick around - a dedicated panel on the workflow page, a full set of controls to add and manage them, and storage behind the scenes. Think of it as giving every matter or process its own folder of reference documents that travels with it, rather than re-uploading the same files every time.

The work is wired into this fork's own database setup and ships with both English and Brazilian-Portuguese labels, so it's tied fairly tightly to gercyc's particular build. Anyone eyeing it for their own fork should look at it alongside the broader self-hosting changes, not as a standalone drop-in.

So what Worth a look for anyone running document-heavy legal workflows who's tired of treating files as disposable inputs.

View this fork on GitHub →

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

Commits in this thread

1 commit from gercyc/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
043ac5f0 Add workflow assets, fix chat with documents Gercy Campos 2026-05-25 ↗ GitHub

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-607.md from inside the repo you want the changes in.

⬇ Download capture-thread-607.md