Website annotation like in pi-annotate

[JulianS-Uni]

Can you implement a website annotation similar to what pi-annotate is doing? I like pi-annotate but having the chrome extension is clunky and the extension does not work when you are coding on a remote machine over ssh. Plannotator just works out of the box.

I thought about loading the website (url) to a new frame on the annotation overview. From there the annotation overview should recognice DOM-Elements and enable to comment on them. The report should include the DOM elements, id and class for the agent to recognize it.

[backnotprop]

This is definitely a cool idea. Though, a lot of big websites will block DOM access through iframe.

• For your local apps, no problem, and can work today. If this is your main use case. It's easy
• Otherwise, to get around this, you either need like a Chrome extension or to launch a separate Chrome browser with debug mode enabled or have a desktop app.

Questions:

1. Is your main use case any website, or your local apps.

2. Is a desktop app a non-starter? I've been testing one of the works that keeps planning and review sessions alive long term.It would also enable this feature.

3. Also, random: I'm just curious. Can you let me know what your remote SSH setup is for Plannotator?

[JulianS-Uni]

1. My use case would be my local apps. I wasn't aware of the problem you described and just thought it would be a nice extra to be able to use any website as reference or mockup.
2. I would be fine with a desktop app I think.
3. I am just using vscode with the remote explorer extension which seems to tunnel the localhost automatically. Vscode is installed on my local machine and my code and plannotator alongside with pi is installed on the remote.
   But I guess something like ssh -L 3000:localhost:3000 user@192.168.1.100 would also work, although I haven't tried it for plannotator.

[EXDEV-oss]

Hey, I came across your project and checked out some of the infrastructure/backend setup you’re working on. I mainly help developers test backend reliability, deployment flow, API behavior, auth systems, scaling issues, edge-case failures, and launch readiness before production release.

If you ever need another technical eye for testing or infrastructure validation during launch stages, I’d be interested in helping out. Your project looks promising.