Always-On Agents course
Build a Founder Command Center with always-on AI agents.
Install the practical operating loop behind useful AI work: capture founder inputs, turn them into scoped issues and briefs, dispatch Codex and Hermes/OpenClaw workers, review receipts in Discord, and ship the next slice without losing context.
The course outcome is a Founder Command Center: inputs from X, Discord, email, docs, and ideas become scoped work, approval-gated agent runs, daily operator reports, and reusable templates at the $49 founding preorder.
Why agent setups fail
Chat demos are easy. A founder command center needs a loop.
The course focuses on the plumbing most agent demos skip: queues, owners, approval gates, logs, and short reports you can act on.
They stay trapped as demos
A chat window or one-off script feels impressive, then disappears when there is no queue, owner, or next action.
They skip approval gates
Autonomous workers need human-readable summaries, safe handoffs, and receipts before they touch money, credentials, or production.
They create more noise than leverage
Without routing, dedupe, and recap discipline, the agent becomes another notification stream instead of an operating loop.
The operating loop
Capture → scope → dispatch → review → report → improve
This is the Founder Command Center operating loop. Each step has a job, an owner, and an artifact so the agent lane stays useful instead of noisy.
Inputs
Signals worth routing
- X bookmarks
- GitHub issues
- Client notes
- Launches
- Content ideas
Step 01
Signal
Inputs
Collect X bookmarks, launches, repo issues, content ideas, client notes, and daily radar inputs.
Artifact: Raw signal queue
Step 02
Triage
Operator
Classify what matters, discard noise, and turn raw inputs into scoped opportunities.
Artifact: Priority decision
Step 03
Issue
PM lane
Create a durable work item with context, constraints, acceptance criteria, and links.
Artifact: GitHub Issue
Step 04
Worker
Agent
Dispatch Codex/Hermes/OpenClaw with a narrow task contract instead of vague autonomy.
Artifact: Branch or artifact
Step 05
Review
Human gate
Verify diffs, previews, screenshots, and receipts before shipping or escalating.
Artifact: Approval receipt
Step 06
Recap
Command center
Return a concise Discord summary with what changed, what is blocked, and the next slice.
Artifact: Next-action summary
Receipts
Proof before the next slice
- PR link
- Preview URL
- Screenshot
- Check status
- Next slice
Course map
Build the Founder Command Center in modules
A practical build order for one private operator system. Start with the server, then add approval channels, workspace context, triage loops, and reports.
Implementation sequence
A compact lesson path. Each row should produce one durable piece of the command center.
- 01
Set up the VPS and Codex foundation
PublishedCreate the small Ubuntu server that will hold state, logs, skills, and scheduled workflows.
Build step: Get the private server online
- 02
Prepare the server for Hermes/OpenClaw
PublishedUse Codex planning mode to shape directories, secrets, logs, and the service boundary.
Build step: Prepare the runtime safely
- 03
Install Hermes/OpenClaw on the VPS
PublishedTurn the prepared server into a concrete Hermes/OpenClaw runtime with service boundaries.
Build step: Install the agent layer
- 04
Connect Hermes to Discord
PublishedCreate a private Discord bot/channel boundary before the agent starts reviewing real work.
Build step: Add the approval channel
- 05
Connect Hermes to Google Workspace
PublishedEnable Gmail, Calendar, Drive, Docs, Sheets, and Contacts through a Google Cloud OAuth client with approval-gated side effects.
Build step: Connect Workspace context
- 06
Design the AI Brain operating model
New trackDesign the four-layer operating model: chat command surface, Obsidian brain, GitHub handoffs, and verified work.
Build step: Draft email without auto-sending
- 07
Create the starter Obsidian AI Brain
NewCreate the starter Obsidian structure for durable project notes, scratchpads, decisions, workflows, templates, and reviews.
Build step: Run a client triage heartbeat
- 08
Make AI work resumable with thread scratchpads
NewUse lightweight thread scratchpads so Hermes can recover Done, Pending, Blocked, and Next after context loss.
Build step: Expand into Drive, Docs, and Sheets
- 09
Route messy inputs before they become work
NewClassify raw ideas, voice notes, bookmarks, and chat messages before deciding what deserves a scratchpad, research note, workflow update, or GitHub Issue.
Build step: Capture X bookmarks into a queue
- 10
Use GitHub Issues as agent handoff objects
NewTurn shaped scratchpad items into GitHub Issues with goal, context, scope, acceptance criteria, source links, and verification receipts.
Build step: Turn raw ideas into scoped work
- 11
Complete the first closed loop
NewRun one tiny real task through the full loop: input, scratchpad, issue, implementation, verification, and final status back to the thread.
Build step: Send one useful daily recap
- 12
Read and draft client emails
PublishedUse Hermes manually with Gmail and Calendar: read client email, summarize the ask, check availability, and draft replies for approval.
Build step: Keep Discord actions approval-gated
- 13
Automate client email triage
PublishedPoll known-client email, dedupe messages, route triage cards to Discord, and keep sends, scheduling, and queue updates approval-gated.
Build step: Plan a release watcher
- 14
Expand into Workspace playbooks
Coming nextUse Drive, Contacts, Docs, and Sheets as follow-on playbooks for client files, stakeholder maps, briefs, SOPs, and status tracking.
Build step: Tighten one part of the operating loop
- 15
Capture X bookmarks into a work queue
Skill includedInstall the bookmark capture workflow and create raw review items from saved X posts in your current work queue.
Build step: Tighten one part of the operating loop
- 16
Triage captures with Shape Up
Skill includedUse a Hermes/Codex heartbeat to turn raw captures into Shape Up work items.
Build step: Tighten one part of the operating loop
- 17
Run the daily heartbeat
NextPost captured-item summaries into Discord and apply approved decisions back to the durable queue.
Build step: Tighten one part of the operating loop
- 18
Add human approval in Discord
PlannedAdd richer Discord approvals after the deterministic capture and triage loop is working.
Build step: Tighten one part of the operating loop
- 19
Plan the Content and Release Watcher
Skill includedPlan an hourly watcher that follows Codex, Hermes, OpenAI, and trusted release sources, then turns meaningful changes into sourced article briefs.
Build step: Tighten one part of the operating loop
Free learning trail
Read the public path, then build the command center
Start with the public guides if you want the model before buying anything. Move into the package when you want the exact setup path.
Run Codex CLI on a private VPS
Codex CLI on a VPSSet up a private VPS so Codex can work with state, logs, and real project context.
Prepare the VPS for Hermes automation
self hosted AI agentPrepare the server layout, secrets boundary, logs, and service model before installing Hermes.
Install Hermes/OpenClaw as the runtime
private AI agentInstall a private Hermes/OpenClaw runtime that can run tools, skills, and scheduled workflows.
Connect Discord as the control room
Discord automation botUse Discord as the approval room for agent summaries, decisions, and operator handoffs.
Build a living AI brain
AI brain Obsidian GitHubGive your assistant durable context, execution handoffs, recovery paths, and self-healing workflows with Obsidian and GitHub.
Use X bookmarks as a workflow inbox
X API automationTurn X bookmarks into a controlled workflow inbox without letting raw saves become chaos.
Turn bookmarks into shaped business tasks
AI workflow automationShape raw captures into scoped business tasks with dry-run validation and human review.
Build an approval-gated AI email assistant
email automationBuild a safe Gmail assistant that summarizes, drafts, and waits before sending or scheduling.
Build an AI release radar
AI content automationWatch trusted releases, dedupe updates, score opportunities, and create sourced briefs.
Founding preorder
Reserve the Founder Command Center build path
Use the free checklist first. Preorder only if you want the protected implementation path at $49 founding preorder.
Package contents
Protected implementation bundle
Exact VPS and Hermes/OpenClaw command sequences, copy-paste scripts, templates, walkthroughs, update notes, and private launch-cohort support.
Launch timing
Founding cohort window
Reserve now to lock the founding price and get the first protected bundle plus cohort onboarding notes as they ship.
Price anchor
$49 founding preorder
Stripe Checkout handles the founding preorder, records checkout/payment signals, and keeps payment proof outside the success-page copy.
50% off preorder
Reserve the packaged course before the launch window closes.
Use the checklist to decide if this is worth building. Preorder if you want the exact lesson path, scripts, templates, updates, and cohort notes.
Assisted install
Want the command center installed with you?
Builders who want the system stood up with guidance can use DevelopJoy for setup help, repo/workspace structure, and a safer first operating loop.
DevelopJoy
OpenClaw/Hermes DIY Lab
DevelopJoy
Starter Support
Follow the Always-On Agents course path
Follow the complete public course path, install the skills as you go, and use DevelopJoy when you want the workflow wired into your actual VPS.