> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/integrations/input-sources/developer-insights/code-interactions.md).

# Code Interactions

When key commands are used to install a package manager or execute software, they provide a strong signal of developer intent, indicating active engagement and interest.

Reo.Dev enables you to track these specific command interactions, giving you valuable insights into which accounts are actively using and engaging with your product.

To configure tracking for code commands:

1. Go to **Integrations** under Settings

<figure><img src="/files/8Uj78KLcmCoQ4pyyfl2i" alt=""><figcaption></figcaption></figure>

2. Click on **Configure** within the Code Interactions Card

<figure><img src="/files/Njvvga4BigfgNWsaQDo9" alt=""><figcaption></figcaption></figure>

3. **Add the Key Commands** you want to track.

Note:

* Before adding key commands, please ensure your documentation is set-up. Here’s a quick guide.
* Copy the complete command from the code block including the comments, if any

<figure><img src="/files/7uRPTWFdDJUGOsXpUQb3" alt=""><figcaption></figcaption></figure>

4. Add a **Command label** for every code command

<figure><img src="/files/ImIhZlUC4FpnIkB1TMTn" alt=""><figcaption></figcaption></figure>

Once added, you can create a Segment to track accounts/developers/buyers who executed specific commands. The command labels will appear under the ‘**Key Commands’** filter while creating segments.

5. Once done, click on **‘Save’** to start tracking code commands.

<figure><img src="/files/XFDtqjdCZxGhyKIkm6EI" alt=""><figcaption></figcaption></figure>

#### **Content Security Policy (CSP) Considerations**

If your website uses a strict Content Security Policy (CSP), you may need to update it to allow our script to load and execute correctly. Please ensure the following directives are updated to include our domains:

**Required CSP Directives**

Copy

```
script-srchttps://static.reo.dev;connect-srchttps://api.reo.dev;
```


---

# 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.reo.dev/integrations/input-sources/developer-insights/code-interactions.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.