Feature Request: Integration with Mirascope Framework

[ramon-prieto]

Background

Currently, the weave.op() decorator does not capture internal Mirascope calls or their associated costs. This creates a gap in observability.

Current Behavior

• Internal Mirascope calls are executed but not logged
• Cost information for these operations is not tracked

Desired Behavior

• Log all internal Mirascope calls with their:
  • Operation name
  • Input/output
  • Execution time
  • Cost (tokens used)
• Provide ability to trace the full call hierarchy including nested Mirascope operations

[andrewtruong]

Hey @ramon-prieto , we don't have this on our roadmap atm, but happy to accept contrib!

Here's an example external contrib from NotDiamond:
#2606