> For the complete documentation index, see [llms.txt](https://www.projectpanoptes.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.projectpanoptes.org/build/software/pocs-command-line.md).

# POCS Command Line

## Overview

The `pocs` command provides a convenient way to work with your PANOPTES unit and is designed to provide a simple interface to nearly all hardware and software components for your unit.

The `pocs` command has a series of subcommands that do all the work. These subcommands might also contain subcommands (e.g. `pocs config get`).

Every subcommand has a `--help` option that explains what it is used for and how to use it. The following pages give more details on the commands.

{% hint style="info" %}
Many of the subcommands require the proper [Services](/build/software/appendix/services.md)to be running although you can often do a `restart` subcommand for the given service, e.g. `pocs config restart` to start or restart the config server.
{% 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://www.projectpanoptes.org/build/software/pocs-command-line.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.