> For the complete documentation index, see [llms.txt](https://docs.remote.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remote.it/software/device-package.md).

# Device Package

The Device Package installs the Remote.It target agent — the smallest-footprint way to make a headless or embedded Linux device reachable for inbound connections.

## Device Package

The Device Package installs the remote.it **target agent** — the lowest-level component required for connections. It's the smallest way to make a device reachable through remote.it.

**With this package installed, other devices and users can connect&#x20;*****to*****&#x20;this device, but this device cannot initiate connections&#x20;*****to*****&#x20;others.** If this machine also needs to initiate connections, install one of these instead:

* **CLI** — if connections will be made from scripts or the command line.
* **Desktop Application** — a straightforward UI for making connections and configuring devices.

Use the Device Package when you care about disk space and process footprint — for example on headless or embedded Linux devices such as Raspberry Pi, OpenWrt routers, IoT hardware, and cloud VMs.


---

# 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.remote.it/software/device-package.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.
