In-browser annotations are coming to Polyscope 🔥 Select any element in your browser → Polyscope will create a new workspace → Claude, Codex or Cursor knows what to change Zero copy paste Zero complex configuration Built with the Polyscope JS SDK 🚀

The extension is not yet published on the extension marketplace, but you can already give it a try:

@getpolyscope Very powerful!

@SRWieZ @getpolyscope Love it!

@getpolyscope Thanks, Marcel. This is very powerful. I’m receiving the following message: “The route api/workspaces could not be found.” How can I get this working?

@getpolyscope With the extension?

@getpolyscope Sorry! yes the chrome extension.

@getpolyscope There should be a delete button Say hi

@getpolyscope zero copy paste is the dream. context switching to grab a selector and paste it into a prompt kills the flow. this is the kind of friction that sounds tiny until you realize how much mental overhead it adds up to

@getpolyscope very cool. i have to try this

@getpolyscope Are you able to explain the frontend workflow? Eg say you got a vite/nextjs website. And you’ve asked Polyscope to make some changes, how are you meant to view the changes in the browser to check the results? The git workplaces means that your dev sever/bundler misses the changes

@getpolyscope I have made an issue on github for the "The route api/workspaces could not be found." issue. Looking forward to using this once this is resolved :)

@getpolyscope Very cool!

@getpolyscope I don’t fully get it. Where is the leverage compared to cc?

@getpolyscope You can use this with remote servers running on VPS servers and use it with a variety of providers like Cursor, Claude or Codex

@getpolyscope Ok interesting for Teams. But what about indie hackers with cc and /remote-control or /channels? Sorry for asking that stupid but people seem hyped and I don’t wanna a miss thing 😂

Polyscope allows you to quickly work on multiple workspaces of the same repository at once and then easily review the code, create PRs, merge etc. one of the main differences is that we use copy on write clones for pretty much instant workspace creation with all dependencies (node, composer etc) being immediately available without taking up extra disk space

@getpolyscope This is a strong UX move. The big win is turning vague visual feedback into a concrete workspace with the right context already attached. Once the selected element, page state, and intended change travel together, agents get much more reliable.

@getpolyscope this is only possible for web app , i doubt this works with desktop app or mobile

@getpolyscope interesting

@getpolyscope Great feature 😄

@getpolyscope 🔥🔥🔥