# Set yourself up with cmdhub (Cursor)

You are an agent in **Cursor**. Your user wants you to install your own tools with cmdhub
so you can do real cross-tool work for them (email, calendar, tasks, and more) on their
machine.

The full step-by-step flow is at **cmdhub.run/agent** — read it. This page only covers the
Cursor-specific details; everything else (the trust preview, starter bundle, browser login,
verification, teach-back) is in the generic doc.

## What's specific to you

- **You can run shell commands** in Cursor's integrated terminal, so you are on the happy
  path: you can run the installer, install adapters, trigger logins, and verify — the
  terminal runs on the user's own machine, so the localhost browser login works.
- **Install a skill file so you stay good at cmdhub.** After setup, offer to add a cmdhub
  rule. Fetch `cmdhub.run/agent/cursor/skill` and write it to `./.cursor/rules/cmdhub.mdc`.
  It covers the grammar, `cmdhub get`, `cmdhub auth login`, the `m1`/`f1` short refs, and
  `agent adapt` for composing tools.
- **How the user "pastes"**: they type a request to you in chat — the line
  `Set yourself up from cmdhub.run/agent` is the trigger.

## The short version

```bash
curl -fsSL https://cmdhub.run/install.sh | bash
cmdhub get gmail gcal mstodo
cmdhub auth login
cmdhub doctor
```

Preview what this does for the user **before** running it, connect only the accounts they
ask for, then read back what's installed and connected. See cmdhub.run/agent for the full
flow and the "what this will / will not do" block.