Mael
It's also available for Ollama https://ollama.com/blog/structured-outputs and Anthropic https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/increase-consistency
Thank you! It might actually need some cleaning / correction (in particular the JSON parsing and validation and error handling) because I (mostly) did it with Claude which isn’t perfect,...
@Beingpax we can collaborate on it! But since you're the main maintainer, I'm not exactly sure what's your preferred approach to coding / what kind of libs you want to...
also I added a IS_DEVELOPMENT compiler flag to compile the "license" feature only in Release so I can dev without nagging... but perhaps you have a better way to do...
Perfect, add me there, should be mael_oulipo Message ID: ***@***.***>
I haven't had the time to really complete this task, so now the code has drifted enough that I guess it would make more sense to scrap this PR and...
Sure, that’s also doable through bash script (basically have a MCP server running on your laptop, and just have a bash script piping your query directly to the script)
Very nice!
No I mean, that's the error I'm getting seems to be because it's confused and trying to use x86_64 instead of amd64
Indeed! I think that specifying an explicit start/end could be an easy was to make it much more predictible, eg `timestamp in @someRange` `timestamp > @someRange.start` `timestamp < @someRange.end`