Getting started guidance

[agrath]

Hi Cole,

I'm on Windows, and came here from a tweet that was shared.
I've tried to get this running and I'm having some problems.

As this project seems to be unix only, the scripts don't support windows directly, I used wsl (windows subsystem for linux)
I have set up node, and worked through this

./install.sh did not work successfully, so I cd into each subfolder (extension, mcp-server, and server) then ran npm install and the relevant build commands referenced in readme.md

For the extension, manifest.json was not created so claude suggested:

ENTRY=content npx vite build
ENTRY=background npx vite build
ENTRY=popup npx vite build

Then copy assets again:
cp manifest.json dist/
cp src/content/styles.css dist/src/content/
cp -r icons dist/

I was then able to get the extension loaded into Chrome

I then started the server (via wsl again) with node server.js in the server subfolder

I can see the extension is connected as I am seeing "Received: ping" repeatedly

But, in the extension, I have a few problems:

1. when I try to "browse" the project folder, I get a browse dialog and select the path to my project source:

Choosing my src folder, I then see: /Users/coleschaffer/Desktop/src as the folder (which is incorrect)

2. when I try to "enable on current page" with the switch, it turns on, but I am unable to click on any elements, to trigger it, and when I re-open the extension panel, enable has toggled back

Subsequently, clicking on elements does not work.

3. Am I correct in understanding that the feedback submitted via this tool makes it way to my current claude cli instance via MCP for action?

As it seems from your docs & repo that you're on macos, I expect that a lot of these problems are due to me being on windows, but I'd appreciate any help or guidance you can provide.

I can obviously open a claude session against a fork of your repo and try and get my own claude to debug and fix this, but before I do that, I want to align with your goals for this project

[agrath]

I got carried away and got claude involved, resulting in this PR:

#2

Referencing the issue I reported:

1. the build is now working for me in wsl, I think claude may have fixed the scripts for me
2. the server was running but not working correctly on windows, this is corrected
3. after getting things working so the browser extension talked to the server, I realised how the tool was meant to work with the standalone server (due to errors in the console) indicating that the workflow would not work for windows or for me. Using claude, I then refined the process to support both windows and my own style of working

Happy to discuss!