Daniel Demmel

I'm also getting this after updating the version, not sure why? I'm only setting 2 callbacks on the top level: ``` litellm.success_callback = ["langfuse"] litellm.failure_callback = ["langfuse"] ``` Another thing...

This is the nth issue opened after all the previous ones got auto-closed without resolution. Can someone please address it? If you really have to waste those tokens on the...

Oh and these even mess up CC's own summary generation: ```jsonl {"type":"summary","summary":"Claude Code CLI Documentation Task","leafUuid":"2b7394b6-d370-4a65-a777-0094c76c0ecd"} {"type":"summary","summary":"CSV data labeling implementation completed successfully","leafUuid":"ddfb079c-148a-4f2e-a026-3fb67be197ed"} {"type":"summary","summary":"Claude Code Codebase Navigation Warmup","leafUuid":"4b539575-1024-4ba4-85bf-2bc32b44e1bd"} {"type":"summary","summary":"Fixed Gemini API...

Oh man, the VS Code plugin (2.0.35) is even unable to render my first message now because of these:

I lost my day to this bug too... **In our case it's the last `@observe()` decorator overriding the trace name, even when `name` isn't passed because of the implicit `func.__name__`...

I managed to work around it adding an empty job (span) with the same name as the workflow and manually propagating and setting input and output values which is quite...

It happens to me too quite a lot with Gemini 2.5 Pro, wish there was an option to fall back to write_to_file immediately or a way to experiment with diff...