← Back to all playbooks

Nat

NAT ELIASON: ClaudeBot 24/7 agent
Start: 02:30:23
Sketch note for Nat's session
TL;DR

Shift from 'coder' to 'Engineering Manager' by running an autonomous 24/7 agent (ClaudeBot) on dedicated hardware that orchestrates specialized sub-agents for implementation, review, and user feedback analysis.

Key Insights

Dedicated Hardware for Persistent Agents

02:34:34

Use a dedicated Mac Mini ($500) to run ClaudeBot 24/7. This allows for 'asynchronous building' where you send voice-note instructions via Telegram at night and wake up to completed features and tested PRs.

Recursive PR Review for Scope Narrowing

02:45:11

Configure Claude to 'review its own review.' It identifies which suggestions are critical for the current PR and which should be spun off into separate GitHub issues, preventing scope creep while ensuring technical debt is tracked.

Model-Specific Orchestration (Opus vs. Codex)

02:49:21

Use Opus 4.5 as the 'Engineering Manager' for high-level orchestration and Codex 5.2 as the 'Worker' for deep implementation. This leverages Codex's coding depth while utilizing Opus's superior general intelligence for planning and review.

Automated User Frustration Ingestion

02:55:21

Build a custom API that pulls daily conversation logs at 2 AM for Claude to analyze. It identifies user friction points, generates a Google Doc report, and waits for a voice-note approval to trigger Codex agents for fixes.

Systems

The Recursive PR Loop

  1. Open a PR on GitHub.
  2. Claude GitHub app performs initial review.
  3. Claude reviews its own suggestions to categorize them into 'Immediate Fix' vs 'Future Issue'.
  4. Claude creates GitHub issues for 'Future' items.
  5. Claude implements 'Immediate' fixes and pushes to the PR.
  6. Upon PR merge, Claude evaluates the previously created issues to decide if they still require implementation.
Tools: Claude Code, GitHub Actions, Conductor Build

Autonomous Bug-Fixing Pipeline

  1. Sentry detects a production error.
  2. Error is sent to a specific Slack channel.
  3. ClaudeBot is tagged in Slack and analyzes the stack trace.
  4. ClaudeBot spins up a Codex sub-agent to write the fix.
  5. Codex opens a PR to the staging environment.
  6. ClaudeBot pings the user on Telegram for final merge approval.
Tools: Sentry, Slack, ClaudeBot, Codex 5.2

Tools

Conductor BuildClaude CodeCodex 5.2Opus 4.5ClaudeBotMonologue (Voice-to-Text)TelegramSentrySlackMac Mini