Worlds quickstart

You’ll generate a small manifest, wait for it, sample a handful of trajectories against it, and open the replay in the web app. A few minutes end-to-end.

Prerequisites

• dn installed and authenticated. See Getting started.
• A workspace. A manifest is created under your default project unless you pass one.

Export the scope you’re working in so the rest of the commands stay short:

export DREADNODE_ORGANIZATION=<your-org>
export DREADNODE_WORKSPACE=<your-workspace>

1. Generate a manifest

Submit a small manifest job. The small preset is the quickest way to get a working graph.

dn worlds manifest-create --preset small --seed 7 --name quickstart --json

The command returns a job record, not the finished manifest. Save the job ID from the output, then wait on it:

dn worlds job-wait <job-id>

job-wait polls until the job reaches completed, failed, or cancelled and exits non-zero on anything but completed.

List the resulting manifest and grab its ID:

dn worlds manifest-list

Note

Presets (small, medium, large, enterprise) are opaque to the control plane — the Worlds backend owns the topology. To set explicit sizes, use --num-users, --num-hosts, and --domain instead of --preset.

2. Inspect what was generated

Open the manifest in the web app under Worlds → Manifests. The Overview tab shows the command catalog — the actions the sampler can take against this environment. The Graph Explorer tab renders hosts, principals, and edges with search, filtering, and subgraph focus.

From the CLI:

dn worlds principals <manifest-id> --query alice
dn worlds host <manifest-id> <host-id>
dn worlds commands <manifest-id>

3. Sample a trajectory

Run the kali sampler against the manifest. kali is a deterministic, Kali-flavored sampler — fast, no agent required.

dn worlds trajectory-create \
  --manifest-id <manifest-id> \
  --goal "Domain Admins" \
  --count 4 \
  --strategy smart-random \
  --mode kali \
  --json

Wait on the trajectory job and list the results:

dn worlds job-wait <job-id>
dn worlds trajectory-list --manifest-id <manifest-id>

Each trajectory record carries success, a termination_reason, the goal, and a step count.

4. Replay the trajectory

In the web app, open Worlds → Trajectories, click a completed trajectory, and select the Steps tab. The replay inspector shows each step’s command, output, target, and state transitions with next/previous navigation. See Replay & artifacts for what each field means.

Next

• Swap --mode kali for agent mode to run your own capability against the environment.
• Feed the trajectory dataset into SFT or RL training.
• Customize what’s generated with explicit --num-users, --num-hosts, and --domain in Manifests.