Jev CLI subcommand correction

Suggest a listed CLI command for an invalid subcommand

Provide the invalid token, intended operation and command help. Suggest a unique listed match, or leave it unchanged when aliases, paths or meaning are unresolved.

CLI subcommand correctionLive API
Try an example

The supplied meaning matches listing.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Suggest only from the supplied help candidates for an explicitly invalid subcommand.

Decision rules and labels
listremoverestoreNo correction
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Semantic correction uses the help descriptions, not just similar spelling. An invalid word such as inventory can refer to a listing command even when the two strings look different.

The correction boundary matters. An alias, plugin or file path can be valid outside a built-in subcommand list, and an ambiguous word must not become a destructive action by guesswork.

The linked jevyoumean project explores semantic CLI suggestions. This independent example uses a fixed fictional help list and only displays a label; it does not invoke a shell or pass arguments to a command.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of choosing one tool from the supplied alternatives
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for cli command correction.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide the invalid token, intended operation and command help.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between list, remove, restore, No correction. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review uncertain or unexpected results before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Inventory intentlist100%
Undo intentrestore100%
Explicit remove intentremove99.0%
Possible aliasNo correction73.0%
Path-like inputNo correction89.0%
Unclear destructive wordNo correction99.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

CLI command correction: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Testing a meaning-based suggestion for a rejected subcommand.
  • Checking that an ambiguous intent produces no correction.
  • Protecting aliases and paths from automatic rewriting.

Outside this demonstration

  • Executing a suggested command or choosing destructive arguments.
  • Guessing commands that are absent from the supplied help list.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Will selecting remove delete anything?

No. All outputs are labels in a text demonstration. No command is executed and no resource is selected.

Why keep possible aliases unchanged?

The supplied help list may not describe user extensions. Without that context, rewriting the token could change a valid user command.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.