[Bug]: CLI crashes a few secs after opening it

[ricky7uio]

Pre-flight checks

• I am running the latest preview release of the Tabular Editor CLI.
• I have searched existing issues and could not find a duplicate.

CLI version

can't execute --version as it crashes as soon as I open it

Operating system

Windows

Architecture

x64

Command that triggered the bug

no Commands, just opening the cli and crashes.

Expected behavior

not to crash

Actual behavior

I open the te.exe file and it crashes

Steps to reproduce

1 open the file
2 it crashes

Additional context

No response

[jeroenterheerdt]

Oh no! Did you get any error message? Can you share a screenshot? Also, which version of Windows are you on please?

[ricky7uio]

Hi Jeroen!,

I was able to get it by recording a video of the crash, otherwise it was too fast to do it.

TE.cli.crash.mp4

This is my windows version:

Hope this helps,
thanks!

[AnalyticEndeavorsUser]

I got this same issue, haha.

Realizing this is just the direct CLI executable, not a setup file for installing to a directory with the path config, haha. So just asked claude "Here's the Tabular Editor CLI exe, please install this, put in a directory, and setup all my LLMs to have access to it's tooling"

[gronnerup]

Thank you so much for downloading and testing the CLI.

What you’re seeing is currently by design, although we agree the experience can be improved and we plan to change it.

The reason for the current behavior is that the CLI expects a command to follow te. When no command is provided, it reports that a required command is missing and then displays the help output as guidance.

When double-clicking te.exe from Windows Explorer, the expected behavior should instead be to open a new terminal window and automatically enter interactive mode, displaying the te> prompt. From there, you can start entering commands such as ls, connect, or auth login. When you’re finished, typing exit would close both the interactive session and the terminal window.

If you launch a terminal manually and run te, you would see the same interactive prompt, but the terminal window would remain open after you exit the CLI.

We’ve added this issue to our backlog and plan to address it in an upcoming release.