I Rode a Scooter in the Rain for 12 Hours. My 6 AI Agents Shipped a Product.

I Rode a Scooter in the Rain for 12 Hours. My 6 AI Agents Shipped a Product.

# ai# automation# productivity# indiehackers
I Rode a Scooter in the Rain for 12 Hours. My 6 AI Agents Shipped a Product.bluefin ships

How a food delivery rider runs a CEO, PM, Copywriter, Designer, Dev, and QA agent from a phone — the architecture, a minimal tick loop, and what actually ships.

Today I rode my 125cc scooter through Taipei rain for twelve hours and made NT$2,100 (about US$65) delivering lunch and dinner shifts.

In the exact same window, my phone was running six AI agents. By the time I peeled off the wet jacket, a $19 product was live on Gumroad. I didn't touch a keyboard.

This is not a manifesto. This is a Thursday.

The team that ships while I ride

Six roles, each a separate Claude CLI process with its own system prompt and memory slice:

  • CEO agent — decides scope. This morning's call: "ship Agent Cookbook to Gumroad today, $19, no feature creep."
  • PM agent — splits the day into six working blocks and assigns deliverables per block.
  • Copywriter — drafts launch copy. Fires on a red light.
  • Designer — renders covers and OG images. Runs while I wait at the restaurant counter.
  • Dev — writes and patches code. Gets the longest turns.
  • QA — reviews everything the others produce and returns a numbered list of defects.

A seventh helper, the CC Daemon, polls IMAP for 2FA codes, pastes them into forms, and pushes completion notices to Discord so I hear a ping on my helmet speaker.

A real timeline from today

  • 09:40, red light on Dunhua: I Discord-send "cookbook launch — $19 — today." CEO answers in 14 seconds.
  • 11:22, waiting for a bento: Designer drops v1 of the cover. Too busy. I reply with one emoji. v2 lands while I strap the bag.
  • 14:08, left turn on Section 4 of Zhongxiao: QA finds three factual errors in the draft. Dev patches them before the light turns green.
  • 19:55, ringing a customer's doorbell: Gumroad sends a KYC code. CC Daemon reads the email, fills the field, publishes the listing. My phone buzzes: live.

I got home soaked. The product had already made its first sale.

The architecture, end to end 

Phone (Discord)
   |
   v
CC Daemon  (hourly tick + event triggers)
   |
   v
Blackboard  (tasks.jsonl — append-only)
   |
   v  fan-out
Subagents  (Claude CLI, parallel)
   - CEO, PM, Copy, Design, Dev, QA
   |
   v
Shared memory  (MemPalace — MCP knowledge graph)
   |
   v
Output queue ---> Gumroad / Discord push / inbox/
Enter fullscreen mode Exit fullscreen mode

The blackboard is the whole trick. Every agent reads the same tasks.jsonl, claims a row, writes its output back as a new row with a parent_id. No orchestrator god-object. If one agent crashes, the row stays unclaimed and the next tick retries it.

MemPalace is the shared brain. When the Copywriter references "last week's tone notes," it's pulling from the same knowledge graph the CEO used to write today's brief. Context survives /compact, reboots, and me forgetting what day it is.

The minimum viable tick

Strip away the Discord bridge, the IMAP poller, the MCP servers, and this is the beating heart:

# Minimal daemon tick — run every 5 minutes via launchd/cron
import subprocess
from pathlib import Path

def call_agent(role_prompt: str, user_prompt: str) -> str | None:
    r = subprocess.run(
        ["claude", "-p", "--max-turns", "1",
         f"[ROLE]\n{role_prompt}\n[TASK]\n{user_prompt}"],
        capture_output=True, text=True, timeout=120,
    )
    return r.stdout if r.returncode == 0 else None

draft = call_agent(
    "You are a copywriter. 200 words max. Hook in first line.",
    "Write a Threads post about shipping while delivering food.",
)
review = call_agent(
    "You are QA. Return a numbered list of factual or tonal defects.",
    f"Review this draft:\n{draft}",
)

Path("inbox/draft.md").write_text(draft or "")
Path("inbox/review.md").write_text(review or "")
# Next tick: a Dev agent reads review.md and patches draft.md.
Enter fullscreen mode Exit fullscreen mode

Fifteen lines. Two agents. A handoff via files. Scale the same pattern to six roles and you have my setup — minus the keys I'm not going to paste.

Why I built it this way

My fixed monthly bills are NT$47,000. I cannot afford one human employee. I cannot afford to stop delivering to "focus on the startup." So I built a team I pay in electricity — less than one coffee a day on an M1 Max — that doesn't clock out when I go back on the road.

The reframe that made it click: I'm not trying to automate myself out of delivery. I'm trying to make sure the six hours I'm on a scooter aren't six hours my business is asleep. Food delivery pays cash today. Agents compound tomorrow. I need both.

What's in the cookbook

I wrote down every piece: the role prompts, the blackboard schema, the Discord-to-daemon bridge, the handoff patterns between CEO and PM, how QA returns structured defects Dev can actually apply, and the failure modes I hit in the first six weeks (there were many).

One honest line: this is a pattern cookbook — you'll wire your own Discord, IMAP, and API keys to make it run. I'm handing you the architecture and the prompts that survived contact with reality, not a one-click installer.

$19 on Gumroad. I'm asleep, on a scooter, or soaked — it's still selling.

https://vampireheart3.gumroad.com/l/agent-cookbook

This is Thursday.