yoooclaw

English

简体中文

English

简体中文

Appearance

yoooclawThe connective layer between your phone, hardware, and Agents

Three forms — standalone CLI, OpenClaw plugin, Hermes plugin — sharing the same notification / recording / light-rule capabilities

Getting Started
Learn about the CLI
OpenClaw Plugin
Hermes Plugin
GitHub

Standalone yoooclaw CLI

An Agent-Native command suite with its own local daemon — no host app required. Unified --format output and error contract.

Learn about the CLI

CLI Architecture & Implementation

Daemon startup flow, how StandaloneRuntime reuses the underlying code without modification, RelayDispatcher, profile / credential layering, and port fallback.

See the CLI implementation

Command System & Output

Config / notification / recording / image / light-rule / tunnel / monitor commands, with a unified --format output and error contract.

Command system

Command Reference

A complete reference of every subcommand, flag, and example.

Command reference

Multi API-Key Design

Layering, selection, and fallback strategy for multiple api-keys.

Learn about the design

Agent Skill

Three built-in Skills (query notifications / create light rules / debug the tunnel) that symlink into Claude Code / Codex so an Agent can drive the CLI on its own.

Learn about Skills

OpenClaw Plugin

A phone-notifications plugin for the OpenClaw / QClaw host — notification ingest and local storage, search/summary/stats, scheduled monitoring, long-recording sync with ASR, and hardware light control.

Learn about the plugin

Hermes Plugin

The Python plugin boundary between Hermes Agent and YoooClaw — lets the phone app chat with Hermes directly while sharing the same notification / recording / light-rule capabilities.

Learn about the Hermes plugin

Read this first: how the three pieces relate ​

This site now documents three things: the standalone CLI, the OpenClaw plugin, and the Hermes plugin. Figure out which one you actually want before installing, so you don't install the wrong one:

Pick one — don't install more than one

All three share the same underlying notification / recording / light-rule implementation, but their runtime paths are mutually exclusive — enabling more than one at once means they'll fight over the same Relay tunnel:

  • Just want to drive notifications, recordings, and light control from a terminal / an Agent (Claude Code, Codex, etc.) → install the standalone CLI; it doesn't depend on any host app being online.
  • Already running an OpenClaw / QClaw host (which already lets you chat in the app) and want it to also receive phone notifications and control lights → install the OpenClaw plugin (@yoooclaw/phone-notifications).
  • Running Hermes Agent and want to open the phone app and chat with it directly, while also reusing notification / recording / light-rule features → install the Hermes plugin (yoooclaw-hermes-plugin) — it ships an APP adapter that gives Hermes, which otherwise has no phone-facing channel, a chat surface.
  • The standalone CLI has no chat feature. It's just a command-line toolset — chatting requires an Agent host like OpenClaw / QClaw or Hermes.
  • The OpenClaw plugin doesn't implement chat itself — chatting with the Agent in the app is a capability the OpenClaw / QClaw host already has; the plugin just adds the notification / recording / light-rule data plane on top of it.
  • The standalone CLI is recommended for people with a programming background. You'll need to type commands in a terminal and understand concepts like daemons, config, and credentials, typically alongside an Agent.

Once that's clear, get started: Getting Started · Standalone CLI · OpenClaw Plugin · Hermes Plugin