> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/wildcards/local-environment-related-wildcards-6/local-registry.md).

# Local Registry ?

This wildcard retrieves the value from a specified Windows registry entry and is ***exclusively applicable to Windows clients.***

* {local.registry.?}
* For the following input (?) --> Registry hive
* The output is going to be --> Registry key value

#### Example:

The following registry key in Windows need to be rewritten to a forward slash notation:

* Computer\HKEY\_CURRENT\_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\AppData
* currentuser/Software/Microsoft/Windows/CurrentVersion/Explorer/Shell Folders/AppData

<figure><img src="/files/vmxi548LtsOjOIPAUWe3" alt=""><figcaption><p>Windows registry key-value</p></figcaption></figure>

* Input: {local.registry.currentuser/Software/Microsoft/Windows/CurrentVersion/Explorer/Shell Folders/AppData}
* Output: C:\Users\\*username*\AppData\Roaming

{% hint style="info" %}
Registry keys should start like this:

* classesroot for HKEY\_CLASSES\_ROOT
* currentuser for HKEY\_CURRENT\_USER
* localmachine for HKEY\_LOCAL\_MACHINE
* users for HKEY\_USERS
* currentconfig for HKEY\_CURRENT\_CONFIG
  {% endhint %}

{% hint style="warning" %}
Registry paths should use / (forward slashes) instead of the usual \ (back slash)!\
\
Using \ will result in a fail with the error "1>0"
{% endhint %}


---

# 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.helmut.de/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/wildcards/local-environment-related-wildcards-6/local-registry.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.