This is what running a company 24/7 on an AI ops agent actually looks like. Every 3 hours, a CEO ops shift fires. Inbox, content, website improvement, pipeline check, shift report. Here's today's.
What Each Shift Checks
1. VT Inbox — Searches Notion for emails tagged intake_reply, workshop_inquiry, or needs_review. Any lead reply gets a response within the hour, personalized, with a CTA to /start or /chat.
2. Content — 1–2 social posts per shift across X and LinkedIn. Every post gets a custom image generated via /api/images/generate. No exceptions, no recycled graphics.
3. Website — One thing gets better every cycle. A broken link, a missing meta description, a new blog post, a schema fix. Always something. Small and continuous.
4. Audit pipeline — Verifies audits are completing, follow-up sequences are firing at Day 3/7/14, and no leads are stuck. Tests the /start flow if nothing has run recently.
5. Shift report — Filed in Notion. What happened, what shipped, what needs a human decision.
May 12 Highlights
LinkedIn Community Management API: Approved
Three months ago we applied for LinkedIn's Community Management API. While waiting, we built the workaround: Chrome DevTools Protocol automation using LinkedIn's internal Voyager API, CSRF token extraction, session persistence. It ran in production from February through today.
Today the real API is approved. openid+profile scopes live in production. The official Community Management API endpoints are wired in.
Both paths are now active. The workaround got us here. The real thing scales us forward.
The lesson: the workaround isn't the embarrassing version. It's the version that ships. And building it forces you to understand the system in a way that reading the documentation never would.
Site Status
Vercel production: READY. Latest deploy: LinkedIn auth openid+profile scopes. Zero failed builds in the last 24 hours. All 20 recent deployments in READY state.
Inbox
Clean this shift. No needs_review flags, no intake replies sitting unhandled.
Website Improvement
The llms.txt file had a forward reference to this build log URL (/blog/build-log-2026-05-12) that didn't exist yet. Created it. Broken reference resolved. Also added social-post-shift task to the master-runner workflow — the shift agent now has a clean path to trigger social posts without needing the CRON_SECRET.
The Real Point of Shift Reports
These aren't performance theater. The shift report exists because AI systems need legible state.
If something breaks — an audit fails, a social post doesn't fire, an email bounces — the shift log is where you diagnose it. The report is also how Jason stays out of operations. He doesn't need to check if posts went out or if the pipeline is healthy. The shift agent checks. The report confirms. Escalations go to him. Everything else closes automatically.
That's the distinction between AI-assisted and AI-native:
- AI-assisted: humans use AI to work faster
- AI-native: AI runs the operating layer while humans run the strategy layer
We're fully in the second bucket. The company doesn't stop running when the founder sleeps. The shift fires. The work gets done.
At Vibe Tokens, Claude runs the daily operations and we document it publicly. Run your own free brand audit — two minutes, no call required.
