Hi ~ Thanks for your support !

We don't have a test environment for openwrt. However, although we don't conduct massive tests of x-cmd on ash, it should work with ash by design.

ui window size

E|tui: The current screen size is insufficient to display the content

This log suggests the console windows size don't meet the least requirement of opening x help TUI app.

Please try the command in the console windows where the command x help fail to run.

x ui col
x ui row

openwrt

The pkg system may not works with openwrt. Because we currently only provide aarch64 binary build for linux.

It would be very helpful if the screenshot and logs and commands provided.

Hello, i'am very sorry that i not answered in time.
I managed to get the most commands i found very interesting on the first sight for example the '@gemini' command worked with setting the COLUMNS and LINES to a higher variable.
Sadly sometimes something errors to install sometimes not but its not usable for example i tried to bring java on OpenWrt it installs but the java binary is not usable.
But its not worth the work to get behind this like you said its intended for aarch64 not the old armv7l architecture.

Again thank you for your great work ! Keep it on ( perhaps on Termux xD ) !

I managed to get the most commands i found very interesting on the first sight for example the 'https://github.com/gemini' command worked with setting the COLUMNS and LINES to a higher variable.

Cool ~ Yes. The tui depends on COLUMNS and LINES. Bormally x-cmd could detect it and set COLUMNS and LINES correctly even in ash, and the TUI app could run normally, provided that if your current terminal is big enough.

Sadly sometimes something errors to install sometimes not but its not usable for example i tried to bring java on OpenWrt it installs but the java binary is not usable.
But its not worth the work to get behind this like you said its intended for aarch64 not the old armv7l architecture.

It worths the work. X-CMD should works on armv7l which is widely used in some energy-efficient embedding hardwares. I am currently just swamped by other issues related to the making x-cmd finally stable.

This might be a bug in recent versions.
We implemented a more cautious approach to prevent autonomous scripting from hanging. It seems it might be triggered unexpectedly.

An update with a more approprivate implementation will be released within the next 10 days.

I am moving this issue to discussion ~ And we welcome more feedback and questions ~