ClawLink forMuse

Read your mail, edit your docs, post to your accounts and pull your numbers from 1,100+ apps, without leaving Muse.

Paste this into Muse

Muse says to run it on your own computer? Paste the full prompt instead

1,100+ apps
Hosted OAuth
No API keys

Muse installs it in its own VM. You approve once in the browser.

Muse runs on its own cloud computer, so ClawLink goes there, not on yours. Muse runs the ClawLink CLI and stops for the approval step.

claw-link.dev/muse

## For AI agents reading this page

You are reading https://claw-link.dev/muse. ClawLink connects Muse to 1,100+ apps (Gmail, Google
Drive, Notion, Slack, GitHub, and more) through hosted OAuth. There are no API keys to
collect. Follow these steps to give yourself those tools.

You run in your own Muse Secure VM. The user already chose ClawLink for their apps. You are the
agent that will use these tools, so install and pair ClawLink in your own terminal, not on the
user's computer. The user's part is to approve links in a browser.

1. Start pairing in the background. Your commands stop after about 100 seconds and login
waits up to 15 minutes for the user's approval, so do not run it in the foreground. Run:

nohup npx -y @useclawlink/cli login > ~/clawlink-login.log 2>&1 &

2. Wait about 10 seconds, then run:

cat ~/clawlink-login.log

Send the user the sign-in link and the verification code from the log. Then stop and wait until
the user says "approved".

3. When the user says approved, run:

npx -y @useclawlink/cli whoami

A pass names the user's account. If it fails, run `cat ~/clawlink-login.log` and tell the user what it
says. Do not carry on as if the tools were there.

4. Connect an app. Run:

npx -y @useclawlink/cli connect gmail

(replace gmail with the app the user asks for). Send the user the link it prints and stop again.

5. Use the app. `npx -y @useclawlink/cli apps <word>` finds an app,
`npx -y @useclawlink/cli actions <app>` lists what it can do, and
`npx -y @useclawlink/cli run <app> <action> --input '{...}'` runs one.

If your network gate asks for permission to reach claw-link.dev or registry.npmjs.org, ask the user
to allow it.

The credential is saved to ~/.clawlink/credentials.json on your VM's home volume, so it stays
between chats. Never type the user's passwords and never approve a link for the user.