▲ | felarof 2 days ago | |||||||||||||||||||||||||
Yes, eventually we think there is more value of owning the entire stack than just be a MCP connector. Few ideas we were thinking of: integrating a small LLM, building MCP store into browser, building a more AI friendly DOM, etc. Even today, we use chrome's accessibility tree (a better representation of DOM for LLMs) which is not exposed via chrome extension APIs. | ||||||||||||||||||||||||||
▲ | pickpuck 2 days ago | parent | next [-] | |||||||||||||||||||||||||
> building a more AI friendly DOM You might consider the Accessibility Tree and its semantics. Plain divs are basically filtered out so you're left with interactive objects and some structural/layout cues. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | xnx a day ago | parent | prev [-] | |||||||||||||||||||||||||
> Few ideas we were thinking of: integrating a small LLM Chrome has a built-in LLM: https://developer.chrome.com/docs/ai/built-in |