After a module is compiled, is it possible to retrieve the optimized prompt?

[maximepeabody]

How can I output the actual prompt that the module compiled/optimized? I'm using LLMs in typescript so I can't use the module itself.

[detaos]

You can always use lm.inspect_history(n=1) after running the compiled program to see the prompt itself.

[RLinnae]

Can you use the compiled prompt as a starting point for future optimization runs?

Ie can you run the SignatureOptimizer. Then use the optimized signature in. BootstrapFewShot?

Or can you run a second iteration of the SignatureOptimizer with slight variation, using the original output as the starting point?

Ok r do we always start from scratch when compiling?

[detaos]

You can definitely do a second optimization run starting from the 1st optimized prompt. You can start from wherever you want 😄

[jingnanzhou]

can you provide sample code how to reload the compiled status?

[lebsral]

You can save the optimized prompt. And then load it later.
https://dspy-docs.vercel.app/docs/building-blocks/optimizers#saving-and-loading-optimizer-output

This works on all optimizers (except COPRO?)