xops ask
xops ask and xgit ask are not LLM features. Same input always produces the same command. Unknown input fails with suggestions, not guesses.
How ask works
xops ask resolves intent phrases to real xops commands using a known, finite catalog.
There is no model inference, no probability, and no guessing involved.
Three guarantees
No variance between runs. No model drift. Scripting and automation can rely on ask output.
If a phrase is not in the catalog, ask returns an error with the closest matching suggestions — never an invented command.
Irreversible operations always print the resolved command and ask for confirmation. No silent destructive actions.
Order modifiers & xgit
ask-cli 1.1.0 recognizes modifier phrases like in the right order without duplicating catalog entries. Order modifiers attach to publish/install intents and show in the resolved plan as Recognized: ….
xops resolves xops → npm → git catalogs. xgit resolves git → xops → npm. Same engine, different default intent. Install both with npm install -g @x12i/ops — see Install → xgit.
Code-agent-safe ask — 2.30.0
For code agents, ask is a resolver first. Use --plan --json to get the matched command, argv, risks, explanation, and suggested execution command without running anything. In non-TTY mode xops will not wait for approval; if approval is needed, it exits with code 4 instead of blocking on stdin.
--agent, XOPS_AGENT=1, CI=true, or non-TTY mode skip the interactive approval prompt entirely.ask-cli library
@x12i/ask-cli is the library behind xops ask. Any CLI can use it to add deterministic natural-language resolution without adding an LLM dependency.
npm install @x12i/ask-cliStandalone library, no LLM dependencyExpanded command surface — in progress
xops ask is still deterministic. It is still phrase-catalog based. It is still not an LLM. The change is scope: ask can now resolve supported operational intents, not only npm/git release intents.