Inspect Homeboy core-owned runtime assets used by extension runners.

Runtime Packages

Homeboy discovers installable runtime packages from ~/.config/homeboy/agent-runtimes/<runtime-id>/<runtime-id>.json. Extension repositories can ship shared runtime packages in agent-runtimes/; homeboy extension install copies that directory into the Homeboy config area.

Runtime package manifests declare generic executor providers through agent_task_executors. Core consumes provider identity, backend, command, capabilities, readiness, role aliases, workspace materialization, and secret requirement/default declarations for selection, listing, interpolation, and redacted execution setup. Backend-specific orchestration remains inside the runtime package command.

Provider commands can use {{runtime_path}}, and Homeboy injects HOMEBOY_RUNTIME_PATH, HOMEBOY_AGENT_RUNTIME_ID, and HOMEBOY_AGENT_RUNTIME_PATH when executing runtime-package providers.

Helper Paths

Resolve the materialized path for a bundled core runtime helper:

homeboy runtime helper path runner-prelude.sh
homeboy runtime helper path HOMEBOY_RUNTIME_COMMAND_CAPTURE

The command accepts only known helper filenames or the corresponding injected HOMEBOY_RUNTIME_* environment variable names. It is not a general runtime package browser, extension asset resolver, or arbitrary config-path lookup. Normal extension execution receives these paths automatically in the runner environment.

Use --plain when a shell wrapper needs a sourceable path without parsing JSON:

source "$(homeboy runtime helper path --plain runner-prelude.sh)"