> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/using-ndi/ndi-tools/ndi-tools-for-windows/bridge/ndi-bridge-automation.md).

# NDI Bridge automation

An NDI Bridge executable can also be launched using the following command line arguments:

`/verbose`\
Generates extensive log entries in Windows Event Logs, with the event source labeled as "NDI Bridge."

`/host`\
Initiates Bridge in host mode.

`/join`\
Launches Bridge in join mode.

`/local`\
Starts Bridge in local mode.

`/autorun`\
Minimizes Bridge window upon startup.

`/noui`\
Suppresses the display of any user interface elements and prevents the creation of a taskbar icon.

For example, you can use /local /autorun to initiate the Bridge in local mode and minimize it. Similarly, `/local /noui` will start the Bridge in local mode without any user interface. If you use `/autostart` without specifying `/host`, `/join`, or `/local`, the Bridge will start in the last selected mode.

{% hint style="warning" %}
It's important to note that Bridge will not start with these flags if there is a configuration error, such as an invalid IP address for the remote address in the join mode while attempting to auto-start join.
{% endhint %}

If you prefer to configure Bridge using a configuration file, you can find the settings in `AppData\Local\NDI\Application.NDI.Bridge.UI\bridge_settings.json.`

Most setting names are self-explanatory, except for "selected\_tab," which serves as an index field to indicate the last selected tab (mode) the user used (0 = host, 1 = join, 2 = local).

All settings for each mode are present in the same file, so you may need to adjust your logic to target the correct settings for the appropriate mode (e.g., "host\_model," "local\_model," "join\_model").


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ndi.video/all/using-ndi/ndi-tools/ndi-tools-for-windows/bridge/ndi-bridge-automation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.