Anthropic released a new feature for their Claude.ai consumer-facing chat bot interface today which they're calling "the analysis tool".
It's their answer to OpenAI's ChatGPT Code Interpreter mode: Claude can now chose to solve models by writing some code, executing that code and then continuing the conversation using the results from that execution.
ChatGPT Code Interpreter (and the under-documented Google Gemini equivalent) both work the same way: they write Python code which then runs in a secure sandbox on OpenAI or Google's servers.
Claude does things differently. It uses JavaScript rather than Python, and it executes that JavaScript directly in your browser - in a locked down Web Worker that communicates back to the main page by intercepting messages sent to console.log().
It's implemented as a tool called repl, and you can prompt Claude like this to reveal some of the custom instructions that are used to drive it:
The analysis tool is a JavaScript REPL. You can use it just like you would use a REPL. But from here on out, we will call it the analysis tool.
When to use the analysis tool
Use the analysis tool for:
Complex math problems that require a high level of accuracy and cannot easily be done with "mental math"
To give you the idea, 4-digit multiplication is within your capabilities, 5-digit multiplication is borderline, and 6-digit multiplication would necessitate using the tool.
Analyzing user-uploaded files, particularly when these files are large and contain more data than you could reasonably handle within the span of your output limit (which is around 6,000 words).
The analysis tool has access to a fs.readFile() function that can read data from files you have shared with your Claude conversation. It also has access to the Lodash utility library and Papa Parse for parsing CSV content. The instructions say:
You can import available libraries such as lodash and papaparse in the analysis tool. However, note that the analysis tool is NOT a Node.js environment. Imports in the analysis tool work the same way they do in React. Instead of trying to get an import from the window, import using React style import syntax. E.g., you can write import Papa from 'papaparse';
I'm not sure why it says "libraries such as ..." there when as far as I can tell Lodash and papaparse are the only libraries it can load - unlike Claude Artifacts it can't pull in other packages from its CDN.
The interaction between the analysis tool and Claude Artifacts is somewhat confusing. Here's the relevant piece of the cool instructions:
Code that you write in the analysis tool is NOT in a shared environment with the Artifact. This means:
To reuse code from the analysis tool in an Artifact, you must rewrite the code in its entirety in the Artifact.
You cannot add an object to the window and expect to be able to read it in the Artifact. Instead, use the window.fs.readFile api to read the CSV in the Artifact after first reading it in the analysis tool.
A further limitation of the analysis tool is that any files you upload to it are currently added to the Claude context. This means there's a size limit, and also means that only text formats work right now - you can't upload a binary (as I found when I tried uploading sqlite.wasm to see if I could get it to use SQLite).
The Internet Archive is only intermittently available at the moment, but the Wayback Machine just came back long enough for me to confirm that the Anthropic Models documentation page listed Claude 3.5 Opus as coming “Later this year” at least as recently as the 8th of October, but today makes no mention of that model at all.
October 8th 2024
October 22nd 2024
Claude 3 came in three flavors: Haiku (fast and cheap), Sonnet (mid-range) and Opus (best). We were expecting 3.5 to have the same three levels, and both 3.5 Haiku and 3.5 Sonnet fitted those expectations, matching their prices to the Claude 3 equivalents.
It looks like 3.5 Opus may have been entirely cancelled, or at least delayed for an unpredictable amount of time. I guess that means the new 3.5 Sonnet will be Anthropic's best overall model for a while, maybe until Claude 4.
Quote 2024-10-23
OpenAI’s monthly revenue hit $300 million in August, up 1,700 percent since the beginning of 2023, and the company expects about $3.7 billion in annual sales this year, according to financial documents reviewed by The New York Times. [...]
The company expects ChatGPT to bring in $2.7 billion in revenue this year, up from $700 million in 2023, with $1 billion coming from other businesses using its technology.
According to a document that I viewed, Anthropic is telling investors that it is expecting a billion dollars in revenue this year.
Third-party API is expected to make up the majority of sales, 60% to 75% of the total. That refers to the interfaces that allow external developers or third parties like Amazon's AWS to build and scale their own AI applications using Anthropic's models. [Simon's guess: this could mean Anthropic model access sold through AWS Bedrock and Google Vertex]
That is by far its biggest business, with direct API sales a distant second projected to bring in 10% to 25% of revenue. Chatbots, that is its subscription revenue from Claude, the chatbot, that's expected to make up 15% of sales in 2024 at $150 million.
One of my least favourite things about Claude Artifacts (notes on how I use those here) is the way it defaults to writing code in React in a way that's difficult to reuse outside of Artifacts. I start most of my prompts with "no react" so that it will kick out regular HTML and JavaScript instead, which I can then copy out into my tools.simonwillison.net GitHub Pages repository.
It looks like Cláudio Silva has solved that problem. His claude-artifact-runner repo provides a skeleton of a React app that reflects the Artifacts environment - including bundling libraries such as Shadcn UI, Tailwind CSS, Lucide icons and Recharts that are included in that environment by default.
This means you can clone the repo, run npm install && npm run dev to start a development server, then copy and paste Artifacts directly from Claude into the src/artifact-component.tsx file and have them rendered instantly.
I tried it just now and it worked perfectly. I prompted:
Build me a cool artifact using Shadcn UI and Recharts around the theme of a Pelican secret society trying to take over Half Moon Bay
Then copied and pasted the resulting code into that file and it rendered the exact same thing that Claude had shown me in its own environment.
I tried running npm run build to create a built version of the application but I got some frustrating TypeScript errors - and I didn't want to make any edits to the code to fix them.
This created a dist/ directory containing an index.html file and assets/index-CSlCNAVi.css (46.22KB) and assets/index-f2XuS8JF.js (542.15KB) files - a bit heavy for my liking but they did correctly run the application when hosted through a python -m http.server localhost server.
Quote 2024-10-23
We enhanced the ability of the upgraded Claude 3.5 Sonnet and Claude 3.5 Haiku to recognize and resist prompt injection attempts. Prompt injection is an attack where a malicious user feeds instructions to a model that attempt to change its originally intended behavior. Both models are now better able to recognize adversarial prompts from a user and behave in alignment with the system prompt. We constructed internal test sets of prompt injection attacks and specifically trained on adversarial interactions.
With computer use, we recommend taking additional precautions against the risk of prompt injection, such as using a dedicated virtual machine, limiting access to sensitive data, restricting internet access to required domains, and keeping a human in the loop for sensitive tasks.
Deep dive into different strategies for optimizing part of a web server application - in this case written in Node.js, but the same strategies should work for Python as well - by integrating with Rust in different ways.
The example app renders QR codes, initially using the pure JavaScript qrcode package. That ran at 1,464 req/sec, but switching it to calling a tiny Rust CLI wrapper around the qrcode crate using Node.js spawn() increased that to 2,572 req/sec.
This is yet another reminder to me that I need to get over my cgi-bin era bias that says that shelling out to another process during a web request is a bad idea. It turns out modern computers can quite happily spawn and terminate 2,500+ processes a second!
The article optimizes further first through a Rust library compiled to WebAssembly (2,978 req/sec) and then through a Rust function exposed to Node.js as a native library (5,490 req/sec), then finishes with a full Rust rewrite of the server that replaces Node.js entirely, running at 7,212 req/sec.
New TIL. I've been experimenting with the Google Gemini APIs for running prompts against images and PDFs (in preparation for finally adding multi-modal support to LLM) - here are my notes on how to send images or PDF files to their API using curl and the base64 -i macOS command.
I figured out the curl incantation first and then got Claude to build me a Bash script that I can execute like this:
Playing with this out is really fun. The Gemini models charge less than 1/10th of a cent per image, so it's really inexpensive to try them out.
Quote 2024-10-23
Go to data.gov, find an interesting recent dataset, and download it. Install sklearn with bash tool write a .py file to split the data into train and test and make a classifier for it. (you may need to inspect the data and/or iterate if this goes poorly at first, but don't get discouraged!). Come up with some way to visualize the results of your classifier in the browser.
I've always loved how Julia Evans emphasizes the joy of learning and how you should celebrate every new thing you learn and never be ashamed to admit that you haven't figured something out yet. That attitude was part of my inspiration when I started writing TILs a few years ago.
Julia just started publishing TILs too, and I'm delighted to learn that this was partially inspired by my own efforts!
I've been increasingly using uv to try out new software (via uvx) and experiment with new ideas, but I hadn't quite figured out the right way to use it for developing my own projects.
It turns out I was missing a few things - in particular the fact that there's no need to use uv pip at all when working with a local development environment, you can get by entirely on uv run (and maybe uv sync --extra test to install test dependencies) with no direct invocations of uv pip at all.
I bounced a few questions off Charlie Marsh and filled in the missing gaps - this TIL shows my new uv-powered process for hacking on Python CLI apps built using Click and my simonw/click-app cookecutter template.
Quote 2024-10-24
Grandma’s secret cake recipe, passed down generation to generation, could be literally passed down: a flat slab of beige ooze kept in a battered pan, DNA-spliced and perfected by guided evolution by her own deft and ancient hands, a roiling wet mass of engineered microbes that slowly scabs over with delicious sponge cake, a delectable crust to be sliced once a week and enjoyed still warm with creme and spoons of pirated jam.
I don't get the difference between this and artifact. they both run Javascript. is it the fact that you can upload files to it?