You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m looking at TOON (Token-Oriented Object Notation) as a token-efficient, lossless alternative to JSON for structured payloads sent to LLMs: https://github.com/toon-format/toon#readme
Agent Framework often feeds structured data into prompts (tool outputs, RAG results, memory/state). JSON can get pretty token-heavy, and TOON seems designed exactly for this boundary (nested structure + tabular arrays for uniform objects).
Question:
Would you be open to an optional TOON formatter/serializer (JSON remains default) to reduce tokens/cost for large structured context?
Where would you see the best integration point in Agent Framework (middleware hook, tool result formatting, memory/context serializer)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I’m looking at TOON (Token-Oriented Object Notation) as a token-efficient, lossless alternative to JSON for structured payloads sent to LLMs:
https://github.com/toon-format/toon#readme
Agent Framework often feeds structured data into prompts (tool outputs, RAG results, memory/state). JSON can get pretty token-heavy, and TOON seems designed exactly for this boundary (nested structure + tabular arrays for uniform objects).
Question:
Refs:
Beta Was this translation helpful? Give feedback.
All reactions