> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/reference/cli.md).

# Nexus CLI reference

**Audience:** Nexus CLI users and integrators.

**Command:** Nexus CLI reference.

**Generated from:** Nexus CLI `v2.1.0` release executable at commit `45d397aafcfbeeeaf5032d5fb9fa5d99b3f36205` (generated inventory preserved below).

This landing page follows the documented CLI command tree, including exact Invocation authorization and ToolCashier policy/collection families. Verify the selected binary’s `nexus --version`, family `--help` output, configured network objects, and transaction effects before executing a command; do not substitute a ToolCashier ID or FQN for an exact Invocation identity.

> **Before executing a command:** Require matching `--help`, generated bindings, network objects, package IDs, and transaction effects.

The operational command families are:

Talus Agent Package (TAP) names the package and Agent compatibility surface; the backticked `tap` names the CLI namespace.

* [`nexus tool`](/talus-docs-v2.1.0/reference/cli/tool.md) — create, validate, register, inspect, configure, and retire Tools.
* [`nexus conf`](/talus-docs-v2.1.0/reference/cli/conf.md) — manage local Nexus configuration.
* [`nexus dag`](/talus-docs-v2.1.0/reference/cli/dag.md) — inspect, validate, and publish DAGs. Execution moved to the Task/Execution model.
* [`nexus task`](/talus-docs-v2.1.0/reference/cli/task.md) — create, schedule, inspect, pause, resume, cancel, refill, close, and operate occurrences.
* [`nexus execution`](/talus-docs-v2.1.0/reference/cli/execution.md) — replay and follow workflow Execution history.
* [`nexus gas`](/talus-docs-v2.1.0/reference/cli/gas.md) — manage Sui transaction gas.
* [`nexus network`](/talus-docs-v2.1.0/reference/cli/network.md) — configure, collect, swap, and withdraw network priority fees.
* [`nexus tap`](/talus-docs-v2.1.0/reference/cli/tap.md) — scaffold/publish/bind/update skills and inspect or recover TAP execution/payment state.
* `nexus completion` — generate completion scripts for supported shells.

The retired `nexus scheduler` family and retired `nexus dag execute`/execution-inspection commands are not part of the documented CLI. Use `nexus task` for scheduling and occurrence recovery, and `nexus execution` for runtime inspection.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talus.network/talus-docs-v2.1.0/reference/cli.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 `build a script that syncs our docs to a CMS` 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.