> For the complete documentation index, see [llms.txt](https://apertus.gitbook.io/vr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apertus.gitbook.io/vr/developers/getting-started/creating-a-plugin.md).

# Creating a plugin

To create a new **plugin** for ApertusVR use *apm* to generate folders and files. In the following example, we create a new plugin called "ipCamera":

```
ApertusVR\utilities\apm>python apm.py create plugin ipCamera
Creating new plugin with the following properties:
  name: ipCamera
  path: ../../plugins/ipCamera/
  class name: ApeIpCameraPlugin
  header name: APE_IPCAMERAPLUGIN_H
  header file path: ../../plugins/ipCamera/ApeIpCameraPlugin.h
  cpp file path: ../../plugins/ipCamera/ApeIpCameraPlugin.cpp
Do you want to continue? [Y/n]
```

If you find everything in order, type '**y**' and press enter to continue.

If you want to add your newly created plugin to plugins/CMakeLists.txt, just type '**y**' when *apm* asks it:

```
Add to plugins/CMakeLists.txt? [Y/n] y
```

{% hint style="warning" %}
In order to see your new plugin in your IDE, don't forget to

1. regenerate the CMake project
2. reload / reopen the generated project file in your IDE.

after editing *CMakeLists.txt* files.
{% 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://apertus.gitbook.io/vr/developers/getting-started/creating-a-plugin.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.