Recommends Tune.

Transcript context

…I'll say no. It's it's it's really simple. It's basically you rewrite your text as a caveman. It's like, and, you know, you know, Nissan not like Burrito. You know? Like, if you do that it's so retarded. But if you do that, you catch your tokens by, like, 20 or 30%, which is good. You know? And so cutting your tokens, like, it'll be it'll make your system faster and make your system cheaper and make it'll make retrieval more more accurate. It'll just be better with basically no loss of of information or context. You know? If you the the reason we've not done that is because we actually do care about the maintain ability, like, the the auditability of the system. And so we did that. Every metric went up. It was awesome. And then the files in the file system look really dumb. And so it doesn't make us look good, you know, to enterprise customers. Like, why do my memory files look like that? But it it works. Actually, similar. You know, those like, there's, like, a bunch of those techniques to just compress of context. Have you heard of a Toon, t o o n? It's it's it's a sort of, like, JSON alternative that's made for agents. That's, like, I think it's, like, 20 or 30% more token efficient than JSON. JSON is actually not that token efficient. So Tune Tune works better. It's 20 or 30. So this work this is less important for, like, memory agents, but it's just I recommend everyone, like, makes their agent use Tune instead of JSON and have, like, a a a Tune passing middleware between your agent and its actions. Like, no action should expose Tune to to to the agent. Like, every every agent every action should expose Yeah. Interesting. I have to check out this Tune format. I've just used YAML, which also is motivated by similar…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.