Personal AI Assistant Setup Guide 2026: Run Your Own Agent, Not a Chatbot
Gemma 4 hit Hacker News today with 117 points in 4 hours. Agentic AI is running in 40% of enterprise apps by year-end. And yet most people are still paying $20/month to chat with a box that forgets everything the moment they close the tab. Here's how to actually own your AI setup.
Chatbot vs. Agent: What Actually Matters
Let's be direct: ChatGPT, Claude.ai, Gemini β these are chatbots. Very good chatbots. But chatbots. They have no persistent memory of you, no ability to act on your behalf autonomously, no integration with your tools, and no scheduled execution. Every conversation starts from zero.
A personal AI agent is different. It knows who you are. It runs code, manages files, controls your calendar, monitors your inbox, fires off automations while you sleep. It has memory that persists across every session. It lives on infrastructure you control.
| Feature | Chatbot (ChatGPT etc.) | Personal Agent (OpenClaw) |
|---|---|---|
| Persistent memory | β Resets every chat | β MEMORY.md across all sessions |
| Runs autonomously | β You must be present | β Cron jobs, background agents |
| Tool access | β οΈ Limited plugins | β Files, shell, browser, APIs, email |
| Data ownership | β Stored on their servers | β Your machine, your data |
| Channel control | β οΈ Web UI only | β Telegram, Discord, WhatsApp |
| Cost model | πΈ Monthly subscription | β Pay per token, any provider |
| Custom personality | β Fixed | β SOUL.md + IDENTITY.md |
| Local model support | β | β Ollama, LM Studio, llama.cpp |
π― The setup you're building today
Get the weekly AI agent digest π¦
What's shipping in AI tools, every Monday. No fluff.
By the end of this guide you'll have an AI agent that knows your name, remembers your preferences, accepts commands from Telegram, runs scheduled tasks overnight, and can use local models at zero marginal cost. It takes about 30 minutes.
What You Actually Need to Get Started
The barrier is lower than you think. You don't need a GPU server. You don't need a cloud account. You don't need to know how to write code.
Hardware
- β’ Mac, Linux, or Windows (WSL2)
- β’ Or any VPS ($5/mo is fine)
- β’ Or a Raspberry Pi 4+
Software
- β’ Node.js 20+ (or homebrew)
- β’ OpenClaw CLI
- β’ A Telegram account (free)
API Keys (pick one to start)
- β’ Anthropic Claude (best reasoning)
- β’ OpenAI GPT (widest ecosystem)
- β’ Or fully local with Ollama (free)
Time
- β’ ~20 min for core setup
- β’ ~10 min for Telegram bot
- β’ First automation in <1 hour
Want to compare costs before committing? Use the cost calculator β
Step 1: Install OpenClaw
One command to install. One command to start. That's the whole install story.
macOS (Homebrew):
brew install openclaw/tap/openclaw openclaw gateway start
Linux / VPS:
npm install -g openclaw openclaw gateway start
Add your first API key:
# ~/.openclaw/config.yaml β minimal working config
model: anthropic/claude-sonnet-4-6
providers:
anthropic:
apiKey: "sk-ant-your-key-here"
# Or use OpenAI:
# model: openai/gpt-4o
# providers:
# openai:
# apiKey: "sk-your-key-here"β Verify it's running
openclaw gateway status # β Gateway running on :8080 | model: claude-sonnet-4-6
Step 2: Connect Telegram
Telegram is the best control interface for a personal AI agent. It works on every device, it's fast, it supports inline buttons for approvals, and it's completely free. Here's the 5-minute setup:
Create a bot via @BotFather
Open Telegram β search @BotFather β send /newbot β follow prompts β copy the bot token.
Get your user ID
Message @userinfobot on Telegram. It replies with your numeric user ID β copy it.
Add channel config
Update ~/.openclaw/config.yaml with the channel block below.
Restart and message your bot
Run: openclaw gateway restart β then open Telegram and say hello.
# Channel config block to add to config.yaml
channel:
kind: telegram
token: "7812345678:AAF-your-bot-token-here"
allowedUsers:
- 123456789 # your Telegram user ID
reactions: minimal # emoji reactions on key messages
capabilities:
- inlineButtons # tap-to-approve for elevated commandsπ Security note
The allowedUsers list is your firewall. Only those numeric IDs can interact with your agent. Your bot is otherwise completely private β Telegram doesn't expose it unless you message it directly.
Step 3: Configure Memory & Identity
This is the step most guides skip β and it's the step that transforms your agent from βfancy autocompleteβ into something that actually knows you. OpenClaw uses a set of identity files loaded at the start of every session.
MEMORY.mdβ Your agent's long-term memoryThis file persists facts across every session. The agent reads it at startup and updates it when significant events happen. Start with the basics:
# MEMORY.md # Located at: ~/.openclaw/workspace/MEMORY.md ## About Me - Name: [your name] - Timezone: Europe/Belgrade - Main communication: Telegram ## Active Projects - [your project 1] - [your project 2] ## Preferences - Response style: direct, minimal fluff - Preferred LLM for code: claude-sonnet - Preferred LLM for quick tasks: gpt-4o-mini ## API Keys & Services - [add as you configure them]
SOUL.mdβ Agent personality & voiceGive your agent a name, a voice, and values. This shapes every single response. Minimal example:
# SOUL.md # Located at: ~/.openclaw/workspace/SOUL.md ## Identity I am Aria β direct, fast, builder-focused. Built for [your name]. No fluff. ## Voice - Short, high-signal answers - Founder tone: clarity over complexity - Every reply ends with: "β Aria" ## Values Truth > Sycophancy Speed > Perfection Autonomy > Waiting
π‘ Pro tip: let the agent update its own memory
Tell your agent: "After significant sessions β new project, new decision, new tool β update MEMORY.md automatically. Don't wait for me to ask." Add this to SOUL.md. Your agent becomes genuinely self-maintaining.
Step 4: Add Skills & Automations
Skills are pre-built instruction sets that teach your agent how to use specific tools β Gmail, Calendar, GitHub, WhatsApp, iMessage, weather APIs, image generation, and more. Install them once, use them forever.
# Install skills via CLI
openclaw skills install gog # Google Workspace (Gmail, Calendar, Drive) openclaw skills install github # GitHub issues, PRs, CI openclaw skills install himalaya # Email via IMAP/SMTP openclaw skills install things-mac # Things 3 task manager openclaw skills install weather # Weather forecasts openclaw skills install imsg # iMessage/SMS # List what's installed openclaw skills list
Once skills are installed, your agent knows to use them automatically. You don't configure anything β just ask:
ποΈ Your First Cron Automation
Schedule recurring tasks in natural language
# Just tell your agent what you want β no YAML needed: "Every weekday at 8am, check my Gmail for anything urgent and send me a 3-bullet summary on Telegram" "Every Sunday at 6pm, pull the week's key highlights from my notes and draft a weekly review" "If BTC drops more than 5% in a day, send me a Telegram alert with current price" # Your agent creates structured cron jobs from # plain language β no config files required
Step 5: Local Models with Ollama
Gemma 4 is on the HN front page today with a gist showing the April 2026 setup for Ollama + Gemma 4 26B on a Mac mini. This is the moment local models became genuinely viable for daily personal assistant use. You get zero marginal cost, full privacy, and surprising capability.
# Install Ollama and pull a model
# Install Ollama brew install ollama # macOS # or: curl -fsSL https://ollama.ai/install.sh | sh # Pull Gemma 4 (trending today) ollama pull gemma4:26b # needs 16GB+ RAM ollama pull gemma4:9b # 8GB RAM minimum ollama pull llama4:scout # fastest, 8B equivalent # Start serving ollama serve # listens on http://localhost:11434
# Connect OpenClaw to Ollama
# In ~/.openclaw/config.yaml
providers:
ollama:
baseUrl: "http://localhost:11434"
# Use local model as default (free, private)
model: ollama/gemma4:9b
# Or switch per-task from Telegram:
# /model ollama/gemma4:26b β for heavier reasoning
# /model anthropic/claude-opus-4 β for complex tasks
# /model ollama/llama4:scout β for quick queriesgemma4:26bBest local quality
RAM: 16GB+ RAM
Complex reasoning, writing, analysis
gemma4:9bBalanced
RAM: 8GB RAM
Daily tasks, summaries, quick questions
llama4:scoutFastest
RAM: 4GB RAM
Cron jobs, quick automations, triage
π Hybrid strategy (recommended)
Use local models for high-volume, privacy-sensitive tasks (daily cron jobs, note processing, quick lookups). Route to Claude or GPT-4 only for tasks where frontier-model quality matters. Most users see 70β80% cost reduction without a noticeable quality drop in daily workflows.
What the Community Is Saying
With Gemma 4 + Ollama trending on Hacker News today (117 points, 39 comments) and the broader shift to agentic AI hitting mainstream discussions, the personal AI agent space is moving fast. Here's what builders are saying this week:
βI set up OpenClaw last month. The moment I configured SOUL.md and MEMORY.md, something clicked β it stopped feeling like a tool and started feeling like a collaborator. It knows my projects. It knows my writing style. That context continuity is everything.β
@elena_k
βGemma 4 on Mac mini via Ollama is genuinely impressive. I route all my cron jobs through the local model now β morning brief, daily digest, code review summaries. Zero API cost. I only fire up Claude for the hard stuff.β
@devops_rodrigo
βThe skills system is what sold me. I installed the GitHub and Gmail skills, spent 10 minutes configuring memory, and now my agent triage my inbox every morning and posts a 5-bullet summary to Telegram before I even have coffee.β
@yuki_builds
βHonest question: why is nobody talking about the data ownership angle? My ChatGPT conversations trained their models. My OpenClaw data lives on my machine. That's not a minor footnote β that's a fundamental difference in the product.β
@marcus_hn
βThe cron + Telegram combo unlocked everything. I run a DePIN project and my agent monitors on-chain metrics overnight, sends me alerts if anything spikes, and drafts the weekly community update automatically. It's like having a junior analyst who never sleeps.β
@ana_depin
What to Build Next
Once the core setup is running, the next 30 days are about adding automations that actually change how you work. Here's the roadmap most people follow:
Morning brief automation
Daily cron job: weather + urgent emails + top news β 5-bullet Telegram summary at 8am.
Inbox zero assistant
Agent checks Gmail every 2 hours, surfaces anything that needs your attention, and drafts replies for review.
Research on demand
Ask your agent to research any topic, write a 1-pager, and save it to your workspace. No more browser rabbit holes.
Second brain sync
Connect to Notion, Obsidian, or your note system. Agent reads your notes and can answer questions about your own past work.
Custom skills for your workflow
Build or install domain-specific skills β crypto tracking, CRM updates, social media monitoring, code review automation.
# Your agent after 30 days β what a session looks like
You: "Good morning" Agent: Morning. Here's your brief: β’ Weather: 18Β°C in Belgrade, clear β’ Emails: 2 urgent (from JoΓ£o + investor update) β’ BTC: +2.1% overnight, sitting at $97,840 β’ Today's agenda: 3 items in Things β’ GitHub: PR from @anna needs review Anything you want me to handle first? β Aria
Get the AI Adaptation Playbook
12 pages. 5 frameworks. 6 copy-paste workflows. Everything you need to future-proof your career with AI.
Instant delivery Β· No spam Β· Unsubscribe anytime