I build Windows desktop tools and developer utilities, with a focus on local workflows, understandable changes, and useful diagnostics.
My projects range from desktop applications to focused C++ library revivals. I care about showing what works today, documenting the limits, and making the next step easy to find.
| Project | What you can explore | Status |
|---|---|---|
| AppTrail | Capture application or project folders, compare snapshots, inspect source/config diffs, and export offline HTML reports. Python desktop app with a Windows x64 download. | Released; Windows 11 x64 tested |
| win-pipe revival | A single-header C++17 local IPC library with bounded messages, cancellable pipe I/O, regression tests, and a real multi-process logging example. Derived from goodtrailer/win-pipe; ISC licensed. | Released 0.2.0; desktop x86/x64 scope |
| Meridian | An offline-first Windows 11 file manager with dual-pane workspaces, Folder DNA summaries, and reviewed batch-copy workflows. Built with C#, .NET, and WinUI 3. | Early development preview |
- SetupSweep — a Rust Windows toolkit for installation evidence, reviewed system changes, and developer-environment diagnostics. Local milestones can be ahead of published source and downloads; see its README for scope.
- CursorCabinet — a native C++ cursor browser with previews, per-user application, and recovery of the preceding scheme. Native releases are previews.
- Keep core workflows local and make changes explicit.
- Use existing stacks where they fit: Rust, C++, C#, and Python.
- Preserve upstream credit and licenses when reviving useful projects.
- Describe validation and compatibility honestly, including unfinished release gates.
Start with AppTrail downloads, the win-pipe 0.2.0 release, or Meridian's preview guide.
For bugs, ideas, or contributions, use the relevant project's issues and contribution guidance. A clear reproduction, Windows version, and build details help me investigate.
Desktop tools, native libraries and revivals are indexed with their different maturity levels. Start with the DLL consumer index, fork provenance, or development resource library.


