Vibe Terminal
My dev team fits in my pocket.
I built my own platform for building. AI coding agents run on a server around the clock. I direct them from my phone, and they ping me when they need a decision.
This site started as a phone screenshot of a domain registrar, uploaded into a session. The first version was live on my tailnet that evening.
Toolbox · now
Claude needs a decision in bumpsync
Apply the RLS migration to production?
A replay of a typical session.
What it does
Always on
Agents run on a server that never sleeps. Sessions keep going when I close the app, and I pick them up on any device.
Pushes when it matters
My phone buzzes when an agent is blocked or finishes a long job. The notification opens that exact session.
A QA API
Agents test their own work in a real browser: click through the app, fill forms, take screenshots, read console errors.
Skills for the hard parts
Reusable playbooks for code review, security audits, analytics deep-dives and design passes. Same standard every time.
QA that agents run themselves
A small HTTP API in front of headless Chromium. Any agent in any session can drive it, so “it works” comes with a screenshot and a clean console.
# launch, open the app, act like a user
curl -X POST $VT/api/browser/launch -d '{"session":"bumpsync"}'
curl -X POST $VT/api/browser/navigate -d '{"session":"bumpsync","url":"…/invite"}'
curl -X POST $VT/api/browser/fill -d '{"selector":"#email", …}'
curl -X POST $VT/api/browser/screenshot -d '{"fullPage":true}'
# anything broken?
curl "$VT/api/browser/logs/bumpsync?type=error"The loop
Spot it
A user complaint, a funnel drop or my own frustration.
Write it down
Plan and decision log go in the repo first.
Build
Agents write the code. I review what it does.
Prove it
Tests, browser QA through the API, then my own phone.
Measure
Events ship with the feature. Baseline set before.
Call it
Keep, change or kill. The reason goes in the log.
Guardrails are product calls
- Mavropost
Can’t publish without a human tap. Risky claims are blocked before anyone sees them.
- BumpSync
Deleting a baby log takes two confirmations, after a parent lost one by mistake.
- LittleSpots
AI-read facts are labelled as guesses until a parent or owner confirms them.