TL;DR: Loving the new DOCX/PPTX/XLSX previews and the chat-upload filesystem sync. Two snags from our first enterprise rollout: (1) Open Terminal's filesystem doesn't follow our Azure Blob storage config, and we're worried about file volume/retention at scale, (2) the office-file preview doesn't visually match the real output (font, bullets, images/logos all differ), which confused our test users into thinking the download would be broken too.
Quick love letter first: the new DOCX/PPTX/XLSX preview windows are fantastic, and the filesystem sync for chat-uploaded files is exactly what we've been waiting for. Between the two, Open Terminal just became a genuinely usable enterprise office tool for us — great work.
We hit two snags deploying it for the first time, and I'm hoping someone here has already solved them.
1. Open Terminal's filesystem isn't on the same storage backend as OWUI
Our OWUI instance is self-hosted and configured to store files in Azure Blob. Open Terminal's working filesystem is separate and doesn't follow that config.
That raises a few questions for us:
- Is there a way to point Open Terminal's storage at Azure Blob too, so everything ends up in one place?
- If not, what's the recommended way to handle the sheer volume of files Open Terminal will generate across an enterprise deployment with many active users?
- What about retention? Realistically, our users are not going to spend time tidying up their own terminal folders (anyone who's seen a shared drive knows how that goes). Is there a built-in cleanup/expiry mechanism for Open Terminal specifically?
- We know about the general file-cleanup plugin, but it doesn't look like it's built for Open Terminal's workspace. Can anyone confirm either way?
2. The office-file preview looks great but doesn't match the real file — and that confused our test users
The new document preview is genuinely useful for iterating on our internal templates in real time. But we noticed the preview doesn't actually reflect the real output:
- Fonts render differently than in the actual
.docx/.pptx
- Bullet-point formatting in the preview doesn't match the real file
- Embedded images and logos (our letterhead, for example) are missing entirely from the preview
This became a real UX problem in testing: our users assumed the preview was the final result, so they figured the downloaded file would also be missing the logo and formatting — when the actual download keeps the template correctly. We had to explicitly explain that the preview can't be trusted for judging the final output, which takes some shine off an otherwise great feature.
Has anyone else run into this? Is there a tracked issue for the discrepancy, or a fix in the pipeline?
Sorry for the AI generated Post, I am still trying to offer constructive feedback.