News for hackers. Stuff that matters.

A comment on /story/47526486. Parent comment

Re: by andrew_zhong on Thursday March 26, 2026 @05:37AM (#47528375)
We do see fewer invalid JSONs on latest bigger LLMs but still can happen on smaller and cheaper models. There is also case when input is truncated or a required field not found, which are inherently difficult.

On XML vs JSON, I think the goal here is to generate typed output where JSON with zod shines - for example the result can type check and be inserted to database typed columns later

[ Parent | on HN ]
Re: by faangguyindia on Thursday March 26, 2026 @05:48AM (#47528445)
Thing is even with XML LLM will fail every now and then.

I've built an agent in both tool calling and by parsing XML

You always need a self correcting loop built in, if you are editing a file with LLM you need provide hints so LLM gets it right the second time or 3rd or n time.

Just by switching to XML you'll not get that.

I used to use XML now i only use it for examples in in system prompt for model to learn. That's all

[ Parent | on HN ]
Re: by andrew_zhong on Thursday March 26, 2026 @05:57AM (#47528488)
Agreed - in this project I did a one path sanitation to recover invalid optional / nullable fields or discard invalid objects in nested array.

I know multi path LLM approaches exist: e.g. generating JSON patches

https://github.com/hinthornw/trustcall

[ Parent | on HN ]