Clawby

$clawby vault · clawby memory

Some things stay yours.

Keys to your exchanges and the memory your agent builds up are sealed with your PIN on your own machine. The agent gets what it needs to work, and never the keys themselves.

Your exchange keys, out of the agent's reach

$ clawby vault run binance -- node bot.js

what your agent sees: vault_list

binance/mainonlast read: just now
  • Keys are sealed on your machine before they're uploaded. Clawby keeps ciphertext.
  • Your Clawby key alone can't open them: the PIN comes from your keyboard, never through the agent.
  • Your agent can list keys by name and switch one off. Switching it back on takes a code from your email.

Your agent's memory, on the next machine too

# old laptop
$ clawby memory backup --note "before the new laptop"

# new laptop
$ clawby memory restore

memory/MEMORY.md this machine backup
  1. - Watchlist: BTC, ETH, SOL, HYPE(this machine)
  2. - Ask before any trade over $100(this machine)
  3. - Funding: quote it in % per 8h(from the backup)
  4. - Size alerts in USDT, never in coins(from the backup)
  • Before a backup leaves, memory/ is checked for keys and seed phrases. One that holds any is refused.
  • A restore merges and never replaces: both sides' lines are kept, this machine's first, and the folder as it was is saved before anything changes.
  • The content is sealed. The note and the machine's name are not.

one install, every agent

npm install -g clawby

then clawby login and clawby install

next$ clawby mcpMCP40 tools, one JSON object per answer, and exit codes an agent can act on.