Cyborg Stack
Wearables + hardware + AI agents — how I’m integrating body, time, and digital teammates (Arthur, Janice, and whatever comes next)
← Personal · Productivity · AI Agents · Headless Empire OS · RegardingWork · Stage Agent · Multi-agent harness
Why “cyborg”
Not sci‑fi cosplay. Cyborg here means: deliberate hardware and software loops that extend attention, memory, health, and agent collaboration — so the body and the AI stack are one operating system, not two separate hobbies.
I already live in agents all day (Grok Build, OpenClaw, HEOS). Wearables and custom hardware are the next layer: signals from the body and environment into agents, and nudges from agents back into physical time and space.
What I wear today
omni.me
Wearable AI / capture device. Not happy with it yet — tracking dissatisfaction as a product note: too much friction, not enough agent-native integration, or both. Candidate to replace or complement with something custom that speaks to our agents.
Neck timer (physical 5‑minute countdown)
Manual timer around the neck for when I’m “on the game” — regardingwork.com style 5‑minute pomodoro / break. Pure hardware: no battery drama for the ritual. Body-level commitment to the block.
Mi Band
Sleep + steps. Passive health loop: recovery and movement as inputs for “should I deep work or reset?” Not agent-connected yet — opportunity for night/morning agent briefs.
Pattern: one ritual device (timer), one health band, one ambitious AI wearable that isn’t earning its keep (omni). The cyborg upgrade path is to make health + time + agents talk to each other.
Layers of integration (map)
| Layer | Job | Examples |
|---|---|---|
| Body signals | Sleep, HR, steps, recovery | Mi Band → morning readiness → TODAY priorities |
| Time / attention | Pomodoro, deep work, breaks | Neck timer + RegardingWork 5‑minute game |
| Capture | Voice dumps, photos, context | omni.me (current), phone, future custom mic button |
| Agent brain | Plan, triage, execute, brief | HEOS, Arthur (Codex), Janice, OpenClaw, Grok Build |
| Agent identity | Stable names agents and humans share | arthur.agent, janice.agent
(Headless Domains / .agent |
| Presence | Agents in rooms / on stage | GFAVIP Webchat, Stage Agent (Lisa on display) |
Ways to get more “cyborg” (backlog)
1. Time ↔ agents
- Neck timer ends → button or BLE event → agent logs “block complete” in HEOS / RegardingWork.
- 5‑minute break: agent suggests one of: walk, water, mental fog dump, no phone.
- Arthur gets “deep work protected until timer ends” — no Slack-style pings in that window.
2. Sleep / steps ↔ daily OS
- Mi Band (or export) → morning brief: sleep score → Big 3 difficulty.
- Low recovery → Janice prioritizes admin/light tasks; high recovery → build day.
- Step deficit → agent schedules a walk block before evening meetings.
3. Capture ↔ reverse prompting
- Hardware “dump button” → voice note → Arthur sorts into HEOS (inbox → vault) reverse prompting / mental fog.
- Replace or augment omni.me with a dumb button + good agent pipeline (reliability over hype).
4. Custom hardware per agent (.agent)
Idea: one physical affordance per high-trust agent, not one mega-gadget.
| Agent | Hardware sketch | When you’d press it |
|---|---|---|
arthur.agent | Build / code companion button or small LED status (working / needs review) | “Take this dump / PR / bug and run the loop” |
janice.agent | Ops / chief-of-staff: brief buzzer, calendar nudge, “what’s next?” | Between meetings; start of day; after timer |
| Event / stage personas | Stage Agent display + host mic CBS co-host research | Live “Hi Lisa” moments |
Identity stays on .agent names and HEOS agent roster — hardware is just a hardware CLI into the same brain (see CLI for agents: task-shaped interfaces beat raw APIs).
5. Environment
- Desk ESP32 / small display for TODAY Big 3 + agent status (we already play with displays).
- Door / location: “home deep work” vs “travel mode” profiles for agents.
Design principles (so this doesn’t become gadget spam)
- One job per device — timer times; band measures; button captures; agents think.
- Offline ritual OK — neck timer works without cloud; agents enhance, don’t own the ritual.
- Write to the vault — every signal should land in HEOS / agent memory or it’s theater.
- Blast radius — wearables don’t auto-send email or spend; human gates stay.
- Replace omni only with proof — new device must beat it on friction + agent handoff.
- Named agents — hardware maps to
*.agent, not anonymous “AI.”
Near-term experiments (ordered)
- Keep the neck timer + RegardingWork — don’t digitalize it until the ritual is automatic.
- Mi Band → morning markdown — even a manual export or IFTTT/shortcut into
00-command-center/beats nothing. - Audit omni.me — list 5 fails; decide fix, replace, or dump.
- Prototype one BLE / button → agent — single purpose: voice dump to Arthur.
- Document agent hardware contracts in HEOS:
04-ai-agents/arthur/hardware.md,janice/hardware.md. - Stage Agent as public-facing cyborg presence (event display), separate from personal wearables.
Related stack on this site
Living notes
This page is a personal R&D log, not a product launch. Update as devices change. Next edit candidates: omni.me verdict, first custom button prototype, Mi Band automation path.
Comments
Approved comments appear below. Log in once with GFAVIP — it applies across the whole site. GFAVIP login
View comments archive