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

# Grok Build

> Asymptote support details for Grok Build endpoint telemetry

## Runtime Overview

Asymptote supports Grok Build through native hook payloads sent to `beacon-hooks`.

## Prerequisites

Before enabling Grok Build hooks, make sure:

* Grok Build is installed for the user or available in the project where hooks will run.
* `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
* Asymptote hooks are installed with `beacon endpoint hooks install --harness grok`.
* Project-level hooks are trusted with `/hooks-trust` in Grok before you expect them to execute.
* Grok is restarted after hook install or removal so new sessions load the updated hook file.

## Collection path

Grok Build invokes Asymptote's hook adapter from Asymptote's owned hook file. The adapter writes normalized endpoint events to the configured runtime JSONL log.

## Discovery and status

Asymptote checks for its managed Grok hook file at `~/.grok/hooks/beacon-endpoint.json` for user-level installs or `./.grok/hooks/beacon-endpoint.json` for project-level installs.

Use `beacon endpoint hooks status --harness grok` to inspect Grok Build hook status.

## Install or configuration support

`beacon endpoint install` prepares shared endpoint config and runtime log paths. Install Grok Build hooks separately:

```bash title="Install runtime hooks" theme={null}
beacon endpoint hooks install --harness grok
```

For project-level hooks, run:

```bash title="Install project-level hooks" theme={null}
beacon endpoint hooks install --harness grok --level project
```

## Telemetry coverage

| Area                              | Support                                                                                                                                     |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Prompt telemetry                  | Supported through `UserPromptSubmit` hooks                                                                                                  |
| Command, tool, and file telemetry | Supported for session, prompt, pre-tool, post-tool, failed tool, stop, session-end, command, and file telemetry where Grok exposes payloads |
| Local JSONL and dashboard         | Supported                                                                                                                                   |
| MDM deployment                    | Supported for the endpoint agent; Grok hooks are installed separately in the logged-in user's context or project context                    |

## Deployment notes

Project-level Grok Build hooks require `/hooks-trust` in Grok before they execute. Grok tool failures normalize to `tool.failed` with high severity.

Restart Grok after installing or removing hooks so new sessions pick up the updated hook configuration.

## Related

<Columns cols={2}>
  <Card title="Supported agent harnesses" icon="list-check" href="/runtimes">
    Return to the runtime support overview.
  </Card>

  <Card title="Hooks" icon="plug" href="/cli/hooks">
    Install, inspect, and uninstall runtime hook integrations.
  </Card>
</Columns>