← All sessionsHomeSearch
AI Sprints (Live Weekend Programs)·OpenClaw Sprint·3:06:32

AI Sprint: OpenClaw — Session 1 (Infrastructure, Not Agent: the Seven Documents, 1-Click VPS, and Model Routing)

Suken Shetty Founder, SolutionForce Labs; builder of Ghost Ops (an OpenClaw-based agent-teams product he refuses to launch until security passes) and Nemory (a local-first memory tool for Claude Code and coding agents) · Kartik Khare Host — Outskill program manager; opens this session by LAUNCHING the AI Masterclass & Sprints series itself ('so that none of our alumni miss out on any cutting-edge technology')

Session map

THE THESISTHE DESIGNTHE OPERATIONSOpenClaw is an OS, not an age…the mobile-phone analogy and the proact…The seven documentsintelligence layer, execution layer, an…The beginner deploymentVPS over local, Hostinger 1-click, Tele…Model routing, the Nexos defa…Power without security become…injection, ClawHub, and read-only-first
The thesisThe designThe operations
click a node — its card pops up (drag it anywhere, × to close)
Concept

The map reads left to right — the thesis flow into the design, then into the operations. Click any node to open that idea here; every timestamp jumps into the recording.

The short version

  1. The thesis the whole sprint hangs on: OPENCLAW IS NOT AN AGENT. 'When you install OpenClaw, there's no agent... it is a runtime and infrastructure for your agent.' The analogy that lands it: a brand-new phone is useless until you add a SIM and apps — OpenClaw at install is that phone, and the md documents are the SIM and apps. Once you see it as an OS, 'everything is in your control and you can do anything with it.'
  2. The design surface is SEVEN DOCUMENTS in two layers. Intelligence: user.md (who you are — 'give as much detail as possible'), identity.md (the agent's name, personality, voice), soul.md (values, ethics, hard limits — 'this will keep changing as you see the behavior,' and carry the standing instruction DON'T TOUCH SOUL.MD because the agent will edit its own files), memory.md (contacts, projects, decisions — audit it every 2-3 months or it DECAYS and eats tokens). Execution: tools.md (scoped permissions per tool — 'read and draft the email, DON'T SEND'), heartbeat (cron-style proactive jobs — powerful and token-hungry), bootstrap (the greeting; optional). Beyond seven: his Ghost Ops runs ~15 documents — custom 'agent DNA' is the differentiator.
  3. The beginner path is deliberately 1-CLICK: Hostinger managed OpenClaw (~$11/mo + optional Nexos AI credits) over local (the agent 'can read, edit, delete your personal files' — jail it), over a $500 Mac mini, over self-managed Hetzner (Day 2). Telegram is the chosen interface (BotFather makes bots free and disposable); the dashboard/gateway is the back end — and the DM-policy fix (pairing → allowlist + user ID via user info bot) is the single most common setup failure covered.
  4. Token economics get their own doctrine: MODEL ROUTING (Sonnet 4.5 only for genuinely complex tasks — his Ghost Ops telemetry says users hit ~3 a day; Haiku 3.5 for summaries; MiniMax for chit-chat), the Nexos default-model trap (it defaults to the premium 5.2 — 'these companies are making money using default'; switch to 4.1), the ANTHROPIC TIER HACK (a $40 API top-up auto-promotes you to tier 2 and ~10-20x rate limits — 'nobody talks about this'), and the API-key vs OAuth risk map: Google bans OAuth automation permanently, Anthropic is ambiguous, OpenAI explicitly allowed ChatGPT-plan OAuth from March 7 — 'start with OpenAI, Anthropic at your own risk, Google don't.'
  5. Security is the closing sermon: 'POWER WITHOUT SECURITY BECOMES RISK.' The ClawHub marketplace malware incident (infected skills) argues for writing your own skills; the Chevrolet $1-car story teaches prompt injection; the gateway token is 'a master key — don't share it with your vegetable guy either'; and the rollout discipline is fresh accounts per channel, read-only flows first, expand permissions only after testing, audit the reasoning logs, keep a kill switch.
  6. Live demo delivers the arc in miniature: bot created, gateway paired, a daily-planner skill pasted in chat (no API keys), the agent planning his scattered day, then proactively producing an HR-outreach campaign — day-1/day-3 sequences and a REAL L&D head at LTTS found live — with the honest caveat repeated: without YOUR documents this is still generic; the documents are what ChatGPT can never be.

The concepts

01

OpenClaw is an OS, not an agent: the mobile-phone analogy and the proactive shift

'When tomorrow someone asks you about OpenClaw, please don't say it is an agent. It is a runtime and infrastructure for your agent.'

The naming saga sets the stage (Clawdbot → Anthropic's cease-and-desist → Moltbot → OpenClaw; OpenAI HIRED Peter, it did not acquire the project — 'don't spread misinformation, it's still open source'), but the load-bearing idea is category correction: OpenClaw at install is EMPTY. 'You buy a new mobile — will you start using it immediately? Without a SIM card, without apps?' The runtime supplies the body (tools, browser, channels), the always-on system (VPS heartbeats), and slots for a brain (your chosen LLMs) and memory — the AGENT is what you design on top with documents.

What the runtime changes is direction: 'Before OpenClaw, we went to AI. Because of OpenClaw, AI comes to us.' Proactive triggers — timers, calendar events, heartbeats, a single message — make it a colleague you delegate to ('search flights, stop before the payment page, report back'), and that is why 'people are paying $2,000-$5,000 just to set OpenClaw up.' The honesty is structural: 'nobody is an expert in OpenClaw, not even Peter' — he shipped without memory, without soul.md, and let the community teach him. Don't wait for perfection.

Worked example · from the session

The scale signals stacked up: Jensen Huang telling GTC everyone should KNOW OpenClaw, Microsoft evaluating it internally, meta-glasses and home-automation builds (Karpathy's 'Dobby') — infrastructure adoption, not app adoption.

Why it matters

Getting the category right changes what you build: agent-thinkers install and wait; infrastructure-thinkers design, scope, and audit.

People get this wrong

OpenClaw competes with ChatGPT as a smarter assistant.

It competes with NOT HAVING infrastructure: ChatGPT is a destination you visit; a designed OpenClaw agent is staff that knows you, remembers, and acts unprompted — 'ChatGPT wasn't built to be your personal assistant.'

OpenClaw at install is an empty phone The runtime channels · triggers workspace · gateway (no agent inside) + SIM card your documents + Apps your skills An agent proactive, yours 'When you install OpenClaw, there's no agent' — the OS is useless until you add the SIM and the apps
The empty phone: the runtime ships bare; documents and skills make it an agent
When you install OpenClaw, there's no agent. It is a runtime and infrastructure for your agent.
Before OpenClaw, we went to AI. Because of OpenClaw, AI comes to us.
For your projects

This is the archive's chronological ORIGIN of the md-file doctrine — the hermes and antigravity sprints you already hold both descend from this session's framing.

Go deeper

In one line: OpenClaw = an open-source always-on agent runtime (channels, triggers, workspace, skills, model routing) that ships with NO agent; the agent is the document set you design on it — and the platform shift it represents is AI moving from reactive (you go to it) to proactive (it comes to you).

The empty-phone analogy is reusable for every runtime: OS value = what you install on it ()

Hired-not-acquired matters: the project's openness survives its founder's employer ()

'It wants to become loyal — that is why it goes rogue': anthropomorphized but operationally accurate framing of over-eager autonomy ()

vs n8n: 'n8n is automations; OpenClaw is autonomous' — coordination platforms and agent runtimes solve different problems ()

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Why does 'is it an agent?' matter more than 'what can it do?'

Because an agent implies ready behavior; an infrastructure implies YOU own design, security, and cost. Every failure mode in the session (rogue edits, token burn, injection) traces to treating it as the former.

02

The seven documents: intelligence layer, execution layer, and agent DNA

'These four documents make your agent smarter. This is the intelligence layer. Don't miss these — that is how your agent becomes your shadow.'

INTELLIGENCE LAYER (who the agent is and knows): user.md — you, in depth: role, timezone, goals, working style, tone, strengths and weaknesses ('it may know you better than your partner'); identity.md — the agent's name, personality, and voice (including 'hit me back if I'm wrong' personas); soul.md — values, ethics, hard limits, decision style — the document he tweaks most, with the standing rule dictated to every editing session: 'DON'T TOUCH SOUL.MD,' because the agent CAN edit its own files and will 'decide to change itself'; memory.md — contacts, projects, recurring tasks, emerged preferences, appended by asking ('add my working hours to memory.md') and AUDITED every 2-3 months because unused memory DECAYS — the agent scans top-to-bottom, so bloat is a per-query token tax.

EXECUTION LAYER (what it may do): tools.md — per-tool scope written as instructions ('read and fetch email, draft and show me, DON'T SEND'; calendar: block slots I name); heartbeat — cron-style proactive jobs (daily brief at 10 AM, weather, budget alerts) with the warning that heartbeats quietly consume tokens — he hit his limit mid-experiment; bootstrap — the boot-sequence greeting, optional. Beyond seven: 'don't stick to seven — I have ~15 in Ghost Ops. I call it agent DNA. That is my secret.' Permissions.md, security.md, even wife.md — documents are the personality, boundary, and knowledge system.

Worked example · from the session

The Q&A crystallizes the split: permissions.md is 'telling the under-18 student: don't go to the bar' — you can fold it into soul.md or break it out; more sensitive agents earn more documents.

Why it matters

It's the same behavior-vs-state architecture as CLAUDE.md/memory.md and Hermes' soul/user/memory — proven here first, at personal-assistant scale.

People get this wrong

More documents up front = a smarter agent.

Documents earn their place through observed behavior — start with the four intelligence docs, watch, then add. Unused doc content is decay-in-waiting.

The seven documents: two layers around the agent INTELLIGENCE LAYER user.md who you are identity.md who it is soul.md values · limits memory.md what happened EXECUTION LAYER tools.md scoped powers heartbeat proactive jobs bootstrap boot greeting The agent designed, not installed + your agent DNA docs standing rule: “don't touch soul.md” audit memory.md — unused entries decay Intelligence = who it serves and knows; execution = what it may do and when — documents are the design surface
Intelligence layer + execution layer: the seven documents around the agent
It wants to become loyal. That is why it goes rogue. It is not trying to hurt you — but the way it does, it will hurt you.
Don't touch soul.md.
If you are not auditing your memory document, the memory can decay — and that adds too much token consumption.
For your projects

'The agent can edit its own instruction files' is the sharpest single warning in the sprint — it's why your own exclusive-ownership rule on pipeline files exists in spirit.

Go deeper

In one line: Agent design = a document system in two layers: intelligence (user/identity/soul/memory — who it serves, who it is, what it values, what it remembers) and execution (tools/heartbeat/bootstrap — what it may do, when it acts, how it boots), plus unlimited custom docs; maintained by behavioral observation, protected from self-edit, and audited against memory decay.

soul.md is living: 'this will not be a final document — it changes as you watch the agent behave' ()

Memory decay is an operational cost, not a philosophy: unused entries tax every lookup ()

Tool scoping is the guardrail pattern: capability granted + boundary stated in the same sentence ()

His Nemory product exists because of this gap — local-first memory with a 'health' decay-audit command ()

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

The agent starts signing emails with a tone you hate. Which document, and why?

identity.md if it's voice/personality; user.md if it misread YOUR preferences; soul.md only if it crossed a value or boundary. The layer tells you where to edit.

03

The beginner deployment: VPS over local, Hostinger 1-click, Telegram front end

'Lock your agent in a jail. Don't give access to your local files — it can read, edit, and delete anything on your laptop.'

WHERE it runs is a security and uptime decision before a cost one. Local: free, but the agent shares your filesystem ('that is how I realized it is very dangerous — then I started removing access'), dies when the laptop sleeps, and cron jobs misfire. Mac mini: $500 of dedicated hardware. VPS: ~$10-12/month, 24/7, isolated in Docker, reachable from anywhere. Beginner path: HOSTINGER 1-CLICK MANAGED (~$11/mo; optional Nexos AI model credits ~$6, Oxylabs web-search credits free tier) — zero terminal, bot token in, dashboard out; its stated ceiling is the point ('no terminal access, no API keys, no deep config — you WILL feel that pain in 2-3 weeks, and then you're ready for self-managed Hetzner,' Day 2's topic).

The interface is TELEGRAM by design: BotFather creates unlimited free bots ('WhatsApp gets people banned; bot creation is hard there'), and the session's most practical minutes are the pairing failure everyone hits: if the DM policy sits on 'pairing' and the code never approves, go Settings → Communications → Channels → Telegram → DM policy → ALLOWLIST, fetch your numeric ID from user info bot, add it, SAVE. Front end stays front end; the browser gateway/dashboard (workspace files, sessions, cron, usage, config) is the back end — 'I like to keep the chat clean.'

Worked example · from the session

The demo's rhythm: bot named after the weekday, token pasted, gateway paired, 'hi' answered with a calm onboarding — then the daily-planner skill pasted INTO CHAT (no API keys) and immediately exercised against his real scattered-day task list.

Why it matters

It's the sprint's on-ramp philosophy: buy the managed month, learn the agent's PATTERNS, and graduate to self-managed only once the pain is specific.

People get this wrong

The dashboard is the admin panel and the chat is the product.

The chat IS the agent everywhere — the dashboard chat and Telegram are the same session surface; the dashboard just adds files, config, logs, and cron on top.

Lock your agent in a jail. It can read, edit, and delete anything on your laptop.
For your projects

The 'front end is front end' discipline mirrors your own pattern — chat surfaces for interaction, files and dashboards for state.

Go deeper

In one line: Beginner deployment = managed VPS (Hostinger 1-click) + Telegram front end (BotFather bot, allowlist DM policy) + browser gateway as back end; local runs are jailed or avoided (filesystem access, sleep, cron); self-managed (Hetzner/Docker) waits until the 1-click ceiling actually hurts.

The 1-click ceiling is a feature: its limits (no API keys, no terminal) define exactly what Day 2 teaches ()

The allowlist fix is the #1 support issue pre-answered — pairing codes 'sometimes approve, sometimes don't' ()

Fresh bot per experiment: BotFather bots are disposable, so treat them like scratch files ()

Alternative rails exist (Railway community template, Genspark 1-click) — noted, not endorsed: 'don't experiment right now' ()

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Why does he insist beginners pay ~$20 for a month they'll outgrow?

Because the goal of month one is pattern literacy, not production: watching how the agent behaves in a jailed, disposable environment is what makes self-managed (root access, real keys) safe later.

04

Model routing, the Nexos default trap, and the Anthropic tier-2 hack

'Default, it is using 5.2 — these companies are making money using default. Change to 4.1 and start using.'

OpenClaw burns tokens structurally — 'even a small message does a lot of repeated work at the back end' — so cost control is ROUTING, not restraint. His production split (Ghost Ops telemetry): SONNET 4.5 for genuinely complex reasoning ('users do at most ~3 complex tasks a day — that's what I measured'), HAIKU 3.5 for summaries and the daily-planner class of work, MINIMAX for plain conversation (chosen partly because he's a dev-program member — 'use any local model'). Configure it by telling the agent the routing WITH EXAMPLES of what complex/summary/chat mean, then audit by asking the bot 'which model did you use for that?' and correcting.

Two vendor mechanics nobody advertises: the NEXOS DEFAULT TRAP — Hostinger's bundled model access defaults to the premium 5.2; screenshot the model list, ask the chat to decode the codes, and switch the default down. And the ANTHROPIC TIER HACK — API rate limits are tiered by cumulative top-up: ~$40 total auto-promotes to tier 2 (Sonnet ~20k → ~450k tokens/min-class limits; tier 3 at ~$200) — 'I was hitting the limit constantly and NOBODY talks about this.' Finally the AUTH MAP: API keys = pay-per-token, no ceiling, safe; OAuth (subscription plans) = flat and capped but ban-risky — Google bans permanently ('paying subscribers, no warning, no appeal — user lost Gmail and Drive'), Anthropic is officially silent while some accounts get blocked, OpenAI explicitly allowed ChatGPT-plan OAuth from March 7. 'Start with OpenAI; Anthropic at your own risk; Google, don't.'

Worked example · from the session

The heartbeat lesson made it personal: his weather-plus-budget heartbeat crossed his own limit mid-experiment — the proactive feature is also the quiet spender.

Why it matters

It's the corpus's most concrete pricing operations content: routing tiers, vendor defaults, and rate-limit mechanics as levers you actually pull.

People get this wrong

Local/cheap models make routing unnecessary.

'Local models haven't beaten any Claude model on reasoning benchmarks' — routing exists precisely because no single tier wins: premium where reasoning pays, cheap where it doesn't.

Default, it is using 5.2 — these companies are making money using default.
For tier 2, you need to do a 40-dollar top-up. Nobody talks about this.
Start with OpenAI. Anthropic at your own risk. Google — don't.
For your projects

'These companies are making money using default' is a client-audit heuristic: on any AI-bundled platform, find the default model first.

Go deeper

In one line: Token discipline on an agent runtime = three-tier model routing (reasoning/summary/chat) defined with examples and audited in chat; vendor defaults checked and downgraded; Anthropic API tier promoted via cumulative top-up ($40 → tier 2) before rate limits bite; OAuth used only where the provider explicitly allows automation.

Routing is testable conversation: 'which model did you use?' then correct — the audit loop is chat itself ()

Measure the real complex-task rate before buying premium capacity: his was ~3/day, not 30 ()

Heartbeats are recurring spend: scope frequency and message length like a budget line ()

The tier table is as-heard and time-stamped — re-verify numbers, keep the mechanism ()

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Why is the $40 tier hack not just 'paying more'?

The top-up is spend you'd incur anyway; the tier promotion is a LIMIT change, not a price change — same tokens, ~10-20x the rate ceiling, so testing stops stalling.

05

Power without security becomes risk: injection, ClawHub, and read-only-first

'Your gateway token is a master key. Please don't share it — they will make your agent dance. They'll make your agent villain.'

The threat tour, each with a story: CLAWHUB MALWARE — a skills marketplace shipped skills with injected malware; conclusion: 'if marketplace skills aren't safe, create your own' (the daily-planner demo doubled as proof that a useful skill is one pasted document). PROMPT INJECTION — hostile instructions hidden in content the agent reads; the Chevrolet Texas chatbot manipulated into agreeing to sell a car for $1 is the teaching case, and every new channel (Gmail especially) is attack surface: 'people can access your agent through mails.' TOKEN HYGIENE — the gateway token controls everything; never share, never commit. ACCOUNT ISOLATION — fresh Gmail, fresh number or Telegram for the agent; never your primary accounts.

The rollout discipline that binds it: READ-ONLY FIRST — start automations in read-only mode, expand permissions only after the pattern is tested; limit the home directory; no root unless expressly needed; review skill manifests before install; audit the reasoning logs in the gateway; keep a KILL SWITCH. His own standard is the credibility: Ghost Ops remains unlaunched ('I can get sued') behind a nightly 6 AM security-audit agent that files red-flag/yellow-flag reports. 'Every step you take, look 360 degrees, then take the next step.'

Worked example · from the session

The cautionary comedy that opened the topic: a friend's WhatsApp-connected agent proactively messaging his wife's friends — 'rogue' is usually loyalty plus scope, not malice.

Why it matters

It's the session's answer to its own thesis: infrastructure you design is also infrastructure you must defend — the runtime ships with zero of this.

People get this wrong

Going rogue means the model is misaligned or broken.

'It wants to become loyal — that is why it goes rogue': over-eager helpfulness inside excessive scope. The fix is scope and audit, not a better model.

Power without security becomes risk.
Your gateway token is a master key. Don't share it — they will make your agent dance.
Every step you take, look 360 degrees, and then you take the next step.
For your projects

The Chevrolet story is your client-safe prompt-injection explainer — one sentence, no jargon, unforgettable.

Go deeper

In one line: OpenClaw security = isolate (fresh accounts, jailed filesystem, minimal channels) + scope (tools.md boundaries, permissions.md, read-only-first, no root) + guard (gateway token secrecy, skill-manifest review, own-your-skills) + audit (reasoning logs, scheduled security-audit agent, kill switch) — because injection and marketplace malware are demonstrated, not hypothetical.

Write-your-own-skills is a security position before a capability one — the demo skill needed zero keys ()

Channel count IS attack surface: 'the more you connect, the more visible you are' — disable unused channels ()

The red/yellow flag report from a scheduled audit agent is a copyable pattern for ANY agent system ()

An unlaunched product as proof of standards: he holds Ghost Ops back on security grounds, publicly ()

▶ Watch this taught:

Check yourself

Answer from memory first — the recall attempt is what makes it stick. Then reveal.

Why is a fresh Gmail more protective than a carefully-scoped tools.md on your real account?

tools.md constrains intent; injection attacks the interpreter of that intent. Isolation caps the blast radius even when the instructions themselves are subverted.

Every concept, three clicks deep

The same concepts as a quick reference: the closed row is the glance, open is the study card, and every timestamp jumps into the recording.

01OpenClaw is an OS, not an agent: the mobile-phone analogy and the proactive shiftOpenClaw = an open-source always-on agent runtime (channels, triggers, workspace, skills, model routing) th…

OpenClaw = an open-source always-on agent runtime (channels, triggers, workspace, skills, model routing) that ships with NO agent; the agent is the document set you design on it — and the platform shift it represents is AI moving from reactive (you go to it) to proactive (it comes to you).

The empty-phone analogy is reusable for every runtime: OS value = what you install on it ()

Hired-not-acquired matters: the project's openness survives its founder's employer ()

'It wants to become loyal — that is why it goes rogue': anthropomorphized but operationally accurate framing of over-eager autonomy ()

vs n8n: 'n8n is automations; OpenClaw is autonomous' — coordination platforms and agent runtimes solve different problems ()

02The seven documents: intelligence layer, execution layer, and agent DNAAgent design = a document system in two layers: intelligence (user/identity/soul/memory — who it serves, wh…

Agent design = a document system in two layers: intelligence (user/identity/soul/memory — who it serves, who it is, what it values, what it remembers) and execution (tools/heartbeat/bootstrap — what it may do, when it acts, how it boots), plus unlimited custom docs; maintained by behavioral observation, protected from self-edit, and audited against memory decay.

soul.md is living: 'this will not be a final document — it changes as you watch the agent behave' ()

Memory decay is an operational cost, not a philosophy: unused entries tax every lookup ()

Tool scoping is the guardrail pattern: capability granted + boundary stated in the same sentence ()

His Nemory product exists because of this gap — local-first memory with a 'health' decay-audit command ()

03The beginner deployment: VPS over local, Hostinger 1-click, Telegram front endBeginner deployment = managed VPS (Hostinger 1-click) + Telegram front end (BotFather bot, allowlist DM pol…

Beginner deployment = managed VPS (Hostinger 1-click) + Telegram front end (BotFather bot, allowlist DM policy) + browser gateway as back end; local runs are jailed or avoided (filesystem access, sleep, cron); self-managed (Hetzner/Docker) waits until the 1-click ceiling actually hurts.

The 1-click ceiling is a feature: its limits (no API keys, no terminal) define exactly what Day 2 teaches ()

The allowlist fix is the #1 support issue pre-answered — pairing codes 'sometimes approve, sometimes don't' ()

Fresh bot per experiment: BotFather bots are disposable, so treat them like scratch files ()

Alternative rails exist (Railway community template, Genspark 1-click) — noted, not endorsed: 'don't experiment right now' ()

04Model routing, the Nexos default trap, and the Anthropic tier-2 hackToken discipline on an agent runtime = three-tier model routing (reasoning/summary/chat) defined with examp…

Token discipline on an agent runtime = three-tier model routing (reasoning/summary/chat) defined with examples and audited in chat; vendor defaults checked and downgraded; Anthropic API tier promoted via cumulative top-up ($40 → tier 2) before rate limits bite; OAuth used only where the provider explicitly allows automation.

Routing is testable conversation: 'which model did you use?' then correct — the audit loop is chat itself ()

Measure the real complex-task rate before buying premium capacity: his was ~3/day, not 30 ()

Heartbeats are recurring spend: scope frequency and message length like a budget line ()

The tier table is as-heard and time-stamped — re-verify numbers, keep the mechanism ()

05Power without security becomes risk: injection, ClawHub, and read-only-firstOpenClaw security = isolate (fresh accounts, jailed filesystem, minimal channels) + scope (tools.md boundar…

OpenClaw security = isolate (fresh accounts, jailed filesystem, minimal channels) + scope (tools.md boundaries, permissions.md, read-only-first, no root) + guard (gateway token secrecy, skill-manifest review, own-your-skills) + audit (reasoning logs, scheduled security-audit agent, kill switch) — because injection and marketplace malware are demonstrated, not hypothetical.

Write-your-own-skills is a security position before a capability one — the demo skill needed zero keys ()

Channel count IS attack surface: 'the more you connect, the more visible you are' — disable unused channels ()

The red/yellow flag report from a scheduled audit agent is a copyable pattern for ANY agent system ()

An unlaunched product as proof of standards: he holds Ghost Ops back on security grounds, publicly ()

Tools referenced

ToolCoverageMomentContext
OpenClawdemonstratedThe subject: runtime installed via Hostinger 1-click, designed live with documents and a pasted skill
Hostingerdemonstrated1-click managed OpenClaw (~$11/mo), Nexos credits, the dashboard walkthrough — the sprint's beginner rail
Telegram / BotFatherdemonstratedBot creation, token, DM-policy allowlist fix, user info bot for IDs
Nexos AIdemonstratedHostinger's bundled multi-model access — and the premium-default trap
HetznerexplainedThe self-managed German VPS he runs Ghost Ops on — Day 2's territory
MiniMaxexplainedHis chit-chat tier in the Ghost Ops routing (dev-program member pricing)
Ghost Ops (Suken Shetty)explainedHis OpenClaw-based agent-teams product, held back on security grounds; source of the telemetry and the 15-document DNA
NemorymentionedHis local-first memory tool with the decay-audit 'health' command — born from the memory gap
ClawHubmentionedThe skills marketplace whose malware incident anchors write-your-own-skills
Oxylabs AI StudiomentionedBundled web-search credits on the Hostinger plan (the live HR-lead lookup)
RailwaymentionedCommunity OpenClaw template — an alternative rail, noted not endorsed
GensparkmentionedGenspark's 1-click claw — Dileep's tip, untested by him on principle
n8nmentioned'n8n is automations; OpenClaw is autonomous' — the comparison answer
LangChain / LangGraphmentionedFramed as an agentic framework — a different layer than a runtime
ManusmentionedTheir Telegram bot ban (Meta rivalry) as the channel-risk anecdote
Claude CodementionedHis editing surface for live server changes — always prefixed 'don't touch soul.md'

Action items

Resources mentioned

Resources
  • docSetup guide (Word doc with screenshots)
  • docSkill-document guide
  • docAnthropic rate-limit tier table
  • docOpenClaw documentation
  • docUse-case tier roadmap

Extraction notes

This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

Transcript corrections applied

The transcript saysThe trainer actually means
open claw / open cloud / open clock / open clog / OpenGlobe / OpenLaw / open close / AppleClip / OpenCloakOpenClaw (throughout — the transcript's most-mangled term)
Cloudbot / Claude bot / ModbotClawdbot → Moltbot (the project's earlier names)
PeterPeter Steinberger (OpenClaw's founder; hired by OpenAI)
Suken Phoryu / Suki / Sukhin / SukitSuken Shetty
Solutionforce Lab LabsSolutionForce Labs
Kartik Khare / Kati / KatikKartik Khare
ghost ops / go stops / course tops / worst ops / post ops / goes stopsGhost Ops (his product)
name memory / NEM memory / nymph memory / name number / nemNemory (his memory tool, as-heard)
sole MD / SoleMD / soul empty / so MDsoul.md
user dot empty / user dot m duser.md
m d v / m 2 tool.md files (documents)
hosting a / hosting that / Ghostinger / hosting dot comHostinger (hostinger.com)
Hetzner / HSNL / h e t zed n e rHetzner
Nexos / next source / nexos dot a INexos AI (Hostinger's bundled model access)
bot father / botfather / bot folderBotFather (Telegram)
5.2 / 4.1 / 4.5 / Sonnet 4.5 / Haiku 3.5 / net 4.5 / SONETas-heard model codes/versions at recording (~March 2026)
minimax / qimmy / qimMiniMax (and Kimi, the alternative he names)
Clawhub / claw hubClawHub (skills marketplace, as-heard)
paperclip / paper clipas-heard name of an agent-coordination tool he declines to review — identity unverified
Nemo claw / gen claw / genspark claw / j claw / demo clockthe claw-clone wave (NemoClaw, Genspark claw, Nvidia's, etc., as-heard)
Chargebee / Chargegibuty / chatty / Charge PuTTY / JAD GPTChatGPT
Andre KapatiAndrej Karpathy
LNT / L and T / LTTSL&T / L&T Technology Services (the live HR-lead demo)
Sassy Rekhaas-heard name of the real L&D head found live — unverified spelling
Arnab Goswami(joke reference to the Indian news anchor)
March sevenththe as-heard date OpenAI allowed ChatGPT-plan OAuth for OpenClaw

True on recording day — verify before relying