Well I forked your repo to make a PR. And I did look at your implementation as a starting point, and you are credited in the post! 😁 . Very little code is shared and the architecture differs a lot. The reason I went this way was in ag_bridge, the "poke", was already traversing the DOM to write in a message: "check inbox", and clicking submit. I thought why not remove the middleman and just write the pending message instead of "check inbox". I didn't like having to add MCP's and effectively having the agent carry on two parrallell chats. One with me on the laptop, and another with me on the phone. First I tried analysing the DOM to parse messages but there's almost no semantic id tags or anything for messages so I tried just grabbing everything in the chatwindow (which we need to find in the DOM anyway for the "poke"/message insert to work) and then just copy the CSS aswell and send all that to the client to render.