> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Get Clawdi support

> Choose a verified Clawdi support channel and share diagnostics without exposing private data.

Use email for account, private product, or billing questions. Use a public
GitHub issue for reproducible problems in the open-source CLI or repository
when the report contains no private data.

<CardGroup cols={2}>
  <Card title="Email Clawdi support" icon="mail" href="mailto:support@clawdi.ai">
    Contact [support@clawdi.ai](mailto:support@clawdi.ai) for help that should not be discussed in a
    public issue.
  </Card>

  <Card title="Open a GitHub issue" icon="github" href="https://github.com/Clawdi-AI/clawdi/issues">
    Search or report a public CLI, self-hosting, or open-source product issue.
  </Card>
</CardGroup>

No response-time commitment is stated on this page.

## Check the common signals

Run read-only diagnostics first:

```bash theme={null}
clawdi --version
clawdi auth status
clawdi status
clawdi doctor
clawdi daemon status
```

For a daemon problem, `clawdi daemon doctor --json` creates a broader snapshot
for support handoff. Review and redact its output before attaching it.

Include:

* Your operating system and CPU architecture.
* How the CLI was installed: native installer or npm.
* The exact command that failed and its exit status.
* The smallest reproducible sequence and what you expected.
* Relevant output after applying the redaction checklist below.

## Redact before sending

Remove or replace:

* Access tokens, API keys, cookies, callback URLs, bot tokens, and Vault
  values.
* The contents of `~/.clawdi/auth.json`, `.env` files, credential profiles,
  and daemon token files.
* Email addresses, user IDs, Agent IDs, Project IDs, Session IDs, Channel IDs,
  and private Project names.
* Absolute file paths that reveal usernames or confidential directory names.
* Session text, prompts, tool output, source code, and log lines unrelated to
  the failure.
* URLs with query strings, user information, or non-public endpoints.

<Danger>
  Never run `clawdi read` to collect support diagnostics. It prints a resolved
  Vault value. Do not attach `auth.json` or send a complete sign-in callback
  URL.
</Danger>

Use placeholders such as `<agent-id>`, `<project-id>`, `<email>`, and
`<redacted-path>` while preserving the surrounding error text.

## Choose public or private support

Use GitHub Issues when another user could reproduce the problem without your
account, private content, or production details. Search existing issues first
and include the installed CLI version.

Use email when the problem involves an account, payment, private Agent state,
or diagnostics that cannot be reduced to a safe public reproduction. Even in
email, do not send credentials or secret values.