OpenClaw: Personal AI OS
Two days to run a personal AI on your VPS — Telegram, memory files, heartbeats, a GitHub pull-request loop, and MCP tools.
- Duration
- 2 days
- Level
- Intermediate
- Format
- On-site or remote
- Price
- On request
What to expect
Go from an empty VPS to a personal AI your team operates: Telegram or Slack, memory files, heartbeats, a GitHub pull-request loop, and MCP tools. Two days, on machines you keep.
- Install and operate the OpenClaw gateway yourself
- Wire chat channels and the files that give the agent continuity
- Leave with heartbeats, a GitHub PR loop, and MCP tools connected
What to know before
Who it's for
- Engineers who want a personal agent on their own VPS, not a chat window in someone else's cloud.
- Teams that already poke at agents and want Telegram, memory, and a GitHub loop wired the same way.
- Each person leaves with a gateway they installed, on a server they administer.
You'll learn to
- Install the OpenClaw gateway on a VPS and talk to it from Telegram or Slack.
- Keep the agent continuous with SOUL.md, MEMORY.md, and daily notes.
- Run heartbeats and ship a change through a GitHub pull request, then connect MCP tools.
Agenda
- 1
Day 1
- VPS setup and OpenClaw gateway install
- Telegram and Slack channels, group chat rules
- SOUL.md, MEMORY.md, daily notes — agent continuity
- 2
Day 2
- Heartbeats, cron, proactive checks
- Cursor CLI / agent loop to GitHub pull requests
- MCP servers (calendar, email, search)
How it's run
- Mostly hands-on. Most of the time is labs. Slides show up only when the next exercise needs them.
- Scoped to your stack. We use your accounts and repositories where that is the point of the day.
- Everyone drives. The group stays small enough that each person gets keyboard time.
- You keep the labs. Scripts and notes stay with the team after the last day.
Request this training
Tell me about the team and I will reply with dates and a quote for this training.
FAQs
What does this training cost?
A training is quoted after the request, not listed as a public price. The quote depends on how many people attend, whether we meet on-site or remote, and how many days you book. Send the form and I reply with a price for that team.
Is the training on-site or remote?
Both. Choose on-site or remote in the request form. On-site I come to your team and we work on your machines. Remote is the same labs over a video call, with everyone on their own keyboard.
Who is the training for?
It is for a company team that wants hands-on time on a stack I run in production. It is not a self-paced video course and it is not a public webinar. Groups stay small so each person drives.
What should we prepare before day one?
A laptop per person, and access to the accounts or repositories you want to use. After we agree dates I send a short checklist. You do not need a finished environment before the request.
Can we book fewer days than the published agenda?
Yes. The agenda is the full version. In the message, name the outcome you care about and I will cut the days to match. The quote follows the days you actually book.
How long is the OpenClaw training?
The OpenClaw training is two days for an intermediate team. Day one covers the VPS, the gateway install, Telegram or Slack, and the memory files. Day two covers heartbeats, the GitHub pull-request loop, and MCP tools such as calendar, email, and search.
Does each person need their own VPS?
Yes. Each participant runs OpenClaw on a VPS they control. The agent built in the room is the one they operate afterward, not a shared sandbox that disappears.
What can the team do after the OpenClaw training?
They can install the gateway, connect Telegram or Slack, keep agent memory in files, and open a GitHub pull request from the agent. MCP integrations for calendar, email, and search are part of day two.