zlacker

>>hugoda+(OP)
I am really confused as to what happened here. The use of ‘disabled organization’ to refer to the author made it extra confusing.

I think I kind of have an idea what the author was doing, but not really.

>>cortes+w7
The author was using instance A of Claude to update a `claude.md` while another instance B of Claude was consuming that file. When Claude B did something wrong, the author asked Claude A to update the `claude.md` so that Claude B didn’t make the same mistake again

>>superb+eb
I don't understand how having two separate instances of Claude helps here. I can understand using multiple Claude instances to work in parallel but in this case, it seems all this process is linear...

>>olalon+mu
If you look at the code it will be obvious. Imagine I’m the creator of React. When someone does “create new app” I want to put a Claude.md in the dir so that they can get started easily.

I want this Claude.md to be useful. What is the natural solution to me?

>>renewi+tK
I'd probably do it like this: ask Claude to do a task, and when it fails, have it update its Claude.md so it doesn’t repeat the mistake. After a few iterations, once the Claude.md looks good, just copy-paste it into the scaffolding tool.

>>olalon+VN
Right, so you see the part where you "ask Claude to do a task" and then "copy-paste it into the template"? He was automating that because he has some n tasks he wants it to do without damaging the prior tasks.

>>renewi+lO
You can just clear the context or restart your Claude instance between tasks. e.g.:

  > do task 1
  ...task fails...
  > please update Claude.md so you don't make X mistake
  > /clear
  > do task 2
  ... task fails ...
  > please update Claude.md so you don't make Y mistake
  > /clear
  etc.

If you want a clean state between tasks you can just commit your Claude.md and `git reset --hard`.

I just don't get why you'd need have to a separate Claude that is solely responsible for updating Claude.md. Maybe they didn't want to bother with git?