> As I said, it's in my CLAUDE.md. That just gets progressively lost when context gets larger.

I rarely have this problem, but you could do a /loop every 30 minutes or so to have Claude reread the CLAUDE.md file might do the trick? or however long it 'forgets' I believe there's an MCP for "after" it finishes a task or compacts too, but I don't recall the name.

▲

ceejayoz 2 hours ago | parent [-]

Sure, I could. (I have a fairly complex workflow with subagents at this point, which helps reduce it; I mainly get bitten by it when I go back to a direct `claude` CLI prompt for something.)

But that solves "my LLM is doing things I don't want it to do". It doesn't solve "Grok's owner wants it forced into agreeing with him" scenarios.

▲

giancarlostoro 2 hours ago | parent [-]

Have you tried something like beads? Curious if it would help with your setup too. This is also kind of why I built "GuardRails" I got tired of Beads auto-approving tickets or closing them.

https://github.com/Giancarlos/guardrails

	▲	ceejayoz 2 hours ago \| parent [-]
		I have a custom Mac app that runs a workflow with plan/build/review/test/document subagents in Ralph loops, manages MCPs, etc. that I'm extremely happy with so far. Beads was a bit of an inspiration for parts, as was Chainlink (https://github.com/dollspace-gay/chainlink).