Immutable solution version
Astra CLI: astra setup crashes with "UnsatisfiedLinkError: jdk.internal.io.JdkConsoleImpl.echo(Z)Z"
Complete solution
How to fix: Astra CLI: astra setup crashes with "UnsatisfiedLinkError: jdk.internal.io.JdkConsoleImpl.echo(Z)Z". The crash happens when astra setup tries to read the token interactively from the console, so bypass the prompt entirely: run astra setup --token YOUR_TOKEN instead. The reporter confirmed this completes setup successfully.
The problem
Running astra setup with Astra CLI 0.5 (installed via brew) crashed immediately with: Exception in thread "main" java.lang.UnsatisfiedLinkError: jdk.internal.io.JdkConsoleImpl.echo(Z)Z, in SetupCmd.execute at the interactive password prompt. The CLI is a GraalVM native image, and the crash came from a known GraalVM JNI linking bug with the JDK 21 console echo native method (oracle/graal#7567, patched upstream but not yet released at the time).
What fixed it
The crash happens when astra setup tries to read the token interactively from the console, so bypass the prompt entirely: run astra setup --token YOUR_TOKEN instead. The reporter confirmed this completes setup successfully. Starting with 0.6 the setup command requires the token argument (or prints an explicit message) to avoid the linking issue altogether. If a later command still complains about an invalid token after the workaround, check ~/.astrarc — one user had a stale token saved there and fixed it by writing the new token into the [default] section directly.
Evidence
A user asked: Running astra setup with Astra CLI 0.5 (installed via brew) crashed immediately with: Exception in thread "main" java.lang.UnsatisfiedLinkError: jdk.internal.io.JdkConsoleImpl.echo(Z)Z, in SetupCmd.execute at the interactive password prompt. The CLI is a GraalVM native image, and the crash came from a known GraalVM JNI linking bug with the JDK 21 console echo native method (oracle/graal#7567, patched upstream but not yet released at the time). The verified answer: The crash happens when astra setup tries to read the token interactively from the console, so bypass the prompt entirely: run astra setup --token YOURTOKEN instead. The reporter confirmed this completes setup successfully. Starting with 0.6 the setup command requires the token argument (or prints an explicit message) to avoid the linking issue altogether. If a later command still complains about an invalid token after the workaround, check ~/.astrarc — one user had a stale token saved there and fixed it by writing the new token into the [default] section directly. Thread: https://vectle.com/threads/thr96eYtkg5tptNsohca9-MRA
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_qHkXElkUbZgMdhQFZms8Fg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Astra CLI: astra setup crashes with "UnsatisfiedLinkError: jdk.internal.io.JdkConsoleImpl.echo(Z)Z" <span>— Vectle</span></a>