> For the complete documentation index, see [llms.txt](https://docs.constellationnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.constellationnetwork.io/run-a-node/legacy/the-nodectl-utility.md).

# The nodectl utility

{% hint style="warning" %}
**⚠️ DEPRECATED:** The `nodectl` utility is no longer supported. This guide is archived for reference only.

New and existing node operators should use the **Node Pilot** utility. **Click here to view the Node Pilot Setup Guide**
{% endhint %}

This section explains how to use the **Constellation Network Command Line Interface** (CLI) utility, which provides a **simplified** way to run a **node** without requiring technical expertise or in-depth knowledge of the **Tessellation Protocol’s architecture and operation**.

## **What is nodectl?**

Pronounced *node control*, *node-c-t-l*, or *node-cuttle.*

**nodectl** is a command-line utility designed to simplify the deployment and management of Constellation Network Validator nodes.

It eliminates the need for deep technical knowledge of the Tessellation Protocol, allowing both technical and non-technical users to run and maintain a Validator node on the Hypergraph and/or metagraph networks.

The utility is packed with powerful features that abstract away the complexities of node management.


---

# 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.constellationnetwork.io/run-a-node/legacy/the-nodectl-utility.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.