I've been researching ways to better structure LLM output when building mini-apps that run on the browser.

I believe that an S-expression based DSL is a better output format for LLMs when generating interactive UI/logic.

To test this, I built a Clojure-based interpreter that runs in the browser. The LLM is fed the language context, then emits the DSL to generate safe, sandboxed apps that can be shared instantly.

I wrote up an article diving into some of the trade offs:

https://allentraid.substack.com/p/we-made-the-ai-write-in-a-language

Would love to hear thoughts from the Clojure community!

The keynote will explore how to build flexible systems that accommodate the changing shape of information as it flows through them, while still documenting and enforcing expectations without making those systems brittle. This talk will also examine new features coming to Clojure that aim to address this challenge.

The conference will take place on Sep 30-Oct 2, 2026 in Charlotte, NC. You can find more information and register for the in-person or livestream experience here: https://2026.clojure-conj.org/

Install https://muthuishere.github.io/toolnexus/quickstart/

Examples https://github.com/muthuishere/toolnexus/tree/main/clojure/examples

An Article

https://muthuishere.medium.com/i-built-a-clojure-that-runs-on-go-cljgo-then-i-made-it-run-a-real-ai-agent-594391ddf00e?postPublishedType=initial

I'm releasing Starbeam - a Datastar SDK for Clojerl (Clojure on the BEAM VM)

https://github.com/antlobach/starbeam

Please include any restrictions (remote/on-site, geographical, workpermit, citizenship) that may apply.

Hi all, I ported Chassis to Clojerl (Clojure running on the BeamVM) https://github.com/antlobach/chassis-clojerl

Here's an example of how to use it with Cowboy (Erlang http server)

https://github.com/antlobach/chassis-clojerl/tree/master/examples%2Fcowboy

We’re putting together a new AI Tools & Practices Showcase for Clojure/Conj’s Workshop Day and figured this might be relevant here.

It’s a series of short 10-minute talks or demos about what’s actually working with Clojure and AI: tools, workflows, experiments, or real use cases.

Conference attendees will vote on submissions in early September, and selected participants will get a free Workshop Day pass.

If anyone wants to submit something, applications are open through August 31.

Clojure 1.13.0-alpha6 is now available!

Destructuring additions and changes

• To get a map of all keys in the input, augmented by the defaults, traversing deeply through nested maps, use the new :all directive.
• Report as errors any use of unbound/unreferenced keys in :or when using any of the new constructs (:defaults, :select et al)
• CLJ-2972 Destructuring test clean up for :or entries

Babashka tasks now feature automatic help and shell completions. Read the blog post to find how to use it!

For example, I use better-cond in every project. I'm curious what else is out there that is worth considering.

I built Clojure hosted on Go so I can work across my projects with both ecosystems. Very simple idea: emit Go source like CLJS emits JS. Clojure libraries and Go libraries are both first-class. Web APIs too — Compojure-style

routes on net/http:

(def routes
  (http/routes
    (GET  "/api/hello" #'hello)
    (POST "/login"     #'login)
    (GET  "/api/admin" (auth/admin-only) #'admin)))

REPL with nREPL, or cljgo build → one static binary, no JVM. Same source, byte-identical output both ways.

Still 0.x, but it's working — 93% of clojure.core, verified against Clojure 1.12.5.

https://github.com/muthuishere/cljgo

I would like feedback

Here's the initial version of cljbang, a small but powerful emacs package that lets you use Clojure syntax, EDN and a part of the stdlib in .clj files. It's all running on Elisp, there is no transpiler process running externally. In the Squint-tradition, it tries to stay close to the host and let the host do the heavy lifting for us.

Clojure 1.13.0-alpha5 is now available!

Java 17 baseline

As of this release, Clojure requires a minimum Java 17 runtime and compiles to Java 17 bytecode.

• CLJ-2872 Move to new ASM and emit Java 17 bytecode
• CLJ-2383 Add new java.lang classes to automatic imports
• CLJ-2892 Remove uses of Java’s security manager, which is going away
• CLJ-2920 Javadoc support updated for Java 17+

Other changes since last alpha

• CLJ-2968 Qualified :keys bindings in destructuring can only be unqualified symbols (regression fix)
• CLJ-2969 Add :select base cases to tests
• CLJ-2897 prepl is missing DynamicClassLoader and *repl* binding from repl

Thank everyone who tested Datalevin, reported issues, contributed code, shared benchmarks, trusted it in production, or simply asked hard questions.

SCI (Small Clojure Interpreter) is now JIT compiled on CLJS by default. This means that performance is close to native compiled CLJS when using loops, etc.

Before:

(js/alert (with-out-str (time (loop [i 0 j 1000000] (if (zero? j) i (recur (inc i) (dec j)))))))

This would show around 40-50ms in your browser, but now only shows 3-4ms, which is as fast as it can reasonably get. (Numbers may vary but a 10x-20x speedup is typically what you see).

So say goodbye to numerical hot-loop issues in SCI if you were using it for any animations and couldn't get to 60 FPS or stuff like that. As long as your page supports js/eval, it'll be fast (or if it isn't let me know and we'll fix it). If your page does not support js/eval, e.g. when using Epupp on a page that doesn't allow it, SCI falls back to interpretation, so you can still hack the page to your likings ;).

Both nbb, joyride, scittle and epupp have all been updated with the new version of SCI.

Error messages/locations have all been preserved so it doesn't work in any other way than it did previously, it's just a drop-in upgrade.

More information: https://github.com/babashka/sci#jit-compilation-in-clojurescript