4 ms·

No it doesn’t. The comments end up complicating simple tasks, and if you open the repo after a week it takes a while to find out why Claude is reading irrelevan

No it doesn’t. The comments end up complicating simple tasks, and if you open the repo after a week it takes a while to find out why Claude is reading irrelevant files or replying about irrelevant things

skeledrew 24d ago
If that happens you do notice that something is off though, and can steer accordingly. Unless you aren't monitoring the agent, which I suspect is the real issue here; people send a prompt, go do whatever else, return and send the next prompt or use/release the artifact, without reviewing the transcript to see how Claude - or whatever agent - did.
- 0x457 24d ago
  I don't notice it because, agent running in full-auto until there is a PR to review or decisions to make. If I wanted to go step-by-step, I'd write code myself with LLM auto-complete. I only leave meta-comments in if its actually helpful (i.e. it goes in a wrong direction without it)
  - skeledrew 24d ago
    I run Claude Code in auto-mode (or bypass when sandboxed) and still am able to monitor the transcript because - possibly by design - it works slowly enough that I can keep up and usually steer; there's no going "step-by-step". In contrast, whenever I use DeepSeek Flash, it goes so fast that I'm unable to keep up, so I primarily prompt it via Claude and also have a separate review in a fresh session, usually also by a Claude.
    - 0x457 23d ago
      > transcript because - possibly by design Except you have to expand to see writes, and if sub-agents are used, suddenly you need to monitor N transcripts. Workflows are even harder to see as they go, but workflows are what make it not have amnesia about rules you set for it. Workflows also can't be steered. Claude Code is just about geared towards "prompt it and let it do its thing"
      - skeledrew 23d ago
        I don't look at the writes unless there's something off in the prose or I know my request might be problematic/vague. For the most part the prose is a suitable signal for how well Claude is doing. I really dislike subagents as their transcripts are obscured, so I made something[0] to remedy that. I depend a lot on being able to see not only what the agent did, but the series of decisions that got it there because that helps me to improve my prompting skills as well as to determine if I should prompt a skill for X or memory entry for Y. [0] https://gitlab.com/skeledrew/jaiver https://gitlab.com/skeledrew/jaiver

skeledrew 24d ago

If that happens you do notice that something is off though, and can steer accordingly. Unless you aren't monitoring the agent, which I suspect is the real issue here; people send a prompt, go do whatever else, return and send the next prompt or use/release the artifact, without reviewing the transcript to see how Claude - or whatever agent - did.

0x457 24d ago
I don't notice it because, agent running in full-auto until there is a PR to review or decisions to make. If I wanted to go step-by-step, I'd write code myself with LLM auto-complete. I only leave meta-comments in if its actually helpful (i.e. it goes in a wrong direction without it)
- skeledrew 24d ago
  I run Claude Code in auto-mode (or bypass when sandboxed) and still am able to monitor the transcript because - possibly by design - it works slowly enough that I can keep up and usually steer; there's no going "step-by-step". In contrast, whenever I use DeepSeek Flash, it goes so fast that I'm unable to keep up, so I primarily prompt it via Claude and also have a separate review in a fresh session, usually also by a Claude.
  - 0x457 23d ago
    > transcript because - possibly by design Except you have to expand to see writes, and if sub-agents are used, suddenly you need to monitor N transcripts. Workflows are even harder to see as they go, but workflows are what make it not have amnesia about rules you set for it. Workflows also can't be steered. Claude Code is just about geared towards "prompt it and let it do its thing"
    - skeledrew 23d ago
      I don't look at the writes unless there's something off in the prose or I know my request might be problematic/vague. For the most part the prose is a suitable signal for how well Claude is doing. I really dislike subagents as their transcripts are obscured, so I made something[0] to remedy that. I depend a lot on being able to see not only what the agent did, but the series of decisions that got it there because that helps me to improve my prompting skills as well as to determine if I should prompt a skill for X or memory entry for Y. [0] https://gitlab.com/skeledrew/jaiver https://gitlab.com/skeledrew/jaiver