Ship
Changes requested
finally done!
ive added uh getting active tab contents for the purpose of summarizing text or whatever
devlog 6
The MCP client has a BUNCH of new features.
- Opening tabs
- Closing tabs
- Unloading tabs
- Grouping tabs
- Changing color and name of groups
- History access (opt-in)
Happy with how it’s turning out still. I think its time to fix more bugs now. if i figure out the situation on keeping websocket open w/ the service worker, i might make this work for firefox. Its been tough tho, so much bugs…
Devlog 5
Created a quick install python script! Right now it only supports adding the mcp to claude code and opencode, and it supports all macos, windows and linux! (someone test it on macos and windows for me pls..)
As for the MCP, grouping a tab now returns the group ID normally, and now you can change title of group! Still dont know which customization features to add.. but ill figure it out hopefully (i took 4h 58m because i have never created an installation script, chrome extension or even a node.js server in general.. and i learned alot)
Devlog 4
finally!!!!!!!!!! The extension now handles closed connections, and reconnects… and the whole server is coded in node.js without python.
Now that the app completely works, the only thing left for me is to add more customization and etc features. Right now there is: getting tabs and their titles, and grouping them..
If you want to, suggest any ideas.
Devlog 3
Finally finished the core MCP! Really fragile.. but it works. fsr some hours are marked as ai coding even though i did not vibecode the MCP at all :( (because i was testing the MCP using opencode) but the MCP works enough. The server is a bit fragile and will hope for a better server in the future.
dev log 2….
ive recoded how the server works, and made the service worker in my extension keepalive. The project is starting to come together at least. Gonna work on the MCP finally next time.
first devlog!!
None of the MCP works yet, but i have gotten the communication between browser and websocket server to work.
I might switch to node.js for the mcp server as i personally think it’s easier to handle websocket there.
to be fair it is my first time creating a chrome extension and doing anything with websocket in general..
