📦nexus tap
Audience: Nexus CLI users and integrators.
Command: nexus tap.
Generated from: Nexus CLI v2.2.0 Linux x86_64 release executable; its archive SHA-256 matched HTTPS release metadata and the extracted binary reported nexus-cli 2.2.0 (generated help inventory preserved below).
Here, Talus Agent Package (TAP) names the package and Agent compatibility surface; the backticked tap names the CLI namespace.
This page is the complete help tree for nexus tap. Global output flags can appear after the family or nested subcommand.
The TAP family remains the compatibility surface for package and Agent operations. Tool authorization is exposed by nexus execution authorize, and timeout/refund identifies the exact invocation_id; do not use a cashier-wide payment candidate from historical TAP help as a substitute. --invocation-id is optional only when the selected command proves one unique candidate—pass the exact ID whenever a lock is known. The effective walk timeout includes the five-second leader-evaluation buffer, so its permissionless recovery boundary is twice the effective value rather than twice the displayed base timeout. See Invocation policy and settlement model.
Prepare and operate standard TAP skills
Usage: nexus tap [OPTIONS] <COMMAND>
Commands:
scaffold Scaffold a TAP package and DAG-backed skill config.
validate-skill Validate a TAP skill config and local TAP package metadata.
publish-skill Publish a TAP package, DAG, and publish artifact.
create-skill-artifact Create a TAP skill publish artifact from explicit inputs and fetched DAG
data.
create-agent Create a standard Talus agent.
register-skill Register a TAP skill from a publish artifact.
update-skill Update an existing TAP skill from a publish artifact.
agent Manage locally saved Talus agent aliases.
vault Inspect Talus agent payment vaults.
payments Inspect standard TAP execution payments and history.
execution Settle or abort active TAP executions.
registry Inspect the agent registry.
default-agent Inspect the standard TAP default agent metadata.
bind Create a Talus agent and register its first skill atomically.
requirements Fetch live skill requirements from the agent registry.
dry-run Validate TAP skill config, DAG, and package metadata (the generated CLI help overstates this as input dry-run).
help Print this message or the help of the given subcommand(s)
Options:
-h, --help Print help
Output:
--json Emit machine readable JSON
-v, --verbose... Increase diagnostic detail
-q, --quiet... Show errors onlynexus tap test
Run a TAP Move unit-test suite in a local Sui VM with Nexus bytecode published in the selected environment. The command resolves MVR packages, reads Nexus modules from Sui, adds test-only module extensions in memory, and verifies the result before execution. It does not require a wallet, private key, gas, or Nexus source and does not publish, register, bind, schedule, settle, or move assets.
Use --list or a fully qualified test-name filter to isolate the first concrete failure, then rerun the same package without a filter as the final VM gate. CLI-generated TAP test modules use braced module bodies so the scaffolded tests compile with nexus tap test. Keep this local published-bytecode evidence separate from pure Move tests, structural DAG/TAP validation, and live network execution.
nexus tap scaffold
nexus tap validate-skill
nexus tap publish-skill
nexus tap create-skill-artifact
nexus tap create-agent
nexus tap register-skill
nexus tap update-skill
nexus tap agent
nexus tap agent save
nexus tap agent list
nexus tap agent remove
nexus tap vault
nexus tap vault balance
nexus tap vault balance is a read-only query and does not require Agent ownership or a private key.
nexus tap vault deposit
nexus tap payments
nexus tap payments show
nexus tap payments wait
nexus tap payments refill
The refill transaction also requests every active walk whose payment is ready. It does not settle a committed result already retained in PendingSettlement; after the refill, run the eligible nexus tap execution settle transition for that walk and verify the committed result and insufficient-payment marker clear.
nexus tap execution
nexus tap execution resolve-expired-walk
nexus tap execution settle
This command settles the eligible committed result and then requests every active walk whose payment is ready in the same transaction. After success, verify both the cleared result/lock state and the request events for eligible active walks.
nexus tap execution abort
nexus tap registry
nexus tap registry show
nexus tap default-agent
nexus tap default-agent show
nexus tap bind
nexus tap requirements
nexus tap requirements reads public skill requirements for the supplied Agent ID and skill index; it does not require Agent ownership or a private key.
nexus tap dry-run metadata validation
Last updated

