Markdown files
Open a Markdown file and switch between the rendered page and its markup with the Preview / Source toggle beside the file name.
ShadRox v0.0.9 — durable runs, evidence-backed checks, free + BYOK. Release notes →
Preview support
ShadRox serves static sites and detected web projects locally, asks before it installs or launches anything, and checks the rendered frame so you know the preview actually worked. Here is exactly what that covers.
Preview support
ShadRox can serve static sites and launch detected Node-based web projects with supported package scripts. It detects Python, Go, PHP, Java, and .NET entry points — the runtime itself must be installed on your machine. Opening a project workspace automatically starts its detected preview script and may offer to install missing dependencies.
Currently supported
Good to know
Under the hood
Five steps between opening a folder and seeing the page. Two of them are yours: approving what runs, and reading the result.
Every managed run action — dependency install or detected script — waits for your approval before it touches the project.
ShadRox reads the folder you opened and works out what it is: a static site, a Node web project with a supported package script, or a detected backend entry point.
Installing missing dependencies and launching a detected script are managed run actions. Both ask for your approval first — nothing installs or starts on its own.
The project is served locally and rendered in the in-app preview panel, beside the editor, the chat and the terminal it came from.
A bounded check grades the rendered frame, so a blank or broken preview is reported instead of quietly counting as a success.
Dev servers left behind by an earlier session are cleaned up on the next start, so old processes do not pile up in the background.
Coverage
Detection happens when you open a folder. What actually runs depends on the project — and on what is installed on your machine.
Open a Markdown file and switch between the rendered page and its markup with the Preview / Source toggle beside the file name.
Plain HTML, CSS and JavaScript folders are served locally and shown in the preview panel — no build step and no configuration.
Detected frameworks and bundlers running their supported package scripts, including nested projects you pick from a list.
Entry points for these backends are detected in your workspace. How far a preview gets depends on the project and its configuration.
The runtime must be installed on your machine.
The Preview / Source switch sits right beside the file name. Read the rendered page, flip to the markup to fix a heading or a link, and flip back — without opening another tool.
Try the toggle
A desktop workspace for the projects on your computer.
shadrox.cyou
An illustration of the toggle beside the file name — same file, two views.
Good to know
Preview is a convenience, not a universal runtime. These are the edges you will actually meet, plus the two behaviours worth knowing about.
Detection covers the setups listed above. A project with an unusual configuration may not be detected, or may not run the way you expect.
External sites that refuse to be embedded will not render inside the preview panel, however healthy they are in a browser.
On pages ShadRox serves, click an element in the preview to jump straight to its source line in the editor.
Managed run actions always ask before anything installs or launches. You stay the one who decides what runs.
Get ShadRox
The quickest way to find out whether your setup is covered is to open it. ShadRox detects what it can run and asks before it runs anything.
v0.0.9 · Windows 10 or 11 (64-bit) · the installer is unsigned, so Windows may warn — choose More → Run anyway.