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§
- Bundled
Agent - One blueprint embedded in the binary.
Enums§
- Agent
Action - What
lev setupshould 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
nameunderagents_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_hintas a suffix ready to append to an error message, or an empty string when there is nothing to say.