It's interesting (and probably correct) how much this focuses on the UI.
I also looked (/am looking) at Lisp and AI, but I went with Clojure and zero-ed in on the REPL driven development. The high level idea is that a session maps to a namespace in Clojure. When you create a new session, it makes a new namespace, injects tools that are bound to that session into it, and then swaps you into that namespace. So I can do something like:
(new!)
(prompt! "Write me a script that does ....")
The agent configuration, tools it has, etc, etc are all bound to the namespace so you can drop a tool or change the model just for the session.
The agent also has a tool (that I've tried to encourage it to use almost exclusively) to execute code in the session's namespace (via nREPL, so same JVM as yours is connected to), so you have full access to any variables it declares, functions it makes, etc.
The idea was to be able to work collaboratively with the agent. I can e.g. load API data into a variable, point the agent at the variable, and it does stuff. It's also capable of modifying its own code. I semi-routinely poke it by asking it to add features to the harness and then use them ("add support for subagents in this workspace, and then invoke a separate agent to handle each of these tasks"). I've also had it add support for a new inference provider, swap the session to that provider and then start doing some other task.
It's very neat, and it's wildly insecure. E.g. prompt injection could theoretically make the LLM change itself to hide messages from you, there's nothing to prevent that. I'm actually not sure how you'd even go about trying to secure that, which is why it's probably a terrible idea. Fun, though.
Relatedly, I have installed my customized emacs inside a container that also has codex and a bunch of other niceties. In short, having Codex and emacs side-by-side super-charges the concept of emacs. Why? Because you can ask AI to write emacs lisp quickly molding the coding environment you want for whatever task you are trying to achieve. And the container aspect makes the whole development environment portable. Despite its age, in the AI era, emacs is the gift that keeps on giving.
I liked the article, it provided contest to everything, as opposed to a rather bland homepage. I won't even call it a AI generated since it looks like...every other bland tool homepage from the past 15 years lol.
Oh, that's exciting! I have been disappointed by Steve Yegge's attempts at emacs-inspired coding harnesses, and options like ECA using ACP have always felt a little too behind for me, so I honestly felt like an insistence on sticking with Emacs for coding / AI interfacing was actually holding me back. But I'm certainly excited to see what Mr. Mastering Emacs has to say about it.
One request, which I'm emailing in for: arm64 builds for Linux, since I use Asahi.
I also looked (/am looking) at Lisp and AI, but I went with Clojure and zero-ed in on the REPL driven development. The high level idea is that a session maps to a namespace in Clojure. When you create a new session, it makes a new namespace, injects tools that are bound to that session into it, and then swaps you into that namespace. So I can do something like:
The agent configuration, tools it has, etc, etc are all bound to the namespace so you can drop a tool or change the model just for the session.The agent also has a tool (that I've tried to encourage it to use almost exclusively) to execute code in the session's namespace (via nREPL, so same JVM as yours is connected to), so you have full access to any variables it declares, functions it makes, etc.
The idea was to be able to work collaboratively with the agent. I can e.g. load API data into a variable, point the agent at the variable, and it does stuff. It's also capable of modifying its own code. I semi-routinely poke it by asking it to add features to the harness and then use them ("add support for subagents in this workspace, and then invoke a separate agent to handle each of these tasks"). I've also had it add support for a new inference provider, swap the session to that provider and then start doing some other task.
It's very neat, and it's wildly insecure. E.g. prompt injection could theoretically make the LLM change itself to hide messages from you, there's nothing to prevent that. I'm actually not sure how you'd even go about trying to secure that, which is why it's probably a terrible idea. Fun, though.
One request, which I'm emailing in for: arm64 builds for Linux, since I use Asahi.