Skip to content

Restore FZF for interactive mode UCM - #6341

Merged
pchiusano merged 2 commits into
trunkfrom
fzf-fix
Nov 11, 2026
Merged

pchiusano merged 2 commits into
trunkfrom
fzf-fix

Conversation

@pchiusano

Copy link
Copy Markdown
Member

In interactive UCM, switch, view, upgrade and other commands run with no arguments are supposed to open fzf typeahead to pick one. #6328 broke this. The new MCP server runs transcripts, and the transcript runner turned fzf off by setting an environment variable (UNISON_FZF_PATH=NONE), which turned it off for interactive use too.

Now parseInput takes an argument that says whether to use fzf. The transcript runner and the MCP server pass NoFZF. Interactive mode passes UseFZF, which uses fzf whenever it's installed (or at UNISON_FZF_PATH, which can still be set to NONE to turn it off).

Tested manually; all transcripts and proofs pass.

…the MCP server's transcript runner, which every interactive UCM now starts for /mcp, turned fzf off for the whole process by setting UNISON_FZF_PATH=NONE. parseInput now takes an FZFMode; the interactive loop passes UseFZF and the transcript runner (transcripts and MCP) NoFZF, and the runner no longer sets the environment variable.
@pchiusano
pchiusano added this pull request to the merge queue Nov 11, 2026
Merged via the queue into trunk with commit 04e630a Nov 11, 2026
13 checks passed
@pchiusano
pchiusano deleted the fzf-fix branch November 11, 2026 19:54
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