# Expose API for browser extensions

**URL:** https://discuss.codemirror.net/t/expose-api-for-browser-extensions/5864
**Category:** v6
**Created:** [March 3, 2023, 1:20pm UTC](https://discuss.codemirror.net/t/expose-api-for-browser-extensions/5864 "2023-03-03T13:20:42Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![marijn](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/marijn/32/136_2.png) [@marijn](https://discuss.codemirror.net/u/marijn)
#### Post date: [March 20, 2023, 7:46am UTC](https://discuss.codemirror.net/t/expose-api-for-browser-extensions/5864/8 "2023-03-20T07:46:50Z")

</div>

> [@timdown](#):
>
> For widely-used, non-Overleaf-specific tools such as Grammarly, it seems preferable to have a generic CM6 API;

No, what I’m talking about is for these tools to define a way in which they _want_ to be able to approach 3rd party editor components, so that, instead of them hard-coding some invasive kludges to work with specific libraries, the libraries can interact with them on their own terms.

But I realize that’s probably too much to ask.

---

_[View the full topic](https://discuss.codemirror.net/t/expose-api-for-browser-extensions/5864)._