magnusi

I'm, the author! And happy to discuss!

hehe

Thank you!

Yooo, based website, hank! Mine was inspired by Xerox PARC and the Interlisp

Correct, that's why I made it! :)

Glad to have you!

Thank you, I am glad you like it, haha! I was inspired by Xerox PARC stuff, mostly Interlisp! :)

Well, I've had success loading Lisp programs into Autolith and letting it poke at them from the inside, haha!

(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.

On the other hand, the more mainstream a programming language, the higher proportion of the training data is going to be terrible code.

I think there's an optimal ratio somewhere

It's not just the syntax, but also the tools for debugging, the image paradigm itself, and the iterative approach to development!

Autolith can spawn managed Lisp REPLs either from saved images (so it can do checkpoints) and triage changes before committing them to files, and then run test suites in the same REPL, it's been very useful for this.

Thanks for liking it!

Hi, I am the author of Autolith. What do you mean by that? I'd love to give you a good answer, haha