跳过导航
In-browser annotations are coming to Polyscope 🔥
0:00 / 5:08

In-browser annotations are coming to Polyscope 🔥

Marcel Pociot 🧪

@marcelpociot7.1万 位关注者

在 X 上查看
82 个赞下载原帖

13,328 次观看

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 🚀

21 条评论

评论来自 X (Twitter) 上的原帖

  • Marcel Pociot 🧪 的头像

    @marcelpociot

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

    5 个赞

  • Jordan Dalton 的头像

    @jordankdalton

    @getpolyscope Very powerful!

    3 个赞

  • Josh Cirre 的头像

    @joshcirre

    @SRWieZ @getpolyscope Love it!

    2 个赞

  • ★ Dhruva 的头像

    @_Dhruva

    @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?

    1 个赞

  • Marcel Pociot 🧪 的头像

    @marcelpociot

    @getpolyscope With the extension?

    1 个赞

  • ★ Dhruva 的头像

    @_Dhruva

    @getpolyscope Sorry! yes the chrome extension.

  • Bobby Bouwmann 的头像

    @bobbybouwmann

    @getpolyscope There should be a delete button Say hi

    1 个赞

  • Kay 的头像

    @kayintveen

    @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

    1 个赞

  • Elie Steinbock 的头像

    @elie2222

    @getpolyscope very cool. i have to try this

    1 个赞

  • Owen Melbourne 的头像

    @OwenMelbz

    @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

    1 个赞

  • Logan Craft 的头像

    @LivewireLogan

    @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 :)

    1 个赞

  • Michael Dyrynda 的头像

    @michaeldyrynda

    @getpolyscope Very cool!

  • David Joos 的头像

    @DavidJoos6

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

  • Marcel Pociot 🧪 的头像

    @marcelpociot

    @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

    1 个赞

  • David Joos 的头像

    @DavidJoos6

    @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 😂

  • Marcel Pociot 🧪 的头像

    @marcelpociot

    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

    1 个赞

  • Chat Data 的头像

    @truechatdata

    @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.

  • Uriah 的头像

    @codeitlikemiley

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

  • United Records 的头像

    @RecordsUni63959

    @getpolyscope interesting

  • Asaf Mazuz 的头像

    @MazuzAsaf

    @getpolyscope Great feature 😄