$ ./about
Polyglot
PHP, Go, Java, Python to DevOps across AWS, GCP & Terraform.
World Traveler
Visited 50 countries so far.
Tech Speaker
Speaker at various conferences and meetups.
Open Source
1.2k+ GitHub followers, active contributor.
$ cat stack.txt
$ ./articles
$ ls articles
Timothy Part 20: Ears and Eyes, Voice Input and Image Attachments
Timothy can now hear and see: a microphone button transcribes speech entirely on-box through a self-hosted Whisper sidecar, and the composer accepts image attachments that are stored content-addressed on the brain and routed to a dedicated vision chain. Both are input-only for now; the model still cannot speak back or generate an image.
Timothy Part 19: A Chat That Survives Reloads and Races
The event log from parts 6 and 7 made turns durable on disk, but the live chat above it still lied under ordinary failure: a reload mid-answer looked stuck, a dead turn looked like a stuck spinner, and parallel tool calls could stack duplicate prompts. This post covers the milestone that made the live experience as honest as the log underneath it: reattach across reloads, one turn per session, persisted permission asks, and turns that say plainly when they produced nothing.
Timothy Part 18: Sensitive Sessions Stay Home
Some content should never reach a cloud provider, no matter which model is smartest. I added a sensitive-tool route that pins a session to a local model the moment it touches something like Gmail, made the pin sticky across every later turn and side-call, and moved local inference off a containerized Ollama onto a native host runner so it's actually fast enough to use.
Timothy Part 17: Mission Schedules, Notifications, and the Canary
A mission that never gets scheduled again is barely different from a chat message. This post covers the cron scheduler that fires mission templates, transition notifications pushed over SSE, per-mission spend read honestly off the cost ledger, an opt-in escalation route for stuck missions, and the golden-mission canary that gates every change to the harness.
Timothy Part 16: Mission Verification, Review, and the Sandbox
A mission that reports itself done is not the same thing as a mission that is done. This part covers the harness-owned verification that never trusts a model's word for it, an antagonistic reviewer that has to be talked out of rejecting, and the move to run every model-authored command in a disposable sandbox instead of the brain's own process.
# ---
>_ ls articles --all