Command line
50 pages.
| Name | Summary |
|---|---|
| argus | Talos engine: run a game project or scene, and make, check and bake its files. |
| argus material check | Check a material's albedo and roughness against measured real surfaces |
| argus minimap-bake | Draw a scene's roads from above into a PNG for a HUD minimap, and write the ground area it shows (minX, minZ, maxX, maxZ, the bounds Minimap takes) beside it as JSON. |
| argus nav-bake | Bake a scene's navmesh to .navbake bytes (World::bake_navmesh): what a web export writes beside the scene, because the browser build has no Recast to build one |
| argus net-bot | Load-test bots for a netplay relay: each takes a seat and sends a neutral input every tick, simulating nothing. |
| argus net-bridge | Foreign entities into a netplay session: each stdin line {"seat": N, "axes": {...}, "held": [...]} becomes seat N's input from the next unsealed tick, axes as raw floats. |
| argus plugin | List, inspect, add and remove the plugins a project loads, attach their behaviours, and run their scripts |
| argus plugin add | Add a plugin to the project, or change its settings when the project already lists it |
| argus plugin attach | Attach one of a listed plugin's behaviours to an entity of a scene (the project's startup scene unless --scene names another). |
| argus plugin info | What a plugin carries, what it may do and the settings it takes |
| argus plugin key list | The plugins and hosts keys are stored for. |
| argus plugin key set | Store a key for a plugin and a host, from a file that holds it. |
| argus plugin list | The installed plugins, and which of them the project lists |
| argus plugin pack | Write a plugin's package: the files its descriptor names, in a new folder, as it is published and installed |
| argus plugin remove | Remove a plugin from the project. |
| argus plugin run | Run one of a plugin's scripts on the Node the engine's tools use, from the working directory, with every argument after the script's name (--help included). |
| argus project init | Make a new project from a template |
| argus project migrate | Report, apply or undo upgrading a project to this engine |
| argus relay | Run a rollback netplay relay (docs/NETCODE.md, "Relay"): it seats peers, keeps the clock and sends every tick's inputs to everyone. |
| argus replay diff | Play recordings A and B (two peers, or one thread count and another) and report where they part: the tick, system, entity and field, with both values |
| argus run | Load a project or a scene, run it, render a PNG, and optionally keep serving and watching. |
| argus scene instance | Turn groups of identical static mesh entities into instanced meshes |
| argus validate | Validate a scene against the contract and report every violation |
| argus vfx bake | |
| argus vfx baseline | |
| argus vfx check | |
| argus vfx clip | |
| argus vfx diff | |
| argus vfx report | |
| argus vfx sheet | |
| argus-agent | The Talos agent interface (MCP over stdio) |
| argus-agent foliage-preset | Plant a scene's terrain over an area with a foliage preset: the foliage.preset tool, run once. |
| argus-agent mcp | Connect AI tools: mcp install --for <tool> |
| argus-agent mcp install | Connect an AI tool to a project in one step: write this agent server into the tool's own MCP config, in its own shape (docs/CONNECT-ANY-AI.md). |
| argus-agent replay | Play a recorded assistant session again against a project: the same engine calls that landed a change, as an agent of the same name, with its recorded narration printed as stream-json at its recorded times (crate::replay). |
| argus-agent self-info | Print the Talos export payload appended to this executable, as the launcher's --info does. |
| argus-agent setup | Connect a person's own AI client to a project in one step: write the project's .mcp.json (what Claude Code reads) with this argus-agent as the argus server, keeping any other servers there. |
| argus-agent tools | Print the tool list as tools/list returns it, and stop. |
| argus-hub | The Talos Hub: installs, updates and opens Talos engines |
argus licence
Since next
usage: licence status [--json] | import <file> | request [--label <text>] [--out <file>] | inspect <file> [--json] | audit <file> issuer: keygen --out <file> | issue --key <pem> --spec <json> [--seat <request>]...
Usage
argus licence [ARGS]...Example
argus licence [ARGS]...argus login
Since next
Sign in for engine and sample downloads: runs the sign-in of the launcher that installed this engine, which prints a code to enter in a browser
Usage
argus loginExample
argus loginargus logout
Since next
Sign out on this computer: runs the sign-out of the launcher that installed this engine
Usage
argus logoutExample
argus logoutargus material
Since next
argus material: the one subcommand is check
Usage
argus material <COMMAND>Commands
| Command | Description |
|---|---|
check | Check a material's albedo and roughness against measured real surfaces |
Example
argus material <COMMAND>argus plugin key
Since next
The keys stored on this machine for the hosts plugins fetch from (docs/PLUGINS.md, "Keys")
Usage
argus plugin key <COMMAND>Commands
| Command | Description |
|---|---|
set | Store a key for a plugin and a host, from a file that holds it. The key is kept readable by you only, and is sent to that host alone, where the plugin's addresses ask for it |
list | The plugins and hosts keys are stored for. Never the keys |
remove | Remove the key stored for a plugin and a host |
Example
argus plugin key <COMMAND>argus plugin key remove
Since next
Remove the key stored for a plugin and a host
Usage
argus plugin key remove <PLUGIN> <HOST>Arguments
| Argument | Description |
|---|---|
<PLUGIN> | |
<HOST> |
Example
argus plugin key remove <PLUGIN> <HOST>argus project
Since next
argus project: the subcommands are init <name> and migrate --dry-run <project>.
Usage
argus project <COMMAND>Commands
| Command | Description |
|---|---|
init | Make a new project from a template |
migrate | Report, apply or undo upgrading a project to this engine |
Example
argus project <COMMAND>argus replay
Since next
Check a --save-replay file against its scene, or two recordings against each other, by the per-system state hashes it carries (the desync finder): where the simulation parts, as JSON on stdout.
Usage
argus replay <COMMAND>Commands
| Command | Description |
|---|---|
verify | Play FILE on the scene and check each hash line it holds: the first tick window and system where the playback parts from the recording, or "ok": true |
diff | Play recordings A and B (two peers, or one thread count and another) and report where they part: the tick, system, entity and field, with both values |
Example
argus replay <COMMAND>argus replay verify
Since next
Play FILE on the scene and check each hash line it holds: the first tick window and system where the playback parts from the recording, or "ok": true
Usage
argus replay verify <PROJECT_OR_SCENE> <FILE>Arguments
| Argument | Description |
|---|---|
<PROJECT_OR_SCENE> | |
<FILE> |
Example
argus replay verify <PROJECT_OR_SCENE> <FILE>argus scene
Since next
argus scene: the one subcommand is instance
Usage
argus scene <COMMAND>Commands
| Command | Description |
|---|---|
instance | Turn groups of identical static mesh entities into instanced meshes |
Example
argus scene <COMMAND>argus vfx
Since next
argus vfx: the subcommands are report, sheet, clip, diff, baseline, bake and check; each takes --help
Usage
argus vfx <COMMAND>Commands
Example
argus vfx <COMMAND>