tritium-legal's online editing bid never makes it over the line

The fork points to a useful idea: let a browser open the original file, not just a pre-rendered version.

integrationworkflow

The proposed change would have created a direct route for file contents to reach the front end. That matters because online editing needs the original document data, whereas a rendered preview is mainly useful for reading.

The work was aimed at an integration that would use those new access points, and the relevant area was reportedly checked with build or test tooling. But the pull request was closed without being merged, so this is a signpost to an unfinished direction rather than a capability users can rely on today.

So what Legal product teams considering browser-based document editing may find the design direction worth examining on GitHub, but should treat it as a proposal, not shipped functionality.

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 tritium-legal/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
a0dcc4e0 add raw File bytes streaming to API Drew Miller 2026-08-07 ↗ 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-1382.md from inside the repo you want the changes in.

⬇ Download capture-thread-1382.md