[simonw]

One of my biggest unlocks has been embracing Claude Code for web - the cloud version - and making sure my projects are setup to work with it.

I mainly work in Python, and I've been ensuring that all of my projects have a test suite which runs cleanly with "uv run pytest" - using a dev dependency group to ensure the right dependencies are installed.

This means I can run Claude Code against any of my repos and tell it "run 'uv run pytest', then implement ..." - which is a shortcut for having it use TDD and write tests for the code it's building, which is essential for having coding agents produce working code that they've tested before they commit.

Once this is working well I can drop ideas directly into the Claude app on my iPhone and get 80% of the implementation of the idea done by the time I get back to a laptop to finish it off.

I wrote a bit about "uv run pytest" and dependency groups here: https://til.simonwillison.net/uv/dependency-groups

[athrowaway3z]

Half my visits to HN are to check out a comment that explains the right uv inline dep syntax

   #!/usr/bin/env -S uv run --script
   # /// script
   # dependencies = [
   #   "requests<3",
   #   "rich",
   # ]
   # ///
   import requests, rich
   # ... script goes here`
   

so i can tell claude to write a self contained script it can later use.

[wrs]

Huh. I just tell Claude “write a self contained uv script” and it does that fine by itself.

[jarrettcoggin]

Are you doing this for non-library projects as well? I'm trying to wrap my head around the idea of packaging a microservice using this mechanism (I haven't heard of this before now).

[simonw]

I have templates for Datasette plugin, Python libraries and Python CLI tools.

I often have Claude Code build little HTML+JavaScript tools which are simple enough that I don't need a template ("Vanilla JavaScript, no dependencies or build script, test it with Playwright").

I've built a couple of Go apps which works great because Go has such strong default patterns and a full featured standard library, so again no need for a template.

[throwup238]

> and making sure my projects are setup to work with it.

MESA drivers are a godsend in Claude Code for web if working on non-web GUIs. It can take screenshots and otherwise interact with them.

[corysama]

What does "MESA drivers" refer to here? I'm guessing it's not GPU drivers from https://mesa3d.org/

[throwup238]

No those don’t work in most cloud VMs but MESA provides llvmpipe/softpipe implementations for Vulkan, OpenGL, etc. They’re software renders so relatively slow but work in headless VMs like Claude Code for web environments.

[sanderjd]

I've been trying to use workflows like this, but I quickly run into token limits.

I'm curious, for those of you who work like this, what level of subscription do you have?

[simonw]

I'm on the $200/month Max plan.

[senko]

> The dev dependency group is a special case for uv run - it will always install those dependencies as well

Huh, this is...unexpected. TIL, indeed!