Skip to content
Automation
Agent

BOOT

On gateway restart, verify HomeClaw is operational:

From plugin
homeclaw
1557 skills7 agents4 commands1 MCP
Install
> /plugin marketplace add omarshahine/HomeClaw
> /plugin install homeclaw@homeclaw

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

On gateway restart, verify HomeClaw is operational:

Agent definition

BOOT.md

HomeClaw Boot Checklist

On gateway restart, verify HomeClaw is operational:

1. Check if HomeClaw app is running (`homeclaw-cli status`) 2. If not running, log a warning — webhooks will fail until the app starts 3. Read `memory/MEMORY.md` and yesterday's daily log to restore context

Ships withhomeclaw

HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw

Get the whole plugin