[simonkagedal]

Regarding documentation, I’d love to hear you take on creating the CLAUDE.md/AGENTS.md type of files using the tools themselves, typically via some /init command. I think Claude Code, Codex and Copilot CLI all have a similar thing.

Those often seem to generate a snapshot of the current state of the codebase that to me seem to be just begging to get out of date, often with references to specific files. I sometimes start out with them and remove a bunch of stuff, or I just start empty and add things as they appear to be needed.

What’s your strategy on these?

[simonw]

I have to admit I don't actually use those yet - I've been enjoying learning how to succinctly prompt in a way that gets the right results without them.

I've experimented with having LLMs write snippets for them - things like "Based on this session, update AGENTS.md with notes about running the tests" - but my stuff tends to be simple enough that I can just say "Run tests with pytest" and it will know what to do.

I did just confirm that you can use efficiently both AGENTS.md and CLAUDE.md in the same repo by having a CLAUDE.md with a single line:

  @AGENTS.md

This is covered in the Claude Code docs here: https://docs.claude.com/en/docs/claude-code/claude-code-on-t...

[theshrike79]

My issue with that is that I don't really have any Python tooling installed globally (old trauma with overlapping package versions), each project is in an uv venv.

So every time an LLM starts firing blind they'll go python -> python3 -> damnit -> uv run python, wasting precious tokens.

That's why I have explicit instructions on how to use uv to manage things in AGENTS.md