Capability map

Built for real engineering workflows, not only one-window chat

MyClaws is designed around multi-machine, multi-role, long-running and hand-off-friendly work. These capabilities cover the most common expansion path after your first Claw is online.

Multi-Claw

Many Claws, choose the right host for each job

Different jobs want different machines—internal network access, GPU, cached dependencies or persistent uptime can all matter.

Use one desktop surface to inspect and switch hosts
Click "Add Claw" inside Client to onboard the next machine
Power users can still use scripts and same-origin install routes

Subagents

Split architecture, implementation and review across subagents

One giant conversation quickly becomes noisy when it must carry planning, coding, debugging and review at once.

Claude Code / Codex / Conversation Agents can divide work
Orchestrator-style flows can break large work into smaller batches
Results fold back into the main thread

Trigger

Trigger lets Agents wake themselves up

Cron, Webhook and SDK cover scheduled jobs, external events and programmatic triggers.

Cron for scheduled checks and daily jobs
Webhook for external systems
SDK for your own services and tools

Skill + MCP

Skill and MCP connect MyClaws to your wider tool ecosystem

Use Skills for reusable higher-order workflows and MCP for session-level external capabilities.

Skills are installed on the Claw host and reused per role
Mount MCP by Agent or session
Tool allowlists keep boundaries tight

Memory

Cross-conversation memory preserves context between sessions

The frustrating part is rarely the model's syntax—it is the repetition required every time a fresh thread starts.

clue indexes help recall across sessions
dream helps consolidate long-term memory
user, host and project memory can evolve separately

Desktop + Mobile

Desktop for dense work, mobile for continuity and confirmation

Desktop remains the main cockpit, while mobile keeps the workflow moving when you are away.

Desktop supports attached shell, modified files and conversation forking
Mobile is ideal for notifications, acknowledgements and task boards
Push narrows the moment when a human must return

Next step

Jump from capabilities back into your own workflow

If you already know your biggest pain, jump straight into the corresponding docs. If not, start with the scenario page.

Open scenarios Open docs home