> how are yall carrying context...

Personally I just , in the orchestration loop, have all decisions be constantly reviewed and deliberated on and the decisions logged in a permanent way, that way everything is auditable, the model if needed can go back and look at why x or why decision was made or x or y tool used, and they're all labeled as D-1234 or whatever.

Plus I have it log the council discussions and always include provenance or the opinions so fable can go back after every major implementation and review how the orchestration loop could be improved. Basically have it log as much thinking in an organized compartmentalized way is better than any memory feature I've found though I haven't tried many. Auditable logs for every major decision, use 5.5 with reckless abandon (still have 3 resets myself).

Not claiming this is perfect but it has led to a very easy time of any fresh agent picking up the project. I also keep a task queue and project status and agent playbook that also get refined based off the logs of how a run went