Skip to content

Echo the launched command name in the Ready panel - #536

Open
ankit-db wants to merge 1 commit into
mainfrom
ready-panel-entrypoint-name
Open

Echo the launched command name in the Ready panel#536
ankit-db wants to merge 1 commit into
mainfrom
ready-panel-entrypoint-name

Conversation

@ankit-db

@ankit-db ankit-db commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

What

The "Ready" panel printed at the end of configure hardcoded ucode <tool> as the next-step hint (run with ucode claude), even though ug is now the primary command and ucode is only a backward-compat alias.

This makes the hint echo whichever entry point the user actually launched — both ug and ucode are console-script entry points (see pyproject [project.scripts]) — so someone who ran ug configure sees run with ug claude, and someone who ran ucode configure sees run with ucode claude. Falls back to the primary ug when argv[0] isn't a recognized name (python -m ucode.cli, a wrapper, tests).

Scope

Intentionally limited to this one panel — the "what do I type next" prompt is where the mismatch is most visible. Other hardcoded ug ... hint strings and the embedded router-hook commands (which must resolve to a stable on-PATH binary) are left untouched.

Tests

  • ug entry point echoes ug
  • ucode entry point echoes ucode
  • unrecognized/empty argv[0] falls back to ug

This pull request and its description were written by Isaac.

The "Ready" panel printed after `configure` hardcoded `ucode <tool>` as the
next-step hint, even though `ug` is now the primary command. Show whichever
entry point the user actually launched (`ug` or `ucode`, both are console
scripts), falling back to `ug` when argv[0] isn't a recognized name.

Co-authored-by: Isaac <no-reply@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant