Untitled conversation
- User
[BUG] @Tool methods not inherited from superclas
@Toolmethods not inherited from superclass. I think this is a bug as this is something that should work.I didn't 100% verify this, but my inherited tools weren't being called and the LLM was stating that it didn't know what tool to call. Once I put the tool methods back in the concrete class, things worked, so I'm assuming that this bug report is true.
This should be done in LC4J too if it already doesn't work there.
Interface
No new interfaces are introduced.
- Assistant
I’ll trace how tool methods are discovered, reproduce the inheritance gap with a focused test, then patch and run the relevant module tests.
- Assistant
The discovery path uses
getDeclaredMethods(), so it stops at the concrete class in both the public specification utility and AI-service registration. I’m centralizing hierarchy-aware method lookup so discovery and legacy execution stay consistent, with overridden methods de-duplicated. - Assistant
The implementation now covers all three affected paths, and the new tests verify both discovery and actual invocation from a subclass. The focused reactor test is compiling the core and service modules now.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →