> github.com
pour one out for the GitLab hosted projects, or its less popular friends hosted on bitbucket, codeberg, forgejo, sourceforge, sourcehut, et al. So dumb.
(b) it's an allowlist rule, not rocket science
(c) where's all this mythical "agent gonna do all the things for me" world?
If you're in a hurry: via mcp servers.
If you're not in a hurry, more and more of these kind of capabilities will end up getting integrated directly.
Claude already has the ability to make or edit files, as artifacts in the web interface, and with the Write tool in Code.
Editorializing, in my understanding, is introducing spin or opinion, or cherry-picking a detail to highlight only one aspect of a story. It seems to me that this edit doesn't do that because it actually broadens the information in the title and corrects a misleading impression given by the original. The only way I could see this being a bad edit is if it's not actually true that Claude now has access to a server-side container environment. If it's accurate then it surely includes the file-creating-and-editing stuff that was spoken about before, along with a lot more important information—arbitrary computation is rather more than just editing files! No?
> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.
The word "container" doesn't even appear in the original post from Anthropic, let alone "server-side container environment."
Editorializing, on the other hand, is about adding clickbait or bias.
I reverse-engineered it a bit, figured out its container specs, used it to render a PDF join diagram for a SQLite database and then re-ran a much more complex "recreate this chart from this screenshot and XLSX file" example that I previously ran against ChatGPT Code Interpreter last night.
Here's my review: https://simonwillison.net/2025/Sep/9/claude-code-interpreter...