Pinned tools
Each L80 release pins every Python tool it runs to one git commit, so a given L80 version always runs the same tool code. All of them are free to use with no token.
What is pinned
| tool | runs | pinned in 1.0.0 | override |
|---|---|---|---|
| BetterBench | betterbench | v0.6.1 · f72bb90 | L80_BETTERBENCH |
| bbvastl80 | bbvastl80 | v0.1.0 · d8ed73f | L80_VAST |
| pwdet | pwdet | v0.1.0 · 85f3ead | L80_PWDET |
| AI command dashboard | ai-dashboard | v0.1.0 · 3cc1575 | L80_DASHBOARD |
The pins live in a manifest embedded in the binary, so L80 update is also how a new version of a tool arrives.
How a tool is found
L80 uses the first of these that works:
- the tool's override variable, such as
L80_PWDET, used without a version check; - a copy on your PATH that is at least the pinned version;
- the pinned commit, via
uvx --from <pkg> @ git+<repo>@<commit> <exe>(uv caches the build); - an older copy on your PATH, with a warning.
Installing uv is the only prerequisite. If L80 cannot run a tool it exits 11 (E_TOOL_UNAVAILABLE) and says how to fix it. Once a tool starts, its own exit status is returned unchanged.
Commands
$ L80 tools list # each tool and the version this release pins$ L80 tools check # how each tool resolves on this machine$ L80 tools prefetch # download and build the pinned tools now$ L80 tools path betterbench # the exact command L80 would run$ L80 tools run pwdet --help # run any pinned tool with its arguments untouched