Skip to content

Best practices

PhysiClaw works three ways: as your personal assistant, as an MCP server connected to a coding agent, and with playbooks for the tasks you repeat.

PhysiClaw gets to know your preferences as you use it.

Be specific about what you want. The clearer your request, the fewer wrong turns it takes. In particular, name the app to use.

Tell it to “remember”. Anything you want it to hold onto for the long run, like your preferences, a saved address, or your rules, just tell it to remember, and it uses that in every future conversation.

Schedule recurring tasks. PhysiClaw can run tasks on a schedule, just tell it when.

If you already work with a coding agent, you can connect PhysiClaw to it as an MCP server. The agent runs on your computer, and you drive the phone straight from the terminal.

Anything you do repeatedly, like the weekly grocery order or the morning coffee, belongs in a playbook rather than a skill. A skill hands every step to the model. A playbook records the fixed steps and calls the model only where judgment is needed. That cuts token usage by 50 to 100 times and runs several times faster. You can have your coding agent write the playbook for you, then run it through on your own phone and enable it once it works.