---
title: "Sign in"
description: "arkor login, logout, whoami."
---

You can use Arkor anonymously without ever signing in: `arkor dev` bootstraps an anonymous identity for you on first launch. To tie work to your Arkor Cloud account instead, use `arkor login`.

## Sign in

<CodeGroup labels={["pnpm","npm","yarn","yarn-berry","bun"]}>

```bash
pnpm arkor login
```

```bash
npm arkor login
```

```bash
yarn arkor login
```

```bash
yarn run arkor login
```

```bash
bun arkor login
```

</CodeGroup>

The CLI prompts you to pick **OAuth (browser)** or **Anonymous**. Pick OAuth to sign in to your Arkor Cloud account; the CLI opens a browser, you authorize, and credentials land in `~/.arkor/credentials.json`.

To skip the picker:

<CodeGroup labels={["pnpm","npm","yarn","yarn-berry","bun"]}>

```bash
pnpm arkor login --oauth
```

```bash
npm arkor login --oauth
```

```bash
yarn arkor login --oauth
```

```bash
yarn run arkor login --oauth
```

```bash
bun arkor login --oauth
```

</CodeGroup>

In CI, use `--anonymous` instead; OAuth needs a browser.

## Check who you are

<CodeGroup labels={["pnpm","npm","yarn","yarn-berry","bun"]}>

```bash
pnpm arkor whoami
```

```bash
npm arkor whoami
```

```bash
yarn arkor whoami
```

```bash
yarn run arkor whoami
```

```bash
bun arkor whoami
```

</CodeGroup>

Prints the current identity and the orgs you can reach.

## Sign out

`arkor logout` asks before deleting `~/.arkor/credentials.json`, and the confirmation defaults to **No**. For anonymous credentials, deleting the file permanently loses access to that anonymous identity unless you backed it up yourself; the next `arkor dev` will bootstrap a fresh anonymous identity. OAuth users can run `arkor login --oauth` again.

## Reference

For the full picker / flag matrix, the anonymous-vs-OAuth tradeoffs, token expiry behavior, and every error message, see the [auth reference](/docs/framework/cli/auth).
