Web App for viewing changes made to custom Filament & Process profiles
When I save changes to profiles or filaments I cannot return to the prevoius value or ever again see what it was. That’s annoying.
If you are very non-tecnical, skip straight to ‘Solution for very non-tecnical users‘ below…
I’ve been working on a small local tool called Bambu browser that reads Bambu Studio’s on-disk JSON / preset data (machines, processes, filaments, inheritance between profiles) and shows it in a clean web UI. Nothing leaves your machine: you run everything yourself on localhost.
I think it could be useful for people who live in presets, inheritance chains, and “why does this profile look like that?”. This may be aimed at technical users. You need Node.js, two terminal processes (a tiny local API + the Next.js dev server), git (source control) and ideally you’re comfortable cloning a repo and reading a README.
Why a local API? Browsers can’t reliably read folders like macOS ~/Library/Application Support/BambuStudio, and the File System Access picker has its own limits. A small read-only Node HTTP server reads Studio’s data directory and the UI talks to it over 127.0.0.1 — that’s the dependable path today.
Clone the repo here: GitHub - oyvindo/bambu-browser: Track custom filaments and proceses. Compare base · GitHub
Reade the readme file.
cd bambu-browser
npm install
terminal 1: npm run api
terminal 2: npm run dev
open localhost:3000
Solution for very non-tecnical users
I have also published the app on Vercel: https://bambu-browser.vercel.app/.
Connect the folder C:\Users\\AppData\Roaming\BambuStudio
For mac users you still have to clone the project from github to run the local api to access your private folders and may as well run the app localy.
(as a mac-workarounds you may copy ‘/Users//Library/Application Support/BambuStudio’ to a location where chrome has access. Then the vercel app is all you need. Just point to that folder.)
Feel free to make suggestions.
Disclaimer:
Although I am a developer, this whole app is created by Cursor, by my input. I saw this as an oportunity to really test Cursors abilities. In total I have spent 20 hours.
My contribution has been research, create exact prompts, testing and verification. This is the reason why some props may be missing(although they should all be there). But for my own needs, to see adjustments comapred to a preset, I am satisfied.
Disclaimer 2:
I have not yet dug into dual process(whatever that is… 
)
I have intentionally not translated names of settings og groups. It look strange, atleast in norwegian.
- øyvind -
Example process:
Example Filament:
…wonder where this ends