Emit events when modules fail to load silently #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running
amplifier updatewhile developing a local module the session started but the module silently failed to load. After an attempted tool call the session raises:This PR emits a
module:load_error eventwhen providers, tools, or hooks fail to load. The event appears inevents.jsonlwith the module ID, type, and actual error message, making failures visible withoutchanging the existing graceful degradation behavior.
Event payload
{"module_id": "my-tool", "module_type": "tool", "error": "No module named 'aiohttp'"}Changes
Follow-up
A separate PR could preserve
ImportError/ModuleNotFoundErrorspecifically inloader.pyrather than catching all exceptions - this would improve diagnostics by keeping the actual error type instead of converting everything to a generic string.