Virtual Me blog
Welcome to Virtual Me
Virtual Me exists because useful background computing should be inspectable, private, and owned by the person asking for the work.
What runs locally
One container brings together a Go controller, a bundled local model, a real Chromium desktop, a reliable queue, and persistent state. The browser is not a remote cloud session. Its profile, screenshots, project files, and history stay in the data directory on hardware you control.
Where to begin
Begin with the 5-minute guide. It starts with the CLI, runs one concrete browser task, and turns another task into a recurring Project. The Desktop shows the work as it happens; Jobs and Data make its result inspectable.
What belongs here
This blog will explain shipped behavior, design constraints, operating lessons, and concrete changes. Claims will stay attached to code and measurements rather than imagined benchmarks.