# argus-agent self-info

> Talos next · Since next

Print the Talos export payload appended to this executable, as the launcher's `--info` does.

A composed export is the launcher template with a payload after it; when this binary *is* that template, this is how it proves the composition by reading its own bytes back. That is what `tests/exit_gate.rs` runs for the exit gate's last step.

## Usage

```sh
argus-agent self-info [OPTIONS]
```

## Options

| Flag | Value | Default | Allowed values | Description |
|---|---|---|---|---|
| `--tool-names` | `<TOOL_NAMES>` | `dotted` |  | How `tools/list` spells the names. `dotted` is the interface's own (`scene.read`); `underscore` is for a client that namespaces a tool into an identifier and will not take a dot (`scene__read`); `hyphen` for one that also takes no `__` inside a tool's name (Grok: `scene-read`). `tools/call` takes any spelling whichever this is |
| `--toolsets` | `<TOOLSETS>` | `""` |  | Toolsets to list from the start, beyond the core: comma-separated names, or `all`. For a client that does not refetch `tools/list` when told it changed; one that does can call `tools.enable` instead and pay for the tools only when it needs them. ARGUS_AGENT_TOOLSETS when absent, so a harness can set it for every server it starts |

## Example

```sh
argus-agent self-info
```