Aesh extension

[ståle pedersen]

Hi all, over a couple of weeks I've worked on and off on an aesh extension;

https://github.com/stalep/quarkus/tree/aesh_extension

It's fairly functional atm, works directly on the shell and websocket and ssh. I've not integrated it to the dev ui, but otherwise most of it should be there I think.

The benefits of aesh vs picocli is that's a more "real" cli with repl.

I've added documentation here; https://github.com/stalep/quarkus/blob/aesh_extension/docs/src/main/asciidoc/aesh.adoc

The aesh homepage has also been updated fairly recently; https://aeshell.github.io/

Let me know if you have any questions.

ståle

[Max Rydahl Andersen]

Awesome stuff Staale!

I think its good to clarify that there are different “levels” of cli in play here.

The quarkus-picocli (and picocli’s) main thing is command line argument parsing.

The readline command line loop (what I believe you call “real” cli) is in picocli available at https://github.com/remkop/picocli/blob/main/picocli-shell-jline3 as the picocli-shell - which I believe we don’t have direct integration with.

I think it is important we do NOT mix those two notions up into one because even though they are very related

And lots can be reused, a command line application (CLI) is NOT the same as a Read Eval Process loop (REPL).

Two quite different approaches to design for imo. 

With that clarification in place I do want to say I think its really awesome and opens up for some cool use cases.

I’m definitely going to give it a try!

About dev-ui - we already have repl commands in the devmode terminal, which I believe is using aesh behind the scenes, right?

I guess that makes the case for aeash extension to be *inside* quarkus main extension as we will have a hard coupling to what

Aesh version in play here or how ?

/max

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/0febd73c-6925-40c5-b4b8-3f764ae09d20n%40googlegroups.com.

[ståle pedersen]

On Saturday, February 14, 2026 at 8:19:04 AM UTC+1 Max Rydahl Andersen wrote:

Awesome stuff Staale!

Thanks! :) 

I think its good to clarify that there are different “levels” of cli in play here.

The quarkus-picocli (and picocli’s) main thing is command line argument parsing.

The readline command line loop (what I believe you call “real” cli) is in picocli available at https://github.com/remkop/picocli/blob/main/picocli-shell-jline3 as the picocli-shell - which I believe we don’t have direct integration with.

I think it is important we do NOT mix those two notions up into one because even though they are very related

And lots can be reused, a command line application (CLI) is NOT the same as a Read Eval Process loop (REPL).

 

Yes, I was not aware of the jline integration with picocli. There is however more it so I without testing picocli+jline I'm not convinced it would have all the features needed.

Two quite different approaches to design for imo. 

Yes, for sure. 

With that clarification in place I do want to say I think its really awesome and opens up for some cool use cases.

I’m definitely going to give it a try!

Let me know how it works! 

About dev-ui - we already have repl commands in the devmode terminal, which I believe is using aesh behind the scenes, right?

I guess that makes the case for aeash extension to be *inside* quarkus main extension as we will have a hard coupling to what

Aesh version in play here or how ?

 

I would think so yes. Quarkus dev mode use aesh behind the scenes.

ståle