ddworken
Joined 12 years ago
Karma
368
Submissions
82
Member since
Oct 23
Recent submissions
Comment · 1 day ago
Dworken from Anthropic here, 2.1.313 was never published on OpenVSX, the VS Code marketplace, or on any of our official hosts. The malicious actor here had published a fake version of this extension on Cursor's marketplace. In order to disambiguate, we made sure our next update was 2.1.314.
Comment · 1 day ago
Dworken from Anthropic here, this did not involve a compromise of any Anthropic systems. A malicious actor used access to Cursor’s marketplace to publish a tampered extension targeting Cursor's users, we were not involved with building, publishing, or hosting this. The versions on our official channels including VS Code and OpenVSX are not affected and this only impacts Cursor users.
Comment · 1 day ago
Dworken from Anthropic here: This only impacted the extension as it was hosted on the Cursor marketplace. It did not impact the official VS Code extension marketplace or OpenVSX. Users of Claude Code on VS Code are not impacted by this issue.
Comment · 1 day ago
Dworken from Anthropic here: This only impacted the extension as it was hosted on the Cursor marketplace. It did not impact the official VS Code extension marketplace or OpenVSX. Users of Claude Code on VS Code are not impacted by this issue.
Comment · 1 day ago
Dworken from Anthropic here, 2.1.313 was never published on OpenVSX, the VS Code marketplace, or on any of our official hosts. The malicious actor here had published a fake version of this extension on Cursor's marketplace. In order to disambiguate, we made sure our next update was 2.1.314.
Comment · 1 day ago
Dworken from Anthropic here, 2.1.313 was never published on OpenVSX, the VS Code marketplace, or on any of our official hosts. The malicious actor here had published a fake version of this extension on Cursor's marketplace. In order to disambiguate, we made sure our next update was 2.1.314.
Comment · 1 day ago
Dworken from Anthropic here, that is correct: This only impacted the extension as it was hosted on the Cursor marketplace. It did not impact the official VS Code extension marketplace or OpenVSX. Users of Claude Code on VS Code are not impacted by this issue.
Comment · 1 day ago
Dworken from Anthropic here, I just want to be clear: OpenVSX was not impacted in this incident, the impacted system was only the Cursor marketplace that they host. We have confirmed that no Anthropic systems or employee devices are involved in this.
Comment · 1 day ago
Dworken from Anthropic here, yes this is correct. This is a third-party marketplace that we are not involved in owning, maintaining, deploying, or reviewing.
Comment · 1 year ago
I actually made a CLI tool (https://github.com/ddworken/hishtory) that automatically binds to Control+R to support both history searching and AI queries (by prefixing queries with `?`).
Here's the prompt engineering I did: https://github.com/ddworken/hishtory/blob/master/shared/ai/a...
Comment · 2 years ago
I'll also plug my project [0] as another alternative that supports syncing (similar to Autumn) and also has a number of powerful customization features (e.g. custom columns to collect arbitrary metadata with each command, like the git remote) and an AI shell command generator.
Comment · 3 years ago
If you're interested in something more actively maintained, and with cross-machine syncing, two recent alternatives are:
* github.com/ddworken/hishtory * github.com/ellie/atuin
Disclaimer: I'm the maintainer of the first one.
Comment · 4 years ago
Ah, thank you commenting on this! This is absolutely unintentional and was the fault of a missing comment in the bash script (that I didn't notice because I generally use zsh). See https://github.com/ddworken/hishtory/commit/72ff95ab8b23c3be... and if you run `hishtory update` it should be all fixed.
[email protected]