rodney

You didn't address my comment about state. If you're driving something like Playwright you need a way to maintain state between tool calls. (Oddly enough I did solve that with my own CLI tool for running browsers during my "who needs MCP" phase, but it's a bit of a nasty hack that involves leaving files with PIDs lying around: https://github.com/simonw/rodney#directory-scoped-sessions and https://github.com/simonw/rodney/blob/a842432246f39775ccb14f...)

I don't have global CLAUDE.md and the only non-default skill I have that was used here is the one to use rodney[0] headless browser. I didn't expressly tell Claude to do browser testing, it decided to do it on its own. So no extra guidance beyond the prompt. [0] https://github.com/simonw/rodney/

I suggest to use https://github.com/simonw/rodney instead

Here are a few of mine from the past month - for all of them 90%+ of the code written by Claude Code: - https://github.com/simonw/sqlite-history-json - https://github.com/simonw/sqlite-ast - https://github.com/simonw/showboat - 292 stars - https://github.com/simonw/datasette-showboat - https://github.com/simonw/rodney - 290 stars and 4 contributors who aren't me or Claude - https://github.com/simonw/chartroom Noting the star counts here because they are a very loose indication that someone other than me has found them useful.

I don't use CLAUDE.md, I instead use simple token-efficient conventions. Most importantly all of my Python projects use a pyproject.toml file with this pattern: [dependency-groups] dev = ["pytest"] Which means I can tell the agent: Run "uv run pytest" And it will run the tests - without first needing to setup a virtual environment or install dependencies or anything like that. I wrote more about that pattern here: https://til.simonwillison.net/uv/dependency-groups For more complex test suites I'll give it more detailed instructions. For testing web apps I used to tell it "use playwright" or "use playwright Python". I'm currently experimenting with my own simple CLI browser automation tool. This means I can tell it: Run "uvx rodney --help" and then use rodney to test this change The --help output tells it everything it needs

Because I don't want it to write to the markdown file directly. I want it to tell me the command it runs and I then run that command and write both the command and the output to the file. Otherwise it's just writing a document, not building a demo you can review. As far as I can tell you can't hook MCPs up to Claude Code for web. I originally planned to support separate sessions but decided to leave that out for the initial release. I've opened an issue for that here: https://github.com/simonw/rodney/issues/6

If you're coming from the Python world, definitely. I find `go install github.com/simonw/rodney@latest` equally easy. :D Although you need the Go tooling installed, of course. But so much agree, Go is great for CLIs!