Configuration

Everything you can tune in Trailblaze, in one place: which configuration surface to use for what, which one wins when two disagree, and whether a change takes effect immediately or needs a daemon restart.

Related pages:

• LLM Configuration — providers, models, API keys, and the llm: YAML schema.
• CLI reference — the generated command reference, including the authoritative trailblaze config key table.
• Trailmaps and Project Layout — per-target workspace configuration (trails/config/).

The configuration surfaces

Surface	Use it for	Where it lives
Persistent config keys — trailblaze config <key> <value>	Your personal defaults (LLM, drivers, screenshot format, experimental toggles)	trailblaze-settings.json (location below)
Environment variables — TRAILBLAZE_*	One-off overrides, CI, and kill-switches	Process environment
User YAML config	Personal LLM providers, models, and credentials	~/.trailblaze/trailblaze.yaml
Workspace config	Team defaults committed to the repo (LLM config, targets, trailmaps)	trailblaze-config/trailblaze.yaml (or the legacy trails/config/trailblaze.yaml)
JVM system properties — -D…	Daemon-process tuning (rarely needed)	Daemon launch command
Android instrumentation arguments	On-device SDK behavior in instrumented test runs	am instrument args

Where settings are persisted

Settings live in trailblaze-settings.json, but which copy applies depends on how you run:

• Installed CLI (e.g. Homebrew): the launcher pins one settings directory for both the CLI and the daemon (-Dtrailblaze.appdata.dir), so there is a single file.
• Daemon: $TRAILBLAZE_HOME/trailblaze-settings.json, default ~/.trailblaze/trailblaze-settings.json. ~/.trailblaze is also the daemon’s state directory (logs, TLS keystore).
• Standalone trailblaze config inside a git repository (no launcher pin): falls back to <repo root>/.trailblaze/trailblaze-settings.json, so a source checkout doesn’t mutate your machine-global settings. Note this repo-local file does not drive an already-running daemon — daemon-backed runs read the daemon’s own file above.

Run trailblaze config with no arguments to print every key with its current value. A few persisted settings — the logs directory and the daemon ports — have no trailblaze config key at all; see Settings keys with no trailblaze config key.

Precedence

Configuration does not have one total ordering because different settings use different subsets of the surfaces. The important resolution chains are:

• LLM providers and models: environment/per-run override → workspace trailblaze.yaml → user ~/.trailblaze/trailblaze.yaml → built-in definitions.
• Target: explicit per-run selection → persisted non-default trailblaze config target selection → workspace defaults.target → built-in target. A persisted selection of the neutral default target is treated as unset so it cannot mask the workspace default.
• Maximum LLM calls: CLI flag → TRAILBLAZE_MAX_LLM_CALLS → workspace defaults.max-llm-calls → persisted config key → agent default.
• Self-heal: CLI flag → TRAILBLAZE_SELF_HEAL_ENABLED → persisted config key → false.

Two more deliberate exceptions:

• Experimental toggles (stream-screenshots, ios-baguette-video, disable-animations, turbo): the env var can only turn the feature on. An explicit falsey env value does not override a true persisted config — unset the config key to turn the feature off.
• Daemon port: a serverPort persisted in trailblaze-settings.json outranks TRAILBLAZE_PORT unless the persisted value equals the default (52525, treated as “not set”). If an env override seems ignored, check for a persisted non-default port — see serverPort / serverHttpsPort.
• Daemon ports must stay outside 52530-59529. That range is where Trailblaze allocates per-device ports, and a device’s port is also a host port: the host bridges to the device with adb forward tcp:<port> tcp:<port>, which takes an already-bound host port without reporting an error. A daemon listening in that range can therefore be silently disconnected the moment a device whose id hashes to its port connects. The daemon refuses to start on such a port rather than fail that way later, so keep TRAILBLAZE_PORT outside 52530-59529 when running parallel daemons. The HTTPS port derives as +1 and is checked too, so 52529 is refused as well. Above the range is worse, not better: it is further into the OS ephemeral range (32768-60999 on Linux, 49152+ on macOS), where an unrelated outbound connection can be assigned the port as its source and the bind then fails outright. Better still is a port below the ephemeral range altogether — 31900, the example the CLI’s own help uses. The default 52525 sits inside that range, so this is a pre-existing risk rather than one parallel daemons introduce, but a port you are choosing fresh is free to avoid it. The Settings UI refuses an in-range port too, and PUT /trailrunner/api/settings returns 200 while silently dropping the field, so a saved value can’t brick the next launch.

When changes take effect

Each variable below is marked with when its value is applied:

Marker	Meaning
launch	Read once when the consuming process starts. Restart a running daemon if it consumes this variable.
command	Read by each CLI process, so a one-shot VAR=x trailblaze … works.
session	Resolved at session/run start from the consuming process’s environment and current persisted config. It never changes mid-session.
subprocess	Read when a tool subprocess imports its SDK or module. Set it before that subprocess starts.
use	Consulted on each use inside the consuming process rather than cached by Trailblaze. A running process still cannot inherit environment changes made later in its parent shell.

Environment variables belong to a process environment: changing export VAR=... in your shell never rewrites an already-running daemon’s environment. When a row is marked session or use, restart the daemon if you changed that variable outside the daemon process.

Persistent config keys (trailblaze config)

The full generated table (valid values, defaults) lives in the CLI reference. Grouped summary:

Group	Keys
LLM	llm (shorthand provider/model), llm-provider, llm-model — see LLM Configuration
Devices & drivers	device, android-driver, ios-driver, web-headless, target
Agent & runs	agent, mode, max-llm-calls, self-heal, require-steps
Screenshots	screenshot-format, screenshot-max-dimensions, screenshot-quality, annotated-screenshots
Capture	capture-video (true/false, default off — the persistent opt-in for session video; env twin TRAILBLAZE_CAPTURE_VIDEO, per-run twin --capture-video)
Experimental	stream-screenshots, ios-baguette-video, disable-animations, turbo

Experimental keys are tri-state (true, false, or unset to inherit the default) and each has an env-var twin documented below.

Settings keys with no trailblaze config key

Some settings live only in trailblaze-settings.json. trailblaze config neither lists nor sets them — the desktop app’s Settings → Advanced Configuration writes them, as does PUT /trailrunner/api/settings — but they are persisted, so they apply to every later CLI run that reads that settings file. Ask a running daemon what it has persisted:

curl -s "localhost:$(trailblaze app --status | awk '/^ *Port:/ {print $2}')/trailrunner/api/settings" | jq '{logsDirectory, serverPort, serverHttpsPort}'

That response echoes the settings file rather than the values in effect: logsDirectory is null whenever it is being derived, and serverPort still reads 52525 when an environment variable moved the daemon. trailblaze app --status prints the port actually in use.

logsDirectory: where session logs land

Every session directory — tool logs, screenshots, device.log, trace.json — is written under this path, and it is the default search root for trailblaze profile and trailblaze otel.

• It is persisted, and it outlives the app that set it. Settings → Advanced Configuration → Logs Directory → Change Location writes it; from then on both daemon-backed and standalone CLI runs use it. Reset to Default clears it back to unset.
• It can point outside the current checkout, including at a different checkout entirely. Never assume a run’s logs are under the directory you ran from — read the value and use it.
• Unset, it derives from the app data directory. A repo-local app data directory puts logs beside it — <git root>/logs, since app data is <git root>/.trailblaze — while the machine-global state directory keeps them inside it, at ~/.trailblaze/logs (or $TRAILBLAZE_HOME/logs). An installed binary therefore lands on ~/.trailblaze/logs and a source checkout on <git root>/logs.
• A CLI settings write materializes the derived value. Any trailblaze config <key> <value> rewrites the file with the currently derived path filled in, so the file usually carries an absolute logsDirectory even when nobody chose one. Move or rename the checkout afterwards and it keeps pointing at the old location.
• Changes apply at daemon start. The daemon opens its logs repository once during boot, so run trailblaze app --stop (or restart the desktop app) after changing this.
• Every run writes and reads here. Each host driver path builds its own logging rule against this directory, then reads the finished session back out of it to generate recording.trail.yaml (copied next to the trail source) and to compare snapshot goldens. That holds for trailblaze run, the desktop app’s Run, and MCP alike.
• Read it at runtime from GET /trailrunner/api/settings → .logsDirectory. The field echoes the persisted value, so null means the process is deriving it.

serverPort and serverHttpsPort

The persisted daemon ports, written by Settings → Advanced Configuration → Server Ports (Save, then restart) or PUT /trailrunner/api/settings. Both are plain integers defaulting to 52525 / 52526.

• A persisted non-default value outranks TRAILBLAZE_PORT / TRAILBLAZE_HTTPS_PORT. Full order inside the JVM: an in-process override applied at launch → persisted non-default serverPort/serverHttpsPort → the env var → 52525 (HTTPS derives as HTTP + 1). A value equal to the default is treated as “not set”, which is what lets the env var through.
• Set TRAILBLAZE_PORT to match a persisted port. The trailblaze launcher script does not read the settings file: it defaults TRAILBLAZE_PORT to 52525 for its own daemon probe and readiness poll. So with serverPort: 51234 persisted and no environment variable, the daemon binds 51234 while the script waits on 52525 and then reports that Trailblaze never became ready. Export the matching TRAILBLAZE_PORT, or move a non-default port to the environment variable and leave the persisted field at its default. trailblaze app --status reports the port the JVM resolved.
• A port inside the device-allocation range never takes effect. The Settings UI refuses it, and PUT /trailrunner/api/settings returns 200 while silently dropping the field, because the daemon refuses to start there — and since that route is served by the daemon, a saved value would leave no UI to undo it. See Precedence.
• Changes apply at launch, so restart the daemon.

Workspace configuration (trailblaze.yaml)

Most projects need no workspace configuration — a single .trail.yaml file is enough. Add a workspace config dir when a team wants to commit shared targets, LLM settings, toolsets, or tools. Two layouts are supported:

my-project/                          my-project/
└── trailblaze-config/               └── trails/
    └── trailblaze.yaml   ← this         ├── config/
                                          │   └── trailblaze.yaml   ← or this
(trails can live anywhere,                └── login/
 e.g. next to features)                       └── trail.yaml

Trailblaze walks up from the current directory (or from the directory containing the trail you invoked) until it finds a trailblaze.yaml in either trailblaze-config/ (the standalone layout) or the legacy trails/config/. The closest ancestor wins; when both layouts exist at the same ancestor, trailblaze-config/ takes precedence and the CLI prints a consolidation warning. Relative paths inside the file resolve against the config directory it sits in — except trails:, which resolves against the workspace root so one value means the same directory under either layout. See Project Layout for the discovery rules.

trailblaze.yaml is configuration, never a trail. Every section is optional, and an empty file is valid.

# trailblaze-config/trailblaze.yaml (or trails/config/trailblaze.yaml) — everything below is optional
defaults:
  target: my-app
  max-llm-calls: 25

targets:
  - my-app

trails: legacy-trails    # only when your trails aren't under <workspace-root>/trails

llm:
  providers:
    openai:
      models:
        - id: gpt-5.6-terra
  defaults:
    model: gpt-5.6-terra

Top-level keys

Key	Type	What it does
defaults	map	Workspace-wide defaults — see below.
targets	list of ids	Target-trailmap ids this workspace opts into. Omit to auto-discover every target trailmap under the workspace config dir’s trailmaps/. Listing ids loads only that subset. Each id must name a target trailmap (one with a target: block); library trailmaps enter scope through a target’s dependencies:.
trails	path	Directory holding this workspace’s trail files, so the desktop app and Trail Runner browse the right tree the moment you launch inside the repo. See Declaring a trails directory.
toolsets	list	Extra toolsets, either inline or pulled in with ref: path/to/toolset.yaml.
tools	list	Extra tools, with the same inline-or-ref: shape.
providers	list	Reserved for standalone LLM provider files. Provider and model definitions are read from the llm: block today.
llm	map	LLM providers, models, and defaults — see LLM Configuration.

defaults

Key	What it does
target	Target-trailmap id used when nothing more specific is selected. It must match a loaded target (case-sensitive); an unknown id is logged and skipped rather than failing the run.
llm	Reserved provider/model shorthand. Use llm.defaults.model today.
max-llm-calls	Team-wide positive-integer cap on LLM calls per objective. Per-run CLI and environment overrides still win.

Declaring a trails directory

A workspace’s trails directory (the .trail.yaml files) is a different thing from its config directory (the one holding trailblaze.yaml). They coincide only in the legacy layout, where the config dir is nested at trails/config/.

Trailblaze’s default guess for the trails directory is <workspace-root>/trails. When a repo keeps its trails somewhere else, say so:

# trailblaze-config/trailblaze.yaml
trails: legacy-trails

Relative paths resolve against the workspace root — the directory holding trailblaze-config/ (or holding trails/, in the legacy layout) — so one committed value means the same directory under either layout. A relative value may not escape that root: the file is shared by everyone who clones the repo, so ../.. would point the whole team’s app, and its recording writes, outside their checkout. Use an absolute path when you really do mean somewhere else; it can’t be portable across machines, so it reads as deliberate rather than as a typo.

Launch the desktop app or the CLI anywhere inside that workspace and the Trails tab, the Waypoints tab, Trail Runner, MCP, and saved recordings all use the declared directory. A clean install does the right thing the first time it opens the workspace, with no per-machine setup.

The trails directory resolves in this order:

1. A directory you picked in Settings (or via PUT /trailrunner/api/settings).
2. The workspace’s trails: declaration.
3. <app data dir>/../trails.

So the declaration answers the question only when you haven’t. Pick a location in Settings and it wins in every workspace; Settings names the file the current value came from, and offers Use Workspace Location to clear your choice and hand the decision back.

Two things worth knowing:

• Only an explicit declaration takes effect. Omit the key and nothing changes. Workspaces already using <workspace-root>/trails need no entry.
• An already-running daemon does not re-anchor. trailblaze app --v2 hands off to the existing window, so the workspace is the one the daemon started in. Run trailblaze app --stop and relaunch from the workspace you want.

A declared directory that isn’t on disk is logged and ignored rather than failing the launch, the same way an unknown defaults.target is.

Trailblaze does not write a trails directory into your settings unless you pick one, so “nobody has chosen yet” stays distinguishable from a real choice. A settings file written by an older version carries the default as though it were a choice; a stored value equal to the default is treated as unchosen so the workspace can still answer.

ref: entries

toolsets, tools, and providers accept either an inline entry or a pointer to a separate file:

toolsets:
  - ref: toolsets/my-toolset.yaml     # relative to the workspace config dir
  - name: inline-toolset
    tools: [tapOn, assertVisible]

Ref paths are always resolved relative to the directory holding trailblaze.yaml. A leading / is stripped and treated the same way, so /foo.yaml is not an escape to the filesystem root. A ref: entry may not carry sibling keys.

Common workspace tasks

I want to…	Go to
Use a model that is not built in	Adding a Model
Point at a private LLM gateway	LLM Configuration
See the persisted per-machine settings currently in effect	trailblaze config show (CLI)
Understand workspace discovery	Project Layout
Add custom tools to a project	Your First Trailmap

The user-level ~/.trailblaze/trailblaze.yaml uses the same llm: schema for personal providers, models, and credentials. Workspace LLM configuration overrides it; see LLM Configuration for the merge rules.

Environment variables

Only set the variables in this section; variables the framework sets for its own subprocesses are listed at the end.

Daemon and ports

Variable	Default	Applied	Purpose
TRAILBLAZE_PORT	52525	launch	Daemon HTTP port. Override to run isolated/parallel daemons. Moves the HTTPS port with it (+1). Must stay outside 52530-59529 (the device-port range; the HTTPS port, +1, is checked too); ideally below 32768 to stay clear of the OS ephemeral range too (31900 works) — see Precedence above.
TRAILBLAZE_HTTPS_PORT	HTTP port + 1	launch	Daemon HTTPS port (the adb-reverse target for on-device logging). Must be outside 52530-59529 — see Precedence above.
TRAILBLAZE_HOME	~/.trailblaze	launch	Relocates the state directory (logs, TLS keystore, settings) — lets concurrent daemons isolate state.
TRAILBLAZE_CONFIG_DIR	cwd walk-up	command	Authoritative override for the workspace config dir (trailblaze-config/ or the legacy trails/config/). Outranks the working-directory walk-up.
TRAILBLAZE_DISABLE_DAEMON_AUTOSTART	unset	use	Kill-switch: “daemon not running” becomes an error instead of an implicit background daemon spawn.
TRAILBLAZE_MCP_REQUEST_TIMEOUT_MS	630000	command	Per-request CLI→daemon MCP timeout. Default is long because agent commands legitimately run for minutes and a target’s scripted launch tool may use the daemon’s whole nested-callback budget (trailblaze.callback.timeoutMs) plus its buffers; lower it to fail fast when triaging a wedged device, and raise it if you raise that budget. Read from the shell that invoked the command, including for the commands the launcher hands to a running daemon, and it bounds the mcp proxy’s hop to the daemon as well – which is the only lever an external agent has, since raising the callback budget lifts the daemon’s per-tool cap above this default.
TRAILBLAZE_MCP_PREFLIGHT_TIMEOUT_MS	5000	command	How long the CLI’s read-only pre-flight steps wait (the MCP handshake that opens a session, validating a saved session, autodetecting the only connected device) before the command fails with a pointer at trailblaze status and TRAILBLAZE_IO_PARALLELISM. Separate from the request timeout because these run before your command starts, and a starved daemon answers /ping while never answering them. The launcher forwards it to a daemon-executed command, so upgrade the launcher along with the daemon if you need to raise it; an older one drops the value and the default stays in force. Capped at TRAILBLAZE_MCP_REQUEST_TIMEOUT_MS, since a pre-flight bound above the deadline it carves a window out of could never fire. Unlike that variable, this one is read from your shell rather than the daemon’s. Raise it only for a healthy daemon on a slow machine.
TRAILBLAZE_RUN_POLL_TIMEOUT_MS	600000	command	Inactivity watchdog for trailblaze run: max time a run may go without new progress before the CLI gives up. Not a wall-clock cap — a trail that keeps advancing runs as long as it needs.
TRAILBLAZE_CLI_PRINT_STACK_TRACES	unset	use	Print raw stack traces alongside the structured CLI error envelope.
TRAILBLAZE_IO_PARALLELISM	512 when the trailblaze launcher starts the JVM	launch	How many blocking operations the JVM may have in flight at once. Raise it if a target declares hundreds of scripted tools: each one runs in a subprocess that holds a slot for the whole session, and running out does not fail on the daemon — it keeps answering /ping while every real command hangs. The CLI notices on its next device command: its pre-flight handshake and device probes give up after TRAILBLAZE_MCP_PREFLIGHT_TIMEOUT_MS (5 s by default) and name this variable. Read once at JVM start, so a running daemon must be restarted (trailblaze daemon stop) for a change to apply. Must be an integer between 1 and 2147483647; the launcher rejects anything else rather than letting the JVM die on it later. Anything below 17 is accepted but leaves no room for scripted tools, because 16 slots are held back for the host’s own work. A JVM that does not come from the launcher does not read this variable: a java -jar, an Android host, or a Gradle test worker gets the JVM default of max(64, CPU count) instead, and must be given -Dkotlinx.coroutines.io.parallelism=<n> directly. For the packaged desktop app the value is baked in when the installer is built, so changing it on the machine that runs the app has no effect.

Development-checkout launcher knobs (the ./trailblaze wrapper script; installed CLIs ignore these): TRAILBLAZE_MAX_HEAP (JVM max heap, default 4g — raise for very large workspaces or heap-hungry report generation), TRAILBLAZE_JAR (path to the built uber JAR), TRAILBLAZE_IPC=0 (disable the daemon IPC fast path), TRAILBLAZE_REBUILD_GRADLE_TASK (override the rebuild task), TRAILBLAZE_FORCE_DAEMON_STOP=1 (stop a busy daemon anyway when the rebuilt JAR needs to take effect now — by default a daemon with in-flight runs is left running).

Runs and recordings

Variable	Default	Applied	Purpose
TRAILBLAZE_DEVICE	unset	command	Manual device override for a shell or non-interactive harness. Interactively you rarely set it — trailblaze device connect records a terminal-scoped pin instead. A --device flag still wins.
TRAILBLAZE_TARGET	unset	command	Per-shell target pin for forwarded subcommands (clear = unset).
TRAILBLAZE_MAX_LLM_CALLS	25	command	Per-objective LLM call cap for the built-in Trailblaze Runner and strategy-graph agents (flag → env → workspace defaults.max-llm-calls → config key).
TRAILBLAZE_SELF_HEAL_ENABLED	false	command	Enable self-heal on recorded replays (flag → env → config key). A multi-device session refuses to open with self-heal on — see TRAILBLAZE_DEVICE_BINDINGS below.
TRAILBLAZE_DEFAULT_MODEL	LLM config value	session	Overrides defaults.model from the loaded LLM configuration.
TRAILBLAZE_OLLAMA_NUM_CTX	65536	session	Positive host-side Ollama num_ctx request override. Malformed or non-positive values fall back to 64K. See Ollama (Local Models).
TRAILBLAZE_DEFERRED_VARIABLES	empty	command	Comma-separated {{var}} names excluded from environment expansion in trail templates (left for runtime memory instead).
TRAILBLAZE_AUTO_TERMINATE_VERIFY_STEPS	false	session	Ends a verify step for an agent that keeps checking instead of declaring itself done. Two signals end it: every target named in the verify text has been asserted successfully, or the agent is visibly re-asserting targets it already proved. Off by default — with it on, a step can end before the agent would have chosen to. Only affects verification steps.
TRAILBLAZE_DEVICE_BINDINGS	unset	session	Binds the non-start named devices of a multi-device trail’s config.devices: configuration entry to connected devices, as comma-separated name=deviceInstanceId pairs (e.g. buyer=emulator-5556). The configuration’s first declared device is the start device and binds to the launch device automatically; every other declared name needs an entry here — the declared classifier is the trail’s portable contract, but classifier-based auto-binding is not implemented yet. Prefer trailblaze run --bind buyer=emulator-5556 (repeatable) — it is per-run, so it needs no daemon restart and two multi-device trails can run concurrently against different device sets, which one daemon-wide value cannot express. This variable remains the fallback for callers that cannot pass flags. Read by the daemon, so restart it (trailblaze --stop) if it was started without the variable. A run request carrying its own bindings — which --bind sets — replaces this value wholesale rather than merging with it. Three rules govern what such a session accepts, all reported at session start before the first step: it must run with self-heal off (--self-heal=false — healing writes a recovered leg back into your trail source and misaligns the steps around it, so legs end up replaying on the wrong display); every switchDevice in a leg the run will actually replay must name a device the configuration declares (a stale name in a leg the run re-blazes past doesn’t stop it, so re-running with --no-use-recorded-steps is how you repair one — trailblaze check still flags it); and a name may not be bound to a device another name already holds. AI-driven steps are supported — the model is told the device roster and can hand over itself — unless the start target’s excluded_tools: drops switchDevice, in which case the session accepts recorded steps only.
TRAILBLAZE_DEVICE_CONFIGURATION	unset	session	Names which of a multi-device trail’s config.devices: configuration entries a run binds. Only needed when a trail declares more than one — a trail declaring exactly one binds it implicitly, and a trail declaring several with no selection is rejected rather than defaulting to the first. A name the trail doesn’t declare is an error; the variable is ignored on trails that declare no configuration at all, so one daemon can serve both. Prefer trailblaze run --configuration <name>, which is per-run and needs no daemon restart. Read by the daemon (restart it if it was started without the variable), and overridden by a selection on the run request itself — which --configuration sets.
TRAILBLAZE_TRAILS_DIR	configured trails root	launch	Overrides the Trail Runner web UI’s primary trails root. Unset, the UI uses the effective trails directory — the launch workspace’s trails: declaration if it has one, else the directory configured in the app (the app-data trails/ dir unless you picked a workspace) — falling back to <cwd>/trails only when that path doesn’t exist.

Android devices

The accessibility-driver switches below are read inside the Android app/service process. Trailblaze does not forward arbitrary host shell environment variables into an already-launched Android process, so treat them as process-local/device-harness controls rather than VAR=x trailblaze run … host overrides.

Variable	Default	Applied	Purpose
ADB_SERVER_SOCKET	unset	launch	Point at a remote adb server (tcp:<host>:<port>), same semantics as the upstream adb binary. Wins over ANDROID_ADB_SERVER_PORT.
ANDROID_ADB_SERVER_PORT	5037	launch	Port-only adb server override (host stays localhost).
TRAILBLAZE_ADB_TIMEOUT_MS	10000	launch	Bound for short-lived host-side adb shell calls. Streaming paths (logcat -f, screenrecord) are exempt. Bump for slow CI emulators.
TRAILBLAZE_DISABLE_ACTION_CLICK_ROUTE	unset	use	Kill-switch: force every selector-resolved tap back to coordinate gestures instead of accessibility ACTION_CLICK.
TRAILBLAZE_DISABLE_TAP_OCCLUSION_WARN	unset	use	Suppress warn-only diagnostics when another visible node covers the selector-resolved tap point; dispatch is unchanged.
TRAILBLAZE_DISABLE_TARGET_TYPE_WARN	unset	use	Suppress warnings when a selector resolves to an unrequested or ambiguous text input; resolution and dispatch are unchanged.
TRAILBLAZE_IME_DISMISS_VIA_SHOW_MODE	unset	use	Route hideKeyboard through the accessibility SoftKeyboardController show-mode instead of a BACK key event (a modal’s back handler can’t swallow it; no back-stack side effects).
TRAILBLAZE_DISABLE_SETTLE_TREE_STABILITY	unset	use	Kill-switch for the capture-time settle gate (tree stability + completeness) — capture immediately with no wait.
TRAILBLAZE_SETTLE_VIA_WAIT_FOR_IDLE	unset	use	Kill-switch for the post-action event-quiet settle: restore the legacy UiDevice.waitForIdle() (fixed 500 ms quiet window) after every gesture.
TRAILBLAZE_DISABLE_BATCHED_TOOL_EXECUTION	unset	use	Kill-switch: give every recorded tool its own execution context instead of sharing one per recording batch.
TRAILBLAZE_ANDROID_WIRE_TRANSPORT	auto	launch	Host↔device RPC / log-upload wire format: auto, protobuf, or json (rollback switch).
TRAILBLAZE_CAPTURE_SECONDARY_TREE	false	session	Capture a secondary view-hierarchy snapshot per selector tool (driver-migration comparison aid).

iOS simulators

Variable	Default	Applied	Purpose
TRAILBLAZE_BAGUETTE	PATH, then Homebrew	launch	Explicit path to the baguette binary (optional macOS dependency powering live H.264 simulator streaming). Absent → the device viewer falls back to screenshot polling.
TRAILBLAZE_BAGUETTE_SERVE_PORT	8421	launch	Port for the shared baguette serve process (loopback only).
TRAILBLAZE_IOS_BAGUETTE_VIDEO	unset	session	Experimental (config twin: ios-baguette-video): record session video by muxing the live baguette stream (wall-clock-accurate frame timestamps) instead of simctl io recordVideo. Declines per session when baguette is unavailable.
TRAILBLAZE_IOS_CLEAR_STATE_MODE	reinstall	use	AXe clearState route. Set container (case-insensitive) to wipe the app data container in place; any other value keeps uninstall-and-reinstall. Both routes fail if the clear does not complete.
TRAILBLAZE_DISABLE_AXE_WEB_CONTENT	unset	use	Kill-switch for AXe WKWebView content descent. The default enables descent when the installed axe binary advertises support. Restart after upgrading axe because that capability probe is cached.

Web and Electron apps

Variable	Default	Applied	Purpose
TRAILBLAZE_ELECTRON_COMMAND	unset	session	Launch command for an Electron app under test (fallback when the target declares no Electron config).
TRAILBLAZE_ELECTRON_ARGS	empty	session	Space-separated launch args.
TRAILBLAZE_ELECTRON_CDP_URL	unset	session	Attach to an already-running Electron app via this CDP endpoint.
TRAILBLAZE_ELECTRON_CDP_PORT	9222	session	CDP port used when launching.
TRAILBLAZE_ELECTRON_HEADLESS	false	session	Launch Electron headless.
TRAILBLAZE_PLAYWRIGHT_DRIVER_REPO	Maven Central	launch	Extra Maven base URL tried first for the Playwright driver-bundle download (air-gapped/mirrored environments).

Screenshots and capture

The stream and proxy capture switches are experimental and off by default; each STREAM_SCREENSHOT env var has AB-mode and config-key companions. Sprite controls tune the timeline artifacts generated for host sessions.

Variable	Default	Applied	Purpose
TRAILBLAZE_CAPTURE_VIDEO	unset	session	Record device screen video for every session in this process (config twin: capture-video; per-run flag twin: --capture-video). Video is off by default — recordings are large, their timing signatures drift on some hosts, and sprite extraction is expensive. Set this to get video and the sprite timeline back for a CI lane or a debugging session without a code change. Only a truthy value opts in — a falsey one reads the same as unset, so unset it to turn video off. Outranked by an explicit --capture-video / --no-capture-video, and outranks the saved capture-video config.
TRAILBLAZE_ANDROID_STREAM_SCREENSHOT / TRAILBLAZE_IOS_STREAM_SCREENSHOT / TRAILBLAZE_WEB_STREAM_SCREENSHOT	unset	session	Serve agent-loop screenshots from the device’s live video stream instead of per-turn direct captures (config twin: stream-screenshots, one toggle for all three platforms). Unmatched captures fall back to a direct screenshot.
…_STREAM_SCREENSHOT_AB (same three prefixes)	unset	session	A/B validation: direct screenshot stays authoritative, stream matcher runs alongside and logs match/unmatch per capture. Run this before trusting the stream path.
TRAILBLAZE_DISABLE_ANIMATIONS	unset	session	Disable OS animations for the duration of each session, restoring previous values at session end (config twin: disable-animations). Android: zeroes the three global animation scales; iOS simulators: near-zero UIAnimationDragCoefficient (deliberately not Reduce Motion, which apps branch on).
TRAILBLAZE_TURBO	unset	session	Turbo mode: let the Android app under test report when it is idle so the accessibility driver waits less after each action, instead of watching for its screen to go quiet (config twin: turbo; per-run flag twin: --turbo / --no-turbo, which outranks both). Each wait ends at whichever answer arrives first, so turbo can only shorten one — same driver, same selectors, same recordings. Requires an app signed with a certificate Trailblaze carries a matching helper for, so a release or beta build declines and runs at normal speed — as does a trail whose target: names no loaded target, since the run then falls back to the workspace default and turbo will not attach to an app the trail does not drive. Turning it on installs the helper into the app and restarts it. Read by the daemon, so restart it (trailblaze --stop) if it was started without the variable — or prefer trailblaze run --turbo, which is per-run and travels with the request.
TRAILBLAZE_ANDROID_PROXY_CAPTURE	unset	session	Single switch for Android network capture via a host-side mitmproxy (emulator-only, API 34+, needs mitmproxy installed): routes the emulator through mitmdump, installs the CA, writes network.ndjson into the session.
TRAILBLAZE_MITMDUMP	mitmdump on PATH	session	Explicit path to the mitmdump binary.
TRAILBLAZE_NETWORK_CAPTURE_DEVICES	unset (= every bound device)	session	Comma-separated config.devices: names to arm Android network capture on in a multi-device session. A multi-device session captures each device separately and suffixes its artifacts with the device name (network.<device>.ndjson, events/<stream>.<device>.ndjson), so both displays’ evidence lands in one session. Narrow it when only some of a pair’s displays run a capture-capable app: capture is load-bearing evidence, so a device whose app never dials in fails the session after the discovery timeout. A name no bound device matches is logged, not ignored. Read by the daemon, so restart it (trailblaze --stop) if it was started without the variable.
TRAILBLAZE_SNAPSHOT_BASELINE	unset	session	Diff each run’s takeSnapshot captures against a PREVIOUS run instead of checked-in golden files: an http(s) URL to a session logs zip, a local zip, or an extracted session directory. Snapshots match by name (and occurrence, for repeated names); a snapshot the baseline lacks is skipped, a mismatch above the threshold fails the run, and an unresolvable reference fails it too — an explicitly requested baseline never silently compares nothing. Read by the process that executes the comparison, so for a daemon-delegated run set it on the daemon (or prefer trailblaze run --snapshot-baseline <ref>, which is per-run and travels with the request). Failing snapshots get a 3-panel Baseline | Diff | Actual PNG written beside the screenshot.
TRAILBLAZE_SNAPSHOT_BASELINE_THRESHOLD	2.0	session	Pass threshold for the baseline comparison: a snapshot passes when its pixel diff percentage is <= this value. Per-run flag twin: --snapshot-baseline-threshold.
TRAILBLAZE_SPRITE_FPS	2	session	Host-session timeline sprite frame rate (1..60); invalid values fall back and log the chosen default.
TRAILBLAZE_SPRITE_FRAME_HEIGHT	720	session	Host-session timeline sprite frame height in pixels (16..16383).
TRAILBLAZE_SPRITE_QUALITY	80	session	Host-session timeline sprite WebP quality (1..100).

Scripted tools and the analyzer

The tool-definition analyzer extracts JSON Schemas from TypeScript scripted tools in a bun subprocess; inline script: MCP tools run as bun subprocesses too.

Variable	Default	Applied	Purpose
TRAILBLAZE_TOOL_ANALYZER_TIMEOUT_SECONDS	60	launch	Per-trailmap analyzer subprocess timeout.
TRAILBLAZE_TOOL_ANALYZER_NO_CACHE	unset	launch	Bypass the workspace-local analyzer cache entirely (reads and writes).
TRAILBLAZE_SDK_DIR	walk-up resolution	launch	Explicit path to the scripting SDK directory (installed-CLI scenarios where the SDK isn’t a cwd ancestor). The directory must have its dependencies installed (bun install): an SDK whose deps are missing is ignored for on-device tool bundling — bundling against it would fail every scripted tool — and Trailblaze falls back to its own SDK copy.
TRAILBLAZE_SDK_PACKAGE	@trailblaze/scripting	launch	npm package name that defines the recognized authoring surface.
TRAILBLAZE_MCP_SUBPROCESS_HANDSHAKE_TIMEOUT_MS	60000	launch	Watchdog on the MCP initialize handshake with each tool subprocess — a hung cold start fails that session’s startup fast instead of wedging the daemon.
TRAILBLAZE_CLIENT_FETCH_TIMEOUT_MS	32000 standalone	subprocess	Client-side fetch timeout read when the tool subprocess imports the SDK; normally forwarded automatically from the daemon’s callback timeout (see JVM system properties).

trailblaze check

Variable	Default	Applied	Purpose
TRAILBLAZE_DISABLE_TRAIL_RECORDING_VALIDATION	unset	command	Skip the recorded-tool type-validation phase (per-trailmap tsc pass) entirely — shaves latency in a tight inner loop.
TRAILBLAZE_DISABLE_SELECTOR_DIALECT_GATE	unset	command	Emergency opt-out from the selector/driver compatibility phase. It skips this trailblaze check phase, but not the unconditional Gradle corpus test.
TRAILBLAZE_DISABLE_DEVICE_PIN_GATE	unset	command	Emergency opt-out from the device-pin gate, which fails a trail that declares a device driver outside the classifier it pins (config.driver: beside config.devices:, or a devices: entry keyed driver) and warns on the deprecated bare-string device form. Separate from the selector-dialect switch on purpose, so turning one off never silently drops the other.
TRAILBLAZE_DISABLE_TRAIL_TARGET_GATE	unset	command	Silences the trail-target check, which warns (it does not fail the build) when a trail’s config.target: — or a per-device target: override — names an id this workspace cannot resolve. Left to run time, such a target silently falls back to the workspace default and the trail still reports PASSED against a different app than it names. Naming a target is optional: a trail with no config.target: uses the workspace default and is never flagged. Its own switch, like the two above.
TRAILBLAZE_TYPECHECK_TIMEOUT_MS	300000	command	Timeout for the TypeScript typecheck phase (clamped to ≥ 1 min).
TRAILBLAZE_TEST_TIMEOUT_MS	300000	command	Timeout for the trailmap unit-test runner.

In-process test APK signing (trailblaze inprocess make-test-apk)

make-test-apk signs its output with the target app’s key, so it needs that keystore’s passwords. They are read from the environment or, failing that, prompted for on the terminal — never from the command line, because argv is visible to ps, lands in shell history, and gets echoed by CI log tracing.

Variable	Default	Applied	Purpose
TRAILBLAZE_INPROCESS_KEYSTORE_PASSWORD	prompt	command	Password for the --keystore file.
TRAILBLAZE_INPROCESS_KEY_PASSWORD	the keystore password	command	Password for the key named by --alias, when it differs from the store’s.

Runtime scripted-tool bundles (allow_runtime_tool_source)

An in-process test APK normally replays with the scripted-tool bundles that were packaged into it, which pins its tool vocabulary to whenever it was built. A host that drives the run itself can instead push bundles matching the trails it is about to replay:

/data/local/tmp/trailblaze/tool-bundles/trails/config/trailmaps/<id>/tools/<stem>.bundle.js

Two gates guard that path, both because the files there are unsigned code that executes inside the app’s process:

1. The process is instrumented. A production install of an app that ships these classes never reads tools off disk.
2. The target config opted in. --allow-runtime-tool-source writes allow_runtime_tool_source: true into the --target-config before signing, so the choice is covered by the signature and is reported in the build record beside the output APK. It is off unless the flag is passed, so an APK produced at a signing ceremony replays from its own frozen assets even when a host drives it — the shell cannot tell one host holding the device from another.

/data/local/tmp is drwxrwx--x shell shell, so only a host holding adb can plant a bundle there; the app process can read one by exact path but cannot write or list the directory. Push bundles world-readable (chmod -R a+rX) — the app process shares neither the uid nor the group of whatever wrote them.

Built-in agent tuning

These affect only the default KOOG_STRATEGY_GRAPH agent. Explicit TRAILBLAZE_RUNNER and MULTI_AGENT_V3 selections ignore them. All are applied per agent run.

Variable	Default	Purpose
TRAILBLAZE_KOOG_DISABLE_HISTORY_COMPRESSION	unset	Prune-only context management (no summarization of older turns).
TRAILBLAZE_KOOG_HISTORY_COMPRESSION_THRESHOLD	30	Message count above which older turns are folded into a summary.
TRAILBLAZE_KOOG_LOOP_DETECT_THRESHOLD	3	Identical back-to-back tool dispatches before a “loop detected” nudge; <= 0 disables.
TRAILBLAZE_KOOG_DISABLE_SCREENSHOT	unset	Send view-hierarchy text only (drop the annotated screenshot) — for A/B or token cost.
TRAILBLAZE_KOOG_DISABLE_VERIFY_SCOPE	unset	Keep the full tool surface on verify-only steps instead of scoping to assertion tools.
TRAILBLAZE_KOOG_DISABLE_VERIFY_EVIDENCE	unset	Let a verify-only step report COMPLETED with no passing assertion behind it. Independent of the scope switch above.
TRAILBLAZE_KOOG_DISABLE_FAILED_RETRY	unset	End a direction step on the model’s first FAILED report instead of retrying it once from a rewound conversation.

Tracing detail

Variable	Default	Applied	Purpose
TRAILBLAZE_TRACE_LEVEL	normal	process	How much of a run is recorded into trace.json: off, normal, or verbose. normal records tools, agent phases, LLM calls and HTTP. verbose adds the fine-grained spans underneath — driver operations, screen-capture internals, per-node selector matching — as each of those layers gets instrumented; a layer that has none yet records the same at both levels. On Android runs driven by the accessibility driver this includes the on-device capture, whose spans land on the profiler’s flat Device lane — though this variable reaches the host and its daemon, not the separate instrumentation process on the device, so those spans still record at normal; see Performance Profiling for how to read them. An instrumented test that drives the in-process ANDROID_TEST driver sets its own level with the trailblaze.trace.level instrumentation argument instead, since there the instrumentation is the run. An unrecognized value is reported and treated as normal. Read from the shell that starts the run and applied to that run alone, so a daemon started at one level does not pin every later run to it.

verbose is for a specific investigation, not a default. Its spans fire hundreds of times per step, and a span that costs more than the work it measures changes the shape of what you are profiling. See Performance Profiling.

Reports and results

Variable	Default	Applied	Purpose
MAX_PLAYBACK_WAIT_MS	600000	command	Playback ceiling for MP4, GIF, and WebP report exports. Non-numeric or non-positive values fall back to the default; an overrun still writes a best-effort truncated artifact.
TRAILBLAZE_REPORT_IMAGE_COMPRESSION_PARALLELISM	min(cores, 4)	command	Thread count for report image compression.
TRAILBLAZE_RESULTS_REPO	unset	command	owner/name of the results-index repository when --repo isn’t passed to trailblaze results.

CI systems additionally stamp report metadata via TRAILBLAZE_TARGET_APP, TRAILBLAZE_DEVICES, TRAILBLAZE_BUILD_TYPE, TRAILBLAZE_TEST_RETRY_COUNT, TRAILBLAZE_AI_ENABLED, and TRAILBLAZE_PARALLEL_EXECUTION. The report generator reads them all as labels, but CI pipelines commonly bridge TRAILBLAZE_AI_ENABLED (disables the LLM for the run) and TRAILBLAZE_TEST_RETRY_COUNT (drives retry loops) into real run behavior — don’t treat those two as cosmetic.

OpenTelemetry export

Off unless you set an endpoint. These are OpenTelemetry’s own variable names, so a collector or local viewer that is already running needs no Trailblaze-specific configuration.

Variable	Default	Applied	Purpose
OTEL_EXPORTER_OTLP_ENDPOINT	unset	run	Base endpoint every signal shares; /v1/traces is appended. Setting it makes a run send its recorded spans there as soon as it writes trace.json.
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT	unset	run	Full traces endpoint, path included. Takes precedence over the shared variable, and nothing is appended to it.
OTEL_EXPORTER_OTLP_PROTOCOL	inferred	run	grpc or http/protobuf. When unset, port 4317 is treated as gRPC and anything else as OTLP/HTTP.
OTEL_EXPORTER_OTLP_TRACES_PROTOCOL	inferred	run	Same, for traces only. Takes precedence.
OTEL_EXPORTER_OTLP_HEADERS	unset	run	key1=value1,key2=value2 headers on every export request — what an authenticating collector needs. A value may contain =; only the first one separates.
OTEL_EXPORTER_OTLP_TRACES_HEADERS	unset	run	Same, for traces only. Merged over the shared variable per key, so a shared header with no override still applies.

A run with no endpoint configured sends nothing and still writes trace.json; trailblaze otel converts a recorded session on demand. See Performance Profiling.

Stability kill-switches

Rollback levers for specific framework behaviors — reach for one when a change regresses your pipeline and you need a one-line revert while the underlying issue is fixed.

Variable	Applied	Reverts
TRAILBLAZE_MEMORY_BLANK_UNKNOWN_TOKENS	use	Unknown {{var}} tokens resolve to empty strings again instead of failing loudly.
TRAILBLAZE_DISABLE_BOUNDARY_MEMORY_INTERPOLATION	use	Disable dispatch-boundary memory interpolation.
TRAILBLAZE_DISABLE_NESTED_DISPATCH_RECORDING_FILTER	use	Record nested tool dispatches again.
TRAILBLAZE_DISABLE_SCRIPTED_ARG_TYPE_COERCION	use	Disable scripted-tool argument type coercion.
TRAILBLAZE_DEVICE_DISCOVERY_CACHE_TTL_MS / TRAILBLAZE_DISABLE_DEVICE_DISCOVERY_CACHE	use	Tune (default 1500 ms) or disable the device-discovery cache.

Set by the framework, not by you

The framework exports these into its own subprocesses; don’t set them yourself. Scripted-tool and MCP-server authors may read the device-context ones as a stable contract:

• Read-only contract for tool subprocesses: TRAILBLAZE_DEVICE_PLATFORM, TRAILBLAZE_DEVICE_DRIVER, TRAILBLAZE_DEVICE_WIDTH_PX, TRAILBLAZE_DEVICE_HEIGHT_PX.
• Internal plumbing: TRAILBLAZE_SESSION_ID, TRAILBLAZE_SESSION_DIR, TRAILBLAZE_TOOLSET_FILE, TRAILBLAZE_BASE_URL, TRAILBLAZE_SHELL_PID, TRAILBLAZE_LAUNCHER, TRAILBLAZE_INTERACTIVE, TRAILBLAZE_TRAIL_CONTEXT, TRAILBLAZE_SETUP_TRAIL_ID.

JVM system properties

Tuning knobs for the /scripting/callback endpoint that backs the TypeScript scripting SDK’s client.tools.<name>(args) round-trip. Defaults are production-ready; override only when a slow emulator or unusual composition graph needs more headroom.

• -Dtrailblaze.callback.timeoutMs (defaults to 600000) — Per-callback dispatch timeout on the daemon side. Raise when a target tool is legitimately slow (e.g. waiting for a screen to settle on a slow emulator); lower it when the harness around the run stops sooner than this, so the timeout you get names the tool instead of killing the process. One override moves the whole ladder inside the daemon: the subprocess’s fetch timeout, the daemon’s own outer tool call, and the cap the daemon puts on any single MCP tool call all resolve this property at runtime, so none of them can cancel a call before the budget you asked for. What it does not move is the caller’s own deadline — TRAILBLAZE_MCP_REQUEST_TIMEOUT_MS is a separate budget, so raising this past it brings back the failure that budget exists to prevent: the CLI gives up and reports an error for a tool the daemon goes on to finish. Raise both together; the second one is an env var read from the shell that invoked the command, so no rebuild is involved.
• TRAILBLAZE_CLIENT_FETCH_TIMEOUT_MS (env var, defaults to 32000 standalone) — Client-side fetch timeout in the subprocess. At runtime the daemon forwards its own timeout value + 2 s as this variable, so the daemon is normally the one that surfaces a structured timeout. If you raise trailblaze.callback.timeoutMs, raise this in lockstep — otherwise the client aborts the HTTP request before the daemon can return. Sampled once at SDK module load.
• -Dtrailblaze.callback.maxDepth (defaults to 16) — Reentrance cap for recursive callback chains (a subprocess tool dispatching another subprocess tool counts as one level).
• -Dtrailblaze.callback.maxBodyBytes (defaults to 1048576 / 1 MB) — Maximum accepted callback request body size; larger declared bodies are rejected with HTTP 413.

Unrelated to callbacks:

• -Dtrailblaze.trace.level (defaults to normal) — Same values as TRAILBLAZE_TRACE_LEVEL, and checked first, so a single run can override the environment it inherits.

The Homebrew-installed launcher also sets -Dtrailblaze.appdata.dir to pin the settings directory — relevant only if you’re building custom launch wrappers.

On-device Android instrumentation arguments

• trailblaze.aiEnabled (defaults to true) - This will have the Trailblaze SDK send all requests to the LLM. When false, only recordings can be used.
• trailblaze.reverseProxy (defaults to false) - This will enable the reverse proxy for all Trailblaze traffic.
• When false, logging traffic is sent to https://10.0.2.2:<httpsPort>, the default Android Emulator networking loopback address.
• When true, the logs are sent through https://localhost:<httpsPort> and using adb reverse tcp:<httpsPort> tcp:<httpsPort> are forwarded to the host running the Trailblaze app.
  • This means all Trailblaze SDK Traffic is re-routed through adb and then the logs server reverse proxies the traffic to the final host.
  • This is important because it allows the Trailblaze Agent to run on-device, but not require a network connection.
  • It is also helpful/important because in the future it will allow you to not send your API Keys to the device itself, but add the Authorization information via the reverse proxy.
• trailblaze.httpsPort (defaults to 52526, i.e. trailblaze.port + 1) - The HTTPS port the on-device runner sends logging traffic to. Host-driven runs set this for you and ignore any value you pass: the daemon injects the port its own HTTPS server bound, which is also the port it adb reverses, so the two can never disagree. Setting it yourself only takes effect where no Trailblaze daemon launched the instrumentation — a Gradle-launched instrumented test being the case that matters — and there it should match the server you want logs to reach.
• trailblaze.logsEndpoint - Defaults to the same values as the reverseProxy uses. You can use this value if you want to use a remote logs server. NOTE: Logging timeouts are set to 5 seconds as they are expected to be fast.
• trailblaze.selfHeal (unset by default) - Strict true/false: enable self-heal for on-device runs. Unset (or an invalid value) defers to the host-side resolution, same parser as TRAILBLAZE_SELF_HEAL_ENABLED.
• trailblaze.agent (defaults to the standard agent) - Agent implementation name for on-device runs; unknown values fall back to the default with a logged warning.
• trailblaze.driverType (unset by default) - Force override for the on-device driver (e.g. ANDROID_ONDEVICE_ACCESSIBILITY); when set, the per-trail config.driver YAML value is skipped entirely.
• trailblaze.target (unset by default) - Selects which injected target config an in-process test APK runs against, by its id. Unset, the APK uses the single injected config it carries; an APK carrying more than one refuses to guess and names the ids it has. An id the APK does not carry is an error rather than a silent fall-through to the built-in default.
• trailblaze.turbo (defaults to false) - Strict true/false (anything else is read as false and warned about): turbo for a run that has no host. The on-device runner installs the idle-detector APK it carries in its own assets, attaches it to the app under test and switches the settle race on, so waits after each action end as soon as the app reports itself idle rather than when its screen has been quiet long enough. On-device counterpart of TRAILBLAZE_TURBO, and the two spell the same feature: same detector, same protocol, same [turbo] log lines. Note the env var also accepts 1, while this arg does not — pass true. Requires an idle-detector build signed with the app’s own signing key to be staged in the test APK (the Trailblaze Android Gradle plugin’s inProcessIdle { } block); a run with none, or one whose attach fails for any other reason, says so and replays at normal speed. Turbo never fails a run unless you ask it to with trailblaze.turbo.required. Only applied when the resolved driver is ANDROID_ONDEVICE_ACCESSIBILITY — that driver owns the settle gates that read the detector, so any other driver would pay the attach (including a restart of the app under test) for a signal nothing reads.
• trailblaze.turbo.required (defaults to false) - Strict true/false: makes a failed turbo attach fail the run instead of quietly replaying at normal speed. Only meaningful alongside trailblaze.turbo. For runs that measure turbo rather than merely benefit from it: the [turbo] lines saying whether the detector attached go to the device log, which a remote device-farm run does not collect, so without this a run that never got turbo is indistinguishable from one that did — both pass. With it, the pass/fail result itself carries the answer. The failure is a distinct exception type (OnDeviceTurbo.TurboRequiredButUnavailableException) so it reads as “this run did not get turbo” rather than as a failing trail. Gates both the attach before the trail and the re-attach around each launchApp, so a trail whose first step force-restarts or clears the app under test — which discards the first attach, since the detector dies with the app’s process — still cannot pass while replaying at heuristic speed. Enforced by the on-device runner, so a run driven by a host instead gets best-effort turbo regardless of this arg.
• trailblaze.captureSecondaryTree (defaults to false) - Strict true/false: also dump the legacy UiAutomator view hierarchy on every capture and use it as the captured viewHierarchy (selector-migration aid; roughly doubles per-step capture latency and session-log size). On-device counterpart of TRAILBLAZE_CAPTURE_SECONDARY_TREE.

Diagnostic log prefixes

Most subsystems tag their diagnostic lines with a bracketed prefix, so you can grep one subsystem out of a verbose run. These go through the console logger, which is suppressed in CLI quiet mode — run with -v or inspect $TRAILBLAZE_HOME/daemon.log for a detached daemon. Desktop logs use $TRAILBLAZE_HOME/desktop-logs/trailblaze.log on the default port and trailblaze-<port>.log on a custom port.

Prefix	Subsystem
[AndroidHostAdbUtils]	Host-side adb (timeouts, env overrides, client eviction)
[tap-route], [tapByActionClickOnBounds]	Android selector-resolved tap routing
[tap-occlusion], [tap-target-type]	Android tap-overlay and selector-target warnings
[hideKeyboard]	IME dismissal routing
[settle], [capture-coverage]	Android settle gates and tree-completeness checks
[ToolBatchScope]	Batched recorded-tool execution
[ScriptedToolDefinitionAnalyzer]	Scripted-tool schema analyzer
[McpSubprocessSession]	Tool subprocess handshake watchdog
[CliMcpClient], [DaemonClient]	CLI→daemon request timeouts and run polling
[KOOG], [KOOG_PRUNE], [KOOG_COMPRESS], [KOOG_SCREENSHOT], [KOOG_VERIFY_SCOPE]	Strategy-graph agent
[stream-screenshot]	Stream-sourced screenshots (including AB-mode lines)
[baguette-video], [IosBaguetteServer], [devices-stream]	iOS streaming and stream-sourced video
[disable-animations]	Session animation disabling
[turbo]	Turbo mode attach and its per-session outcome
[mitm-capture]	Android proxy network capture
[AxeDeviceManager]	iOS AXe clear-state routing
selector-dialect gate (FATAL)	Selector/driver incompatibilities found by trailblaze check