Use Case
- You see, API calls and responses are oftentimes Json. When working on multi AI agent cooperation more of vanilla js style, it makes a lot of sense to look at Json directly. This ensures a "what you see is what you get" experience without hidden logic or unnecessary GUI bloat.
- Viewing Json directly have many advantagous such as instantly allowing you to alter the Json file of an AI conversation at any point in time without the use of bloat like GUI.
- It would greatly benefit developers to be able to directly read AI outputs (which heavily use Markdown and LaTeX) right inside an extension like JSON Hero, instead of being forced to build or use a separate GUI just to read the chat history.
Proposed Solution
When hovering over a text field or clicking one, if a Markdown renderer renders it as non plain text, it should be rendered as Markdown with LaTex support.
Use Case
Proposed Solution
When hovering over a text field or clicking one, if a Markdown renderer renders it as non plain text, it should be rendered as Markdown with LaTex support.