(disclaimer: I made Autolith) Well, having the agent write out tools and call those tools is something I consider to be under self-modification also. But ther

(disclaimer: I made Autolith) Well, having the agent write out tools and call those tools is something I consider to be under self-modification also. But there are other things, when it's useful: - You want the agent to update without restarting a session and e.g. killing child LISP REPLs and long-running sub-agents - There is a bug in the harness that bothers you (Autolith records papercuts and can generally solve them via self-modification) - You want to temporarily or permanently hook into literally any part of the agent lifecycle - You are of a ricing persuassion and want to change how the agent looks (very surface level, but I have seen people do it) - Related to the hooking point, you want to integrate Autolith with something else or make it emit something. We cannot predict all the knobs where you might do this, or how selectively you might do it, but self-modification lets you do it - You want to add support for yourself for non-standard or proprietary/secret providers That's off the top of my head. The secondary benefit is that this is great at developing the agent itself as a project. It can try/triage the changes it's working on, try its own tests, probe at things, and so on. This is why by far, the changes submitted to Autolith developed by Autolith are by far the highest quality out of all clanker-submitted changes.