Skip to main content

Module bundled

Module bundled 

Source
Expand description

The agent blueprints shipped inside the lev binary, and the planner that decides what to do with them.

Embedding is what makes the blueprints under the workspace’s agents/ directory reachable outside a git checkout: lev add takes a local path, and an agents/ directory next to the executable is a layout no real install has, so without the bundle a user who downloads a release binary gets a working runtime and zero agents to run on it.

build.rs embeds every file of every blueprint via include_str! and generates the BUNDLED_AGENTS table included below. lev setup offers to install them; lev list reports them.

Structs§

BundledAgent
One blueprint embedded in the binary.

Enums§

AgentAction
What lev setup should do with one bundled blueprint, given what is currently installed.

Statics§

BUNDLED_AGENTS
Every blueprint shipped with this binary, sorted by name.

Functions§

install_bundled
Write one bundled blueprint into <agents_dir>/<name>/, replacing whatever is there.
installed_version
The installed version of name under agents_dir, if a readable manifest is there.
plan_agent_actions
Decide what to do with every bundled blueprint.
real_agents_dir_opt
The agents directory of the real environment, for a caller that has no test seam of its own.
stale_install_hint
Why an installed bundled blueprint would not load, when the reason is that it is old rather than that it is wrong.
stale_install_note
A note for a run about to start on an installed bundled blueprint that this binary ships a different version of.
stale_install_suffix
stale_install_hint as a suffix ready to append to an error message, or an empty string when there is nothing to say.