> For the complete documentation index, see [llms.txt](https://docs.kyvvu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyvvu.com/cli-reference/auth.md).

# kyvvu register / login

**What you'll learn:** How to create an account, log in, check your session, and manage authentication.

***

## `kyvvu register`

Create a new Kyvvu account. Prompts for email, display name, and password. On success, creates an API key and stores it locally.

```
Usage: kyvvu register [OPTIONS]

Options:
  --api-url TEXT  Kyvvu API URL (default: https://platform.kyvvu.com)
```

### Example

```bash
$ kyvvu register
Registering at https://platform.kyvvu.com

Email: you@company.com
Display name: Your Name
Password:
Confirm password:

✓ Account created and verified.

Your API key (save this — it will not be shown again):

    KvKey-abc123...

Set it in your environment:

    export KV_API_KEY=KvKey-abc123...

Next steps:
    kyvvu init my-agent
```

### Verification and waitlisting

If the platform is at capacity, your account is created but waitlisted:

```
Kyvvu is in early access — we're actively managing growth.
Your account has been created and you're on the waitlist.
We'll contact you at you@company.com when your account is ready.
```

If your organization requires admin approval, you'll see:

```
Your account at company.com is pending verification.
An admin at your organization needs to approve you before you can
create agents or API keys.
Once they've approved you, run `kyvvu login` to refresh your session.
```

## `kyvvu login`

Log in to an existing account. Stores a JWT locally for dashboard and CLI operations.

```
Usage: kyvvu login [OPTIONS]

Options:
  --api-url TEXT  Kyvvu API URL
```

### Example

```bash
$ kyvvu login
Email: you@company.com
Password:

✓ Logged in as you@company.com
```

If no API key is stored, you'll be offered to create one.

## `kyvvu forgot-password`

Request a password reset email for your account.

```
Usage: kyvvu forgot-password [OPTIONS]

Options:
  --api-url TEXT  Kyvvu API URL
```

## `kyvvu logout`

Clear the JWT session. Your API key in `~/.kyvvu/config.toml` is preserved — agents continue to work.

```bash
$ kyvvu logout
✓ Logged out. Your API key in ~/.kyvvu/config.toml is preserved
(the SDK and agents continue to work).
```

## `kyvvu whoami`

Show current user info, verification status, and endpoint configuration.

```bash
$ kyvvu whoami
Email:         you@company.com
API URL:       https://platform.kyvvu.com
Verification:  ✓ verified
Log location:  stdout
Incidents:     (inherits log location: stdout)
```

## Configuration storage

Auth state is stored in `~/.kyvvu/config.toml`:

* JWT token and expiry (cleared by `kyvvu logout`)
* Default API key (preserved across logins)
* API URL

***

## Next steps

* [kyvvu init](/cli-reference/init.md) — scaffold a new agent project
* [Installation](/getting-started/installation.md) — full setup guide


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kyvvu.com/cli-reference/auth.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.