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

# CLI Quick start

## 1. Get your organization activated

Every Mithrl organization starts inactive until Mithrl grants it access to a knowledge-graph build — a one-time step per organization, not per user. Contact us at <support@mithrl.com> with your company name to get your organization activated.

## 2. Get added as a user

Once your organization is active, an existing admin/manager on your organization's account needs to add you as a user. Signing in is per-user, so `mithrl login` (step 5) won't work until someone with access to your organization has added you.

## 3. Get the Mithrl-1 CLI

Download the `mithrl` binary for your platform from [`aviai/public-releases`](https://github.com/aviai/public-releases/releases) — see [Installation](/getting-started/installation.md) for platform-specific steps. Confirm it's working:

```bash
./mithrl --version
```

## 4. (Optional) Point the CLI at production

```bash
./mithrl api default
```

You can skip this — `mithrl` already talks to production by default. Run this only if you've pointed the CLI somewhere else before (e.g. while testing against a different deployment) and need to switch back. This is persisted locally, so it's a one-time step, not something you repeat every session; check what's currently configured with `mithrl api show`.

## 5. Log in

```bash
./mithrl login
```

This opens your browser for sign-in. Use the account added in step 2.

## 6. Run a query

```bash
./mithrl search BRCA1
```

This resolves `BRCA1` to its knowledge-graph node(s) and prints a compact result. From here, see the [CLI reference](/docs/cli.md) for the rest of the command surface, or [Running and managing Inference](/guides/workflow-cli.md) for triggering analysis workflows.