The argument in one line.
PopeBot eliminates the setup friction that prevents most developers from building AI agents by letting Claude write infrastructure code through natural language, making multi-user, production-ready agents buildable in minutes instead of weeks.
Read if. Skip if.
- A solo founder or small team operator who receives high-volume email and wants to automate triage without hiring a developer or paying for enterprise tools.
- Someone comfortable with OAuth flows and basic API setup who needs a working agent deployed in under an hour rather than spending days configuring OpenClaw infrastructure.
- A builder exploring AI agents for the first time who wants to see a complete end-to-end example—from spec to deployment—before committing to a heavier framework.
- A technical operator running multiple projects who needs a free, self-hosted option with multi-user scoping and CLI access for scaling personal automation.
- You need agents that integrate with non-Google services or proprietary internal systems — this demo focuses exclusively on Gmail and basic HTTP endpoints.
- You're building a production system for non-technical end users who can't handle OAuth setup or Google Cloud credential management themselves.
- You've already shipped multiple Claude-based agents and are looking for advanced features like function calling chains or sophisticated reasoning strategies — this is entry-level.
The full version, fast.
PopeBot is a free Claude-Code-powered agent framework positioned as the easier alternative to OpenClaw for building AI agents that run your life around the clock. The system works by chatting a plain-English spec into an interface that scaffolds skills, system prompts, cron schedules, and OAuth-secured tool access on the back end, demonstrated by spinning up an email assistant that triages Gmail every thirty minutes, archives spam, and DMs urgent summaries through a Telegram bot. The practical lesson is to lean on the agent itself for setup instructions rather than waiting for tutorials, scope each agent narrowly so it stays fast and undistracted, and use multi-user routing plus Telegram integration to coordinate authorized humans through one bot.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open + promise
OpenClaw is a pain. PopeBot is free and easy. Demo target: email agent that kills spam, DMs urgent ones, can send on my behalf.

02 · Gmail OAuth setup
Add new OAuth secret named GMAIL_OAUTH_TOKEN. Google Cloud console: existing project, enable Gmail API, create OAuth client ID, paste redirect URI back into PopeBot. Empower-the-viewer aside: 'ask the agent itself for step-by-step.'

03 · Write the spec
One-paragraph instruction: check email every 30 min, archive spam, DM urgent ones with sender + summary, add a way to send email, create the required skills.

04 · Agent builds itself (Claude Code on the back end)
PopeBot delegates to the Claude Code SDK. It plans, builds the email-assistant skill, writes system prompt + CLAUDE.md, registers an AI-triage Gmail label, sets a 30-min cron, runs an end-to-end test.

05 · Admin tour — cron + agent secrets + LLM providers
Cron job listed in Triggers. Agent secrets page under Event Handler. Provider settings support Anthropic, OpenAI, Google, DeepSeek and multiple coding agents.

06 · Live triage test
Pope asks the agent to find an email worth flagging. It pulls one from his accountant, DMs him on Telegram with a summary, then applies the AI-triage label on command.

07 · Multi-user + Telegram routing
PopeBot supports multiple authorized users per install. Telegram bot per install. Profile nicknames let you say 'send Steve a test message' and have it route correctly. Bot only listens to authorized chat IDs.

08 · Interactive mode = Claude Code in the browser
Tab into a raw Claude Code CLI in-browser. Shell, file editor, voice-to-text in the chat box. Web chat, Telegram, and CLI all share the same thread.

09 · Scoped agents (anti-context-bloat)
Dropdown to scope a chat to a single agent so PopeBot doesn't get distracted by skills from other agents when you've installed 20 of them. Demos the underlying agents/email-assistant/ folder, system prompt, CLAUDE.md.

10 · Install + community CTA
Link in description, two-step wizard installer for Win/Mac/Linux, built-in upgrade system. Pitches the AI Architects community: classroom, Tuesday/Wednesday support calls, Friday networking calls.
Lines worth screenshotting.
- PopeBot wraps Claude Code's SDK so that a plain-English spec like 'check my email every thirty minutes and DM me urgent ones' scaffolds the skill, cron, and Telegram alert automatically.
- An agent that can set up its own OAuth credentials, write its own skill files, schedule its own cron job, and test end-to-end before committing is doing what used to require a developer.
- Asking the agent itself how to set up a Google Cloud project and OAuth credentials is more reliable than following a tutorial — the agent gives step-by-step instructions calibrated to your current state.
- Multi-user support in an agent framework means different people can interact with different scoped agents through the same Telegram bot without their contexts bleeding into each other.
- Supporting every major LLM provider and every major coding agent in the same framework means the infrastructure investment compounds regardless of which model wins the next benchmark.
- An AI triage label applied to processed emails creates a visible, auditable record of agent actions inside the email client itself — not just in a log file.
- The barrier to agent adoption is not capability — it is setup complexity, and frameworks that collapse setup to OAuth plus one paragraph of English unlock the majority of potential users.
Steal the format.
Pick the hottest tool in your category, claim it's harder than yours, and prove it in under 15 minutes of unedited screen-share.
- Title formula: '[Hyped Competitor] Is HARD (My [Thing] Is EASY)'. Parenthetical flip does the positioning in one breath.
- Open with the promise + the spec. State exactly what you'll build before you touch a tool — 'kill spam, DM urgent emails, let me send' — so every later beat is checked against that contract.
- Hand the boring setup back to the tool. When the demo wanders into territory you don't want to teach (Google Cloud, in this case), tell the viewer to ask the agent itself. Empowers them and de-risks your script.
- Reveal differentiators inside the demo, not in a feature list. Multi-user, Telegram routing, scoped agents, voice-to-text — each one drops in as a natural detour, not a slide.
- Earn the CTA. Twelve minutes of giveaway first, then a soft two-stage CTA (install link → community). No urgency, no scarcity, no $$.
- One screen + one face-cam + no music = totally viable for a tutorial channel. Production complexity is zero. The leverage is in the spec, the demo, and the framing — not the edit.
Terms worth knowing.
- PopeBot
- A free, open-source Claude Code-powered agent framework that provides a chat interface, multi-user support, OAuth credential management, cron scheduling, and Telegram integration for building personal or business AI agents.
- OpenClaw
- An open-source AI agent framework built around Claude Code that offers extensive configuration options, positioned as powerful but complex to set up compared to simpler alternatives.
- OAuth
- An open authorization standard that lets a user grant an application access to their account on another service (like Gmail) without sharing their password, instead issuing a secure access token.
- Google Cloud (project)
- Google's cloud platform where developers register applications, enable APIs, and obtain credentials (client IDs and secrets) that allow their apps to access Google services like Gmail.
- Cron job
- A scheduled task that runs automatically at defined time intervals (e.g., every 30 minutes), commonly used in server environments to trigger recurring processes without manual action.
- Gmail label
- A tag applied to emails in Gmail that organizes them into categories, functionally similar to folders but allowing one email to carry multiple labels simultaneously.
- Claude Code SDK
- Anthropic's software development kit that allows external applications to interact programmatically with Claude Code, enabling custom interfaces and automation wrappers to run Claude Code sessions in the background.
- Scoped agent
- A Claude Code session or sub-agent that is given access only to the context and skills relevant to a specific task or assistant, preventing it from being distracted by unrelated agents or configurations in the same system.
- Telegram bot API key
- A credential issued by Telegram's BotFather service that authorizes an application to send and receive messages through a custom Telegram bot on behalf of its owner.
- Headless mode
- Running a program or agent without an interactive user interface, allowing it to execute tasks in the background and report results asynchronously.
Things they pointed at.
Lines you could clip.
“I like to show people this because a lot of times people feel like they need somebody to show them things — but you can use these agents to actually show you how to do it.”
“All we have to do is tell our agent what we want to build.”
“I'd like to create an email assistant that checks my email every thirty minutes, automatically removes spam, DMs me when something looks urgent, and creates a way for me to send email.”
“If it was all just one big agent, it's gonna get harder and harder for the agent to be successful — that's why we have scoped agents.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Stephen Pope opens with a straight knife-fight: OpenClaw is hard, his free thing is easy, and he's about to prove it by wiring up an email-triage agent in twelve minutes flat. The whole video is the proof. There is no theory section — just OAuth tokens, one paragraph of natural-language spec, and a working scheduled agent by the credits.
Named ideas worth stealing.
Ask-the-tool-how-to-use-the-tool
When the tutorial hits an external dependency the viewer might not know (Google Cloud), Pope tells the viewer to ask the agent itself for step-by-step instructions instead of teaching it.
Scoped agents
Conversation-level scope to one sub-agent so the orchestrator isn't loading every skill in the install. Faster decisions, less drift in 20-agent setups.
One spec, four interfaces
Web chat, Telegram chat, raw Claude Code CLI, and shell all share the same conversation thread and skill registry — same agent state across surfaces.
How they asked for the click.
“Go to the link in the description, scroll down to installation, two simple steps. If you need support after install, click the link. And if you want to learn more about agents, jump into my community, the AI Architects.”
Soft, layered CTA — install link first, then community as the second offer. No pricing pressure, no urgency, just 'here's where to go'. Earns it after 12 minutes of giving away a working product.






































































