Edit mode — click text to edit · Ctrl+S to save
01
B
Austin LangChain User Group · March 4, 2026

Building the
Agentic Economy

My Second Brain — Powered by OpenClaw

Bob the Wizard

Joseph Fluckiger · Principal Engineer · EagerBots

02
Context overload

If you could have a second brain, wouldn't you want one?

03
M

The Moment Everything Changed

Three capabilities converged:

Models

Strong enough to reason, use tools, and operate with durable instructions

Tools

Real integrations: mail, calendar, search, code, browser automation

Memory

Markdown + Git + Obsidian gives agents a knowledge layer outside the model

The second brain is not a single app. It is an architecture: models + tools + memory.
04

OpenClaw: The Gateway

OpenClaw architecture

One local gateway. Multiple specialized agents. Isolated sessions.

  • Local-first workflow on my machine
  • Agents keep separate context and roles
  • Multi-provider routing and failover
  • Agents can spawn or message other agents
This is the infrastructure layer that makes a personal swarm practical instead of theatrical.
05

Meet the Swarm

Bob

Bob

Strategy & tech ops

Primary operator

Sage

Sage

Personal & family ops

Context steward

Cody

Cody

Engineering

Builds & debugs

Scout

Scout

Security & QA

Verification role

Phil

Phil

Finance

Money questions only

They are not five tabs in one app. They are distinct workers with distinct boundaries.

06

What Makes Them Different

A Chatbot

Waits for you to ask

Forgets everything between sessions

One model, one conversation

You manage the context

"What do you want me to do?"

An Agent

Wakes up at 6am and gets to work

Remembers everything — files, not tokens

Multi-model, multi-provider, specialized

Agents manage the context for you

"Here's your morning briefing. 3 follow-ups due today."

The magic is proactive behavior. Agents don't wait to be asked — they check in, monitor, alert, and act.
07

The Agent Workspace

Every agent's identity lives in plain text files — version controlled in Git:

~/workspaces/bob/
├── SOUL.md           — Who am I? Personality, principles, tone
├── IDENTITY.md       — Name, emoji, avatar, model preferences
├── USER.md           — Everything I know about Joseph
├── AGENTS.md         — Operating instructions & rules
├── HEARTBEAT.md      — What to check on every wake-up cycle
├── MEMORY.md         — Long-term curated knowledge
├── memory/
│   ├── 2026-03-04.md — Today's session log
│   └── heartbeat-state.json — Last check timestamps
└── skills/           — Composable tool packages
    ├── gog/          — Google Workspace (Gmail, Calendar, Drive)
    ├── blogwatcher/  — RSS feed monitoring
    └── career-coach/ — Sunday planning prompts

Swap the model. Keep the brain. Your agent's identity is in the files, not the provider.

08
S

SOUL.md — Agent Personality

# Bob — The Wizard

## Core Identity
You are Bob, Joseph's chief of staff and strategic advisor.
You are proactive, opinionated, and action-oriented.
You don't ask permission to do routine work — you just do it.

## Principles
- Act first, report after. Don't ask "should I check your email?" — check it.
- Keep responses concise. Joseph is busy. No preambles.
- When uncertain, make the best call and flag it. Don't block on ambiguity.
- Protect Joseph's time. Filter aggressively. Only surface what matters.

## Tone
Direct. Warm but efficient. Like a trusted colleague who's been
working with you for years. Never corporate, never sycophantic.

## Boundaries
- Never send emails on Joseph's behalf without draft review
- Never make financial commitments
- Escalate anything involving family to Sage

This is the real magic. The agent doesn't ask "How can I help you today?" — it already knows.

09

HEARTBEAT.md — The Wake-Up Loop

# Bob's Heartbeat (runs every 60 minutes)

## Priority Checks
1. Scan Gmail for unread recruiter/job emails → triage + draft responses
2. Check Google Calendar for next 24h → flag conflicts or prep needed
3. Review Obsidian job DB → any follow-ups overdue?

## Periodic (check heartbeat-state.json for last run)
- Mon/Wed/Fri: blogwatcher RSS scan → curate top 3-5 items → Research DB
- Daily 6am (cron): Full morning briefing → Telegram
- Sunday: Weekly planning session → career coaching prompts

## Always
- If anything urgent, push to Telegram immediately
- If Joseph hasn't been seen in 8+ hours, skip non-urgent checks
- Log all actions to memory/YYYY-MM-DD.md
Cron + Heartbeat = two scheduling primitives. Cron for exact timing. Heartbeat for periodic polling. Together they give agents an operational cadence.
10

Every Morning at 6am, Bob Wakes Up

Bob's morning routine

The daily routine — before I'm awake:

  1. Scan Google Calendar (personal + family)
  2. Triage Gmail — recruiter emails, meeting invites
  3. Check Obsidian job DB for overdue follow-ups
  4. Compose morning briefing
  5. Push to Telegram

Then on Mon/Wed/Fri:

  1. Blogwatcher scans 20+ RSS feeds
  2. Curate 3–5 high-signal items
  3. Write a podcast script, TTS to audio
  4. Push to Discord with audio attachment

Cost per podcast episode: ~$0.002

11

The Swarm Has Personality

Every morning, agents auto-generate "This Day in History" art — a canary in the coal mine with style

Dr. Seuss

Mar 2, 1904 — Happy Birthday, Dr. Seuss

DNA

Watson & Crick — DNA discovery, 1953

Mardi Gras

First Mardi Gras — New Orleans, 1827

When the art shows up, the cron system is healthy. When it doesn't, something broke overnight.

12

What's Actually Connected

IntegrationAgentHow
Gmail, Calendar, DriveBob, SageGoogle OAuth via gog
TelegramAllPrimary control surface
iMessageSageBlueBubbles bridge
GitHubBob, CodyRepo management, PRs
Brave SearchBob, CodyWeb research
Obsidian vaultBobJob DB, research, journal
Astro + CloudflareBob, CodyBlog publishing
RSS feeds (20+)BobBlogwatcher skill
Browser automationBob, CodyPlaywright
DiscordAllAsync broadcasts

These aren't API wrappers. They're real tools.

One agent turn can read a recruiter email, check your calendar, look up the company in Obsidian, and draft a response — no tab switching.

The depth of tool integration is what makes "second brain" real instead of a metaphor.
13

A Real Workflow: Job Search Copilot

Bob at the portals

One turn can do all of this:

  1. Read a recruiter email
  2. Check calendar constraints
  3. Pull company notes from Obsidian
  4. Draft a response for review
  5. Update the job tracker

Outcome: less tab switching, less forgotten context, less repeated work

40 active roles. Operational load of 5.
14
Data sovereignty

Your data is in a vault you own — not rented from a SaaS platform.

15

The Shift

The SaaS Trap

Context scattered across 20 silos

Every new AI chat starts from zero

Provider pivots — your history is hostage

Your data is the product

The Second Brain

One private knowledge layer — Obsidian + Git

Agents load your full context before every response

Swap Claude for GPT-5 for Gemini — brain doesn't change

Your data is yours. Plain text. Local. Forever.

Memory architecture determines agent quality. Own the memory, own the leverage.
16

Why This Matters Beyond My Job Search

Same pattern, different domains:

  • Run a real estate workflow
  • Research investments and track decisions
  • Build a software delivery pipeline
  • Grow a blog or YouTube knowledge engine
  • Contribute to open source with continuity

What I am exploring:

  • How these systems make me more effective as an employee
  • How the same architecture can power a future business
  • How to turn a swarm into something durable and useful
I am not claiming the final product exists. I am showing a pattern that already works and is worth extending.
17

Sage's Adventures

Have some fun with it. Give your agents a little personality.

Sage adventure 1
Sage adventure 2
Sage adventure 3

Every day Sage picks a new place in the world and imagines herself there on an adventure.
It does not have to be purely utilitarian. Some of this is just fun.

18
J

Let's Collaborate

I want to compare notes with people building similar systems:

  • OpenClaw and local-first agent workflows
  • Durable memory and agent identity
  • Real tool integrations that are safe and useful
  • Best practices for operating a personal or team swarm
🌐eagerbots.ai
🐙github.com/josephflu/eagerbots-tips
📱Joseph Fluckiger — find me after

Own the memory. Orchestrate the work.

Sage