# Set yourself up with cmdhub (Codex)

You are **Codex**. 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
Codex-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**, so you are on the happy path: you can run the installer,
  install adapters, trigger logins, and verify — as long as your shell is on the **same
  computer as the user's browser** (see "Where does your shell run?" in the generic doc).
  Codex often runs in a sandbox or container; if so, prefer installing on the host machine
  and do the browser login there, or the localhost login will not reach the user's browser.
- **Install a skill file so you stay good at cmdhub.** After setup, offer to add cmdhub
  guidance to `AGENTS.md` in the project root. Fetch `cmdhub.run/agent/codex/skill` and
  write it to `./AGENTS.md` (or merge it in). 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 — 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.