# argus-agent foliage-preset

> Talos next · Since next

Plant a scene's terrain over an area with a foliage preset: the `foliage.preset` tool, run once.

## Usage

```sh
argus-agent foliage-preset [OPTIONS] --scene <SCENE> --preset <PRESET> --area <AREA>
```

## Options

| Flag | Value | Default | Allowed values | Description |
|---|---|---|---|---|
| `--project` | `<PROJECT>` |  |  | The project folder (or its project file). The current folder when absent |
| `--scene` | `<SCENE>` |  |  | The scene, relative to the project |
| `--preset` | `<PRESET>` |  |  | The preset (listed below) |
| `--area` | `<AREA>` |  |  | minX,minZ,maxX,maxZ in scene metres |
| `--seed` | `<SEED>` |  |  | The same inputs give the same bytes. Default 1 |
| `--dry-run` |  |  |  | Cook and answer; write nothing |
| `--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 foliage-preset --scene <SCENE> --preset <PRESET> --area <AREA>
```