You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HTTP static --tools validation falls back to the full static inventory #2933
For the current main revision, the HTTP static-inventory path handles an
invalid EnabledTools entry differently from the documented startup behavior.
The static builder returns the existing unknown-tool error, but
buildStaticInventory substitutes the full local tool/resource/prompt inventory.
The default HTTP inventory factory then uses that widened static universe.
This is inconsistent with the README and configuration troubleshooting guide,
which say that invalid --tools names cause startup failure.
Construct the current HTTP handler and default inventory path with
in-memory request/response objects only.
Compare the mixed configuration above with a valid
get_file_contents-only control.
Observe that the valid control omits create_repository, while the mixed
configuration carries create_repository into the local tools/list response
through the current default factory path.
The fixture used inert dependencies and did not create a listener, network
connection, external client, account, or tool invocation.
Expected vs actual behavior
Expected: an invalid static EnabledTools entry preserves the typed unknown-tool
error and prevents the HTTP static inventory from being constructed.
Actual: the static helper replaces that error with the full static universe,
which makes the malformed configuration broader than its valid one-tool
control in the local fixture.
Logs
No production logs were collected. The source-bound local evidence and a
focused candidate patch are ready to share in a follow-on pull request if this
behavior is confirmed as unintended.
Activity
gerardomarci60-blip commentedon Aug 11, 2026
`