Skip to content

Private build

Wiregent

A governed file agent for Windows. It maps where the space goes across C:, WSL and Docker, proposes what to clean, and deletes nothing until you tick it.

Role
Creator · Solo build with a seated agent team
Period
Oct 2026 – present
Stack
Rust · Tokio · Tauri 2 · React 19 · and 6 more
Place
Remote · Windows desktop

3 placesC:, WSL and Docker in one scan

01 / 02

What I built

  • A Rust core with modules in any language. The host speaks JSON lines over stdio, so the cleanup checks run as PowerShell modules behind one contract.
  • A read-only drive map. Where the space goes, the largest files and their kinds, before anything is touched.
  • A consent-gated secrets scan. Values stay masked, and leak risks in git and cloud folders show only after consent.
  • Drives that come and go. Eject, watchers, speed tests and verified moves: copy, compare, then remove.
  • An advisor that proposes. One click uses a signed-in Claude Code; a local OpenAI-compatible server answers with the same subscription. Each AI task is its own specialist, and none of them can write.
  • A daily view. One read-only look across storage, secrets, connections, rules and this PC, with every change ticked by a person and recorded.
  • A desktop app. Tauri 2 around a React UI, with a demo backend that shows every screen without touching a disk.
02 / 02

What it taught me

A tool that deletes files earns trust through its invariants: local-first by default, content read only with consent, moves verified, the AI proposing and a person deciding, and every action recorded.

It is also the first project I ran from day one with a seated agent team, where merges pass a Bar Raiser review and the riskier ones a Security review too.

Decisions and why

  1. The AI proposes; a person deletes.

    WhyEvery change to data waits for a tick and a press of Clean. The tool works fully with the advisor turned off.

  2. Modules behind a contract, not a monolith.

    WhyCleanup checks live in PowerShell where Windows knowledge lives, and the Rust core hosts them over stdio.

Technical highlights

  • 01

    Rust workspace: core host, AI providers, drive map, secrets scan, drive watchers, audit, a System hub, CLI and a local AI server.

  • 02

    Module contract over JSON lines on stdio, so a check can be written in any language.

  • 03

    Tauri 2 desktop shell with a React 19 UI and a browser demo backend.

Outcomes

By the numbers.

Rust + Tauri 2
native core, React UI
Opt-in AI
works fully without it
Recent activity

The changelog.

October 2026
2w
shipped:Wiregent — behind-the-scenes fixes and upkeep15 commits · 2w
Private
3w
released:Wiregent — first slice - read open tabs, back them up, find exact duplicates194 commits · 3w
Private
3w
shipped:Wiregent — slim the project's own seat descriptions
Private
↗ Next case study

BoundStretch

BoundStretch gives every workspace a cockpit: tasks, time, Claude usage and cost, findings with traceable IDs, topic microsites and an Ask panel. An indexer reads markdown, YAML, git history and Claude Code session logs into one snapshot, and the same React UI runs on a local server or as a published page I can open from my phone. The workspace repo stays the source of truth; edits wait in an outbox until a sync writes them back into the markdown.