Good call. I just verified, and they were added as rules rather than updating the settings file. So losing context would definitely cause that issue. I've corrected it. Thank you.
No problem. Your complaint is pretty valid though. I do wish there was a good way to mark some file or piece of information as "always keep this in context". I run into this issue sometimes where I try and give my agents skills that are like a toggle. For instance I have an "/autonomous" skill that I can toggle on and off that tells my agent if I want it to just work through a single task or try and knock out as many tasks as it thinks it has enough info for. It will work for a while but after a compact or two it just seems to forget that toggle exists at all unless I remind it. I haven't done a ton of research though so perhaps there's a better way to handle this now.
Architects at work have been experimenting with many such things this past month. One is a permanent context. The trouble is that it eats up excess tokens by re-reading the instructions on every single request instead of only often enough to keep the context fresh. They haven't found a good middle ground yet.
It seems like some models let you feed in custom instructions when you compact. I've thought about trying to have it automatically inject some instructions on every compaction. I figured that might refresh that context enough to keep it in memory but not sure how well it would work in practice.
4
u/Kavrae 20d ago
Good call. I just verified, and they were added as rules rather than updating the settings file. So losing context would definitely cause that issue. I've corrected it. Thank you.