this is really very helpful. Thanks for sharing
The Vercel plugin on Claude Code wants to read your prompts
111–120 of 120 posts
Re: The Vercel plugin on Claude Code wants to read your prompts
#112[dead]
Re: The Vercel plugin on Claude Code wants to read your prompts
#113Engineer at Vercel here who worked on the plugin! We have been super heads down to the initial versions of the plugin and constantly improving it. Always super happy to hear feedback and track the changes on GitHub. I want to address the notes here: The plugin is always on, once installed on an agent harness. We do not want to limit to only detected Vecel project, because we also want to help with greenfield projects…
Bullshit justifications for bullshit decisions.
Re: The Vercel plugin on Claude Code wants to read your prompts
#114Earlier quoted context omitted.
OP here, ty for your response. Few reflections: 1. Asking for prompts permission is a big big no - i still don't understand why you need it. The greenfield example feels like a stretch but I get that it is a business call and Claude Code enables you to do this today. I am just more pissed with them here. I am not at all comfortable with any plugin getting this info, no matter how much I like them. 2. The way you ask…
For sure, I can see from your perspective how some of the measures we took were a little aggressive. And we're currently working on making it more explicit. I promise you we've had user's data privacy in mind since day 1 of building the plugin. Everything we collect is only used to improve the Vercel plugin, eg: seeing when skills are being triggered too often, when certain skills are not useful, when certain context…
More bullshit justifications to defend the indefensible, gross.
Re: The Vercel plugin on Claude Code wants to read your prompts
#115Earlier quoted context omitted.
[flagged]
Israel has a disproportionately large amount of tech companies for its size and he took one photo with their leader. I have no idea why everyone on the internet wants to endlessly seethe about this & personally attack Guillermo for it as if he’s endorsed their foreign policy or something
Be for real, he took a selfie with the leader of a country actively involved in genocide. You don’t do that if you don’t implicitly agree.
Re: The Vercel plugin on Claude Code wants to read your prompts
#116I still use Claude to code in a very stoneage way. I copy c code into the web site/desktop App and type in my prompt. Then i read the output and if i like it i copy paste it into my code. I always felt very old doing that way when things like Claude code exists. Now i fell somehow not so old. All this hacking into my private space using a develpment tool is insane. Also i do not use Git
Not using version control is just stupidity
Re: The Vercel plugin on Claude Code wants to read your prompts
#117Earlier quoted context omitted.
Just came to say (since the person you’re responding to has a different view of the world) that I agree with you that this is both a more accurate, and easier way to live. Assuming malice as the default sounds like a recipe for being very, very unhappy.
This attitude of ignoring what is true in favour of what makes you happy is exactly how corporations made up of mostly good people can do bad things.
Thank you, it's really crazy to be see "it's sad that you want truth when ignorance makes me happy" being upvoted on this platform. I suppose it's par for the course on a VC forum..
Re: The Vercel plugin on Claude Code wants to read your prompts
#118I still use Claude to code in a very stoneage way. I copy c code into the web site/desktop App and type in my prompt. Then i read the output and if i like it i copy paste it into my code. I always felt very old doing that way when things like Claude code exists. Now i fell somehow not so old. All this hacking into my private space using a develpment tool is insane. Also i do not use Git
Not using version control is just stupidity
i use SVN, Git isn't the only thing out there
Re: The Vercel plugin on Claude Code wants to read your prompts
#119Earlier quoted context omitted.
I’ll just say that as someone who was on the React team throughout these years, the drive to expand React to the server and the design iteration around it always came from within the team. Some folks went to Vercel to finish what they started with more solid backing than at Meta (Meta wasn’t investing heavily into JS on the server), but the “Vercel takeover” stories that you and others are telling are lies.
Gosh, Dan, in seeing your response here - I'm truly sorry I wrote this. While I still find opt-out telemetry distasteful and dangerous, I over-generalized to React in a hurtful way. You've been an incredible influence on me and I have the utmost respect for everything you've done. I've shown quite the opposite of respect in my writing, here. For whatever it's worth on the RSC front: I, and many others used to "if the…
Hey, appreciate the reply! I’m sorry for lashing out as well.
Re: protocol, I see where you’re coming from although I can also see the team perspective and I kind of like it the way it is. The team’s perspective is that this isn’t a “protocol” in the sense that HTTP or such is. It isn’t designed to have many implementations emitting it. It is an implementation detail of React itself for which React provides both the “writer” and the “reader”. Those are completely open source — none of the RSC frameworks need to know the actual wire format. They just use the packages provided by React to read and write. Keeping the protocol an implementation detail of React (rather than an “open format”) lets React evolve it pretty substantially between versions with zero concerns about backwards compat. Which is still quite useful at this stage.
When you’re concerned about wire format not being an open protocol, it’s because you’re imagining it would be useful for others to read and write. But this doesn’t really buy you anything. If you’re making an RSC framework, you should just use the React packages for reading and writing. And if you’re not, there’s no reason to use this format. Eg if you make an RSC-like framework in another (non-JS) language, it’s better for you to use your own wire format that’s more targeted to your use case.
Does this help clarify it?
(Note I do think it would be beneficial to document the current version for educational reasons, which is part of why I made https://rscexplorer.dev, but that’s separate from wanting it to be fixed in stone as protocols must be. I think the desire for it to be fixed is rooted in a misconception that frameworks like Next.js somehow “rely” on the protocol and thus have “secret knowledge”, but that’s false — they just use the React packages for it and stay agnostic of the actual protocol.)
Re: The Vercel plugin on Claude Code wants to read your prompts
#120OP here. update: all 4 identified issues in the blog are now fixed by the Vercel team.
https://akshaychugh.xyz/writings/png/vercel-plugin-telemetry...