Account
You can run agents locally without an account. You need one to publish to the registry.
When do I need an account?#
Rush splits cleanly into “things you can do alone” and “things that touch the registry or Rush Cloud.”
| Local (no account) | Account required |
|---|---|
rush run ./my-agent | rush login |
rush serve ./my-agent | rush whoami |
rush list | rush publish ./my-agent |
rush install acme/foo | rush deploy prix/rabbit-hole |
rush build ./my-agent | rush unpublish acme/foo |
Installing agents from the registry is free and anonymous. Publishing to the registry and deploying to Rush Cloud require an authenticated developer account so ownership can be attributed and signing enforced.
Sign in#
rush loginThis opens your browser, takes you through Google OAuth, and writes tokens back to ~/.rush/user.yaml (mode 0600). No token ever hits your shell history.
Confirm it worked:
rush whoami
# -> [email protected] (developer handle: your-handle)rush login writes tokens to ~/.rush/user.yaml. Subsequent commands (publish, dev enable, etc.) read from the same file — sign in once, everything else just works.
Your developer handle#
Every published agent has a developer field in agent.yaml. That field has to match the handle tied to your account.
name: my-researcher
developer: your-handle # must match rush whoamiYour handle is set the first time you sign in. You can see it via rush whoami.
Organizations (optional)#
Teams at the same company can share an organization. The first person from a domain creates it; others join with an invite code.
| Situation | What happens |
|---|---|
| First signup from acme.com | Prompted to create an Acme organization |
| Second signup from acme.com | Prompted for the org's invite code |
| Signup from gmail.com | Personal account — no org |
Orgs are optional. Solo developers never need to think about this. SSO is available for enterprise orgs on request.
Sign out#
rush logoutClears ~/.rush/user.yaml. You can still run agents; you just can't publish until you sign in again.