Ive seen context forge has a way to use hooks to keep CC going after context condensing. Are there any other patterns or tools people are using with CC to keep it on task, with current context until it has a validated completion of its task? I feel like we have all these tools separately but nothing brings it all together and also isn’t crazy buggy.

▲

kroaton 4 days ago | parent | next [-]

Load up the context with your information + task list (broken down into phases). Have Sonnet implement phase one tasks and mark phase 1 as done. Go into planning mode, have Opus review the work (you should ideally also review it at this point). Double press escape and go back to the point in the conversation where you loaded up the context with your information + task list. Tell it to do phase 2. Repeat until you run out of usage.

	▲	conception 4 days ago \| parent \| next [-]
		Yes, i can manage CC through a task list but there’s nothing technically stopping all your steps from happening automatically. That tool just doesn’t exist yet as far as I can tell but it’s not a very advanced tool to build. I’m surprised no one has put those steps together. Also if the task runs out of context it will get progressively worse rather than refresh its own context from time to time.
	▲	kroaton 4 days ago \| parent \| prev [-]
		From time to time, go into Opus planning mode, have it review your entire codebase and tell it to go file by file and look for bugs, security issues, logical problems, etc. Have it make a list. Then load up the context + task list...

▲

rolls-reus 4 days ago | parent | prev [-]

What’s context forge?

	▲	conception 4 days ago \| parent [-]
		https://github.com/webdevtodayjason/context-forge