u/andre-br

I used CCleaner for years and stopped. Not because it broke, but because it kept growing. Driver updater, health check, software updater, popups. I only ever wanted one thing out of it: delete the temp junk.

So I wrote a .bat file. It worked fine, but every time I wanted to change something I had to read through the whole thing again. Eventually I put a UI on top of it and moved all the paths into a plain silt.ini sitting next to the exe. Every folder it cleans is a line in that file. Don't like one? Delete the line. I missed one? Add it.

What it does:

scans first, shows how much is sitting in each location, then you choose what goes

tells you the exact folders it touches, nothing hidden behind a category name

never writes to the registry, never touches Windows system files

That last part is the whole point for me. Registry cleaning is where these tools historically wrecked people's installs and I never saw a real benefit from it.

Some questions I'd ask myself:

Why use this instead of Disk Cleanup / Storage Sense / BleachBit?

Maybe don't. Disk Cleanup is built in and it's fine. BleachBit is open source and does more. I'm not trying to compete with anyone here. I built this for myself and figured someone else might want the same small thing.

Is it free?

Yes. No trial, no pro tier, no account.

Then why isn't it open source?

The UI framework it's built on belongs to my company and I use it in my commercial products, so I can't publish the source. The cleaning logic isn't the secret part anyway, it's all sitting in silt.ini and you can read every path before you run anything.

Windows only.

Link: https://silt.devslim.com

If there's a folder that should be there and isn't, or one that shouldn't be there at all, tell me.

I've spent most of my career writing Windows desktop software in Delphi, and the UI layer has always been the part I fight with. So I went the other way: let Edge WebView2 render the interface, keep every line of logic in Pascal, and wrap the whole thing in a component.

It's called Astraeus, it's still in development, and I'd rather have it torn apart here than find the holes after release.

How it actually looks

Drop a TEdgeBrowser (Align := alClient) and a TAstraeusWindow on the form, put your index.html in web\, F9. The bridge is typed on both ends:

Astraeus1.Register('todos.add',
  procedure(const Req: IAstraeusRequest; const Res: IAstraeusResponse)
  begin
    Res.Ok(TTodoRepo.Add(Req.AsString('title')));
  end);

const id = await astraeus.invoke('todos.add', { title: 'Buy coffee' });

Component, not runtime — no singleton, no global state, no initialization call. Two windows in one process each carry their own bridge. Release builds pack the web\ folder into the executable, so distribution is MyApp.exe plus WebView2Loader.dll.

Proof it isn't a toy

Two products already built exactly like this, HTML for the entire UI and Delphi only on the calls, the same shape as Tauri:

• https://strata.devslim.com — disk space analyzer that reads the NTFS MFT directly and draws a treemap in the webview
• https://recovera.devslim.com — file recovery for Windows

The parts that took real work

Frameless windows are the tax you pay: custom title bar, rounded corners, Snap, maximize without flicker, browser shortcuts disabled. Then the startup gap — WebView2 needs a second or two, and the window sits there grey until the page paints, so there's a background color property and an option to hold the window until the first frame (or until the app says it's ready). Then transparency via per-pixel alpha so Windows 10 gets it too, not just Mica on 11. And an interop layer with my own ICoreWebView2 declarations, tested against the real runtime, because every RTL version exposes a different subset.

10.4 Sydney or later, Win32 and Win64, Evergreen runtime. CI builds both packages for both platforms and runs lint checks and test programs before anything gets committed.

Honest gaps: 10.4 has never run this code, and the design-time package has no test coverage — the wizard and property editors are verified by me using them, nothing more.

So: what am I not seeing?

Specifically — does requiring the WebView2 runtime cost you real users in practice? Is the memory footprint of an embedded browser something your customers would notice? And for anyone who tried this and went back to VCL or FMX, what made you turn around?

We built a disk space analyzer for Windows and it's free to use, including commercially.

What it does:

Reads the NTFS master file table directly, so a full drive scan finishes in seconds

Renders the whole volume as a treemap, click any block to drill into that folder

Breakdown by file type, so you can see how much space each extension takes across the drive

Sidebar listing every volume on the machine

Detail panel with full path, size and dates for whatever is selected

Dark theme

How it handles sizes: every byte is attributed to exactly one file, so the treemap totals add up to the volume's used space instead of double counting.

Requirements and limits:

Windows only

NTFS only, since the MFT is an NTFS structure

Needs admin rights for raw volume access

Signed binary

Free, no account, no paid tier

https://strata.devslim.com

Solo dev here. I've been living in the Start menu search for years and hating it, so I finally built the replacement.

Findly: press Alt+Space anywhere, type two letters, Enter. It merges installed programs, Store apps, system tools and Settings pages into one ranked list and reorders based on what you actually launch.

Constraints I set for myself: it had to be small (ended up around 5MB), install without admin rights, keep the index fully local, and never require the mouse.

https://findly.devslim.com

It's free. Mostly looking for feedback on ranking quality, that's the part that's hardest to get right.

I just shipped v1.0 of Terminalia, a native terminal workspace for Windows.

Built with Tauri v2, Vue 3, and xterm.js, and written entirely inside its own window — the agents in the screenshots are the ones that wrote the code.

What it does

• Panes, tabs, and workspaces — Split a tab as much as you want, and your layout and sessions come back exactly how you left them.
• Native WSL support — WSL distros open as real terminals, with no path hacks.
• Built-in project explorer — A project file tree and a lightweight editor sit right next to your AI agent.
• Detached terminal windows — Pop any pane into its own native window and re-attach it whenever you want.
• Native screenshot workflow — Capture any screen region, annotate it with arrows, boxes, and numbered markers, then paste it directly into an AI conversation. Saying "fix 1, then 2" is much easier than describing where a button is.
• Live AI quota tracking — See your Claude Code and Codex usage in real time, so you know whether there's enough quota left before starting a large task.

The installer is only 8.7 MB, which is one of the main reasons I chose Tauri.

Platform Support

• Windows (available now)
• Linux (coming soon)
• macOS (coming soon)

Website

https://terminalia.devslim.com