CS student · indie developer
Currently building VeriSilo, a Windows-first, open-source browser environment isolation and privacy-auditing project for Chrome and Edge.
Selected work
Each project starts with a concrete problem, keeps its boundary visible, and leaves behind something another person can inspect.
01 · Current focus
Every Silo launches Chrome or Edge with its own managed data directory. Cookies, storage, cache, service workers, permissions, and history stay inside that environment rather than the default profile.
VeriSilo does not claim device impersonation, fraud bypass, TLS or QUIC modification, hardware isolation, or undetectability.
Available · v0.2.0 · Local-first nutrition feedback workbench
Connects meal photos, daily state, trends, and corrections into a feedback history that can improve the next decision.
The application keeps facts, schemas, and correction history local; it does not call an external model API itself.
Stabilizing · v0.5.0 candidate · Local-first AI agent activity radar
Brings running, waiting, permission-request, completed, and failed states from parallel Claude Code, Codex, and other tools into read-only Desktop, Companion, Dashboard, and CLI views.
Linux x64 has completed hands-on verification; Windows and macOS remain pending. Crewlight stores no prompts, transcripts, tool I/O, or complete platform payloads.
Teaching · local experimentation · Repeatable local Hadoop laboratory
Connects environment setup, service observation, MapReduce, and three-node failure and recovery into a guided learning path.
A lifecycle CLI plus doctor, status, WordCount, safe reset, and redacted diagnostics keep the lab reproducible without presenting it as a production platform.
How I build
I am most interested in software that stays understandable after the first demo—where data lives, what changed, and what the tool refuses to promise.
Keep useful work and private state on the user’s machine by default.
Expose evidence, history, and capability state instead of hiding judgment behind a score.
Say what the software does not solve before marketing fills in the blank.
Turn setup and recovery into paths another person can repeat and verify.
Prefer deliberate export, correction, and deletion over silent synchronization.
Selected writing
Technical guides, model criticism, and a few rules I use to keep tools from deciding the work for me.
Beyond work
Writing, guitar, games, relationships, and questions that have not turned into software live in a slower, more personal space.
Enter Qiu's RoomContact
Open to technical conversations, project feedback, and focused software help.