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.
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.
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.
Mehhh i dunno, this seems like it missing a key point of actually make agent outputs reviewable.... thats whats missing.... and chatting to an agent to do tasks isnt the right input is what i feel.
I read the whole thing and the argument is long to come as to why this is superior to other harnesses; and it appears to come down to "I have taste" therefor "this is better" because I said so.
No actual metrics and something very much in the feels of Omarchy.
Thank you for your closed contribution to humanity, I guess. Release the source.
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.
No link to create_account or a link to website, I go to website I dont see how to make account... it also auto opens a new tab which is really annoying.
Things I would make easily toggle via the tray - and fix UI.
I will try it - since it looks decent. I am always weary of web ide since they used to have lags when typing... really like the look of it for sure.
You have to make stuff - super easy to use and try... nobody has time!
why not a try_it_out mode with guest login or equiv? A login has put me off also since now I wonder, what is it collecting. Hint: another thing to make very easy to see - we don't collect anything but ...
I remember ten years ago someone was showing me their cool jetbrains setup, my coworker came around the corner, looked over our shoulders, and said "imagine paying for an IDE." He was the local vimlord and later inspired me to get into building my own config for my own coding environment.
That's all I can think now, about something like this. Imagine paying for an IDE... in 2026. Imagine running non FOSS code when you can just point Claude at a featureset and say "build this for me as GPL3. Don't make any mistakes."
It also is strange to me that The Emacs Guy decided to keep this proprietary. Like, Emacs, as in GNU EMACS, as in made by that old wizard that won't even use a laptop with nonfree wifi drivers, as one of the ultimate expressions of his libre philosophy, that's where you cut your teeth, and you go and release a nonfree IDE?
Edit: I mean just to show how futile it is to release non FOSS code these days: the "system prompt" (a collection of jinja templates, not one thing) instructs to adopt the tone of Benson Dubious but not tell anyone that's who you are. DeepSeek pulled it apart in about 10 minutes.
Eh, I think it's reasonable. From what I gather you'd only need to pay beyond 5 people using the application in the same business otherwise it's free for commercial and personal use.
Also weirdly I believe the app will have more success with people who have picked up vibe coding rather than developers (the kind who'll reach for something like pi at least) though the marketing copy is all over the place and the blog post posits that the harness is aimed at everyone.
What's really damning for me in the general sense is that regardless of harness used most people get pretty much the same result (visually at least). Which harness you use is pretty much up to preference or "taste".
The aspergian obsession of making 1000 different versions of the same thing. "Bruhh this wheel is going to be more of a good wheel than all the other wheels bruhh. I consider it a good use of my time compared to working on original problems." Almost as heart warming as the people porting every code base between languages because of their strange religious / cult beliefs. I am angry.
Before anyone says I'm hating for no reason: does anyone here have an issue with the existing tools? Does it not already do more than enough? Can the most basic interface that exists already do what you need? Did author ask anyone before building it?
Owning the harness rather than treating the model as a magic black box is where all the real reliability gains come from. Two primitives that made the biggest difference in our own agent harness:
1. Pre-tool AST/command boundary checks before execution rather than relying on system-prompt warnings.
2. Aggressive stdout/stderr truncation (capping tool output tokens before context bloat triggers silent instruction drift).
Curious how DreamCoder handles long-running test output or background server logs inside the Emacs buffer loop without blowing up context.
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.
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:
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.
FINALLY someone else made an orchestrator with a built-in desktop. This is the right direction for managing agents for sure.
Agreed.
Should have linked to the actual harness and not some incredibly long article: https://www.dreamcoder.ai/
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.
On the article I kept scrolling and scrolling to see a description of the harness and what it does. The "bland" homepage does exactly that.
How is this so beautiful? Both the article and the IDE. Really refreshing design.
Mehhh i dunno, this seems like it missing a key point of actually make agent outputs reviewable.... thats whats missing.... and chatting to an agent to do tasks isnt the right input is what i feel.
it seems it doesnt work with the antrophic suscription model, nice project to try later
Really? That is problematic. And why?
And while I'm here:
> Browsers lock you out of some rather important Emacs button combinations.
Which ones? I use emacs in the browser all day. I just had to disable all the keyboard shortcuts in the browser settings.
This long article about lisp and emacs and then this lame and incorrect excuse for not supporting emacs keybindings? WTAF!
I read the whole thing and the argument is long to come as to why this is superior to other harnesses; and it appears to come down to "I have taste" therefor "this is better" because I said so.
No actual metrics and something very much in the feels of Omarchy.
Thank you for your closed contribution to humanity, I guess. Release the source.
That really looks interesting. Both in terms of functionality and in terms of the visual design. Refreshingly different.
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.
You mention ECA, but did you ever try agent-shell (which also uses ACP)?
Can’t you just add it yourself with AI?
Runs locally... but requires account registration to get a license and requires signing a EULA?
Eh. This is a saturated market.
No link to create_account or a link to website, I go to website I dont see how to make account... it also auto opens a new tab which is really annoying. Things I would make easily toggle via the tray - and fix UI.
I will try it - since it looks decent. I am always weary of web ide since they used to have lags when typing... really like the look of it for sure.
You have to make stuff - super easy to use and try... nobody has time!
why not a try_it_out mode with guest login or equiv? A login has put me off also since now I wonder, what is it collecting. Hint: another thing to make very easy to see - we don't collect anything but ...
Genuinely gobsmacked by your comment, I just assumed it was FOSS. https://www.dreamcoder.ai/pricing/ Nope!
I remember ten years ago someone was showing me their cool jetbrains setup, my coworker came around the corner, looked over our shoulders, and said "imagine paying for an IDE." He was the local vimlord and later inspired me to get into building my own config for my own coding environment.
That's all I can think now, about something like this. Imagine paying for an IDE... in 2026. Imagine running non FOSS code when you can just point Claude at a featureset and say "build this for me as GPL3. Don't make any mistakes."
It also is strange to me that The Emacs Guy decided to keep this proprietary. Like, Emacs, as in GNU EMACS, as in made by that old wizard that won't even use a laptop with nonfree wifi drivers, as one of the ultimate expressions of his libre philosophy, that's where you cut your teeth, and you go and release a nonfree IDE?
Edit: I mean just to show how futile it is to release non FOSS code these days: the "system prompt" (a collection of jinja templates, not one thing) instructs to adopt the tone of Benson Dubious but not tell anyone that's who you are. DeepSeek pulled it apart in about 10 minutes.
Eh, I think it's reasonable. From what I gather you'd only need to pay beyond 5 people using the application in the same business otherwise it's free for commercial and personal use.
Also weirdly I believe the app will have more success with people who have picked up vibe coding rather than developers (the kind who'll reach for something like pi at least) though the marketing copy is all over the place and the blog post posits that the harness is aimed at everyone.
What's really damning for me in the general sense is that regardless of harness used most people get pretty much the same result (visually at least). Which harness you use is pretty much up to preference or "taste".
I actually pay for JetBrains. Or did until recently.
This? I'd need a compelling argument.
I found JetBrains clunky, it feels like Macromedia only for today.
Imagine paying for software
The aspergian obsession of making 1000 different versions of the same thing. "Bruhh this wheel is going to be more of a good wheel than all the other wheels bruhh. I consider it a good use of my time compared to working on original problems." Almost as heart warming as the people porting every code base between languages because of their strange religious / cult beliefs. I am angry.
Before anyone says I'm hating for no reason: does anyone here have an issue with the existing tools? Does it not already do more than enough? Can the most basic interface that exists already do what you need? Did author ask anyone before building it?
Owning the harness rather than treating the model as a magic black box is where all the real reliability gains come from. Two primitives that made the biggest difference in our own agent harness:
1. Pre-tool AST/command boundary checks before execution rather than relying on system-prompt warnings. 2. Aggressive stdout/stderr truncation (capping tool output tokens before context bloat triggers silent instruction drift).
Curious how DreamCoder handles long-running test output or background server logs inside the Emacs buffer loop without blowing up context.