FAQ

Short answers for setting up the Vizhi plugins. The Claude Console and Vizhi for Codex guides have the long ones.

General

What do I need?

An MX Creative Keypad, Logi Options+ 6.4 or newer, and the agent installed on the machine itself: Claude Code for Claude Console, Codex CLI for Vizhi for Codex. A session inside WSL is not visible to the plugins. On macOS: Apple Silicon and Apple Terminal. On Windows: Windows 10 or 11 and Windows Terminal, which the navigation keys drive.

Which terminals are supported?

Apple Terminal on macOS and Windows Terminal on Windows. Each keypress targets a specific session, which is why support is deliberate rather than universal: a terminal has to let the plugin address an individual session for the can't-miss guarantee to hold. Sessions in iTerm2, Ghostty or Warp are not shown on the session keys.

Does anything leave my machine?

No. Voice transcription runs on-device, the plugins send no telemetry, and this site has no analytics. The only network request a plugin ever makes is the one-time download of the speech model. Claude Code and Codex CLI themselves talk to Anthropic and OpenAI under their own terms. Details in the privacy policy.

Is this an official Logitech, Anthropic, or OpenAI product?

No. It began in Logitech's dev-studio programme and they provided the hardware, but it is an independent project: unendorsed and unaffiliated.

Why is the plugin about 21 MB?

It carries the offline voice runtime for both macOS and Windows, so dictation works without any cloud service. The speech model itself is not included and downloads on first use.

What about Stream Deck?

Vizhi is built for the MX Creative Keypad's LCD keys. There is no Stream Deck port today.

Setting up

I installed the plugin and nothing appeared on the keypad.

That is expected. The plugin binds to no application and carries no layout, so it adds nothing until you import one. Download the layout for your platform from the keypad layouts page, then in Logi Options+ open your keypad, open the profile menu (the ⋯ button) and choose Import Profile. Do this once. On macOS the layout attaches to Terminal; on Windows to Windows Terminal. The plugin's actions are also in the action panel if you prefer to place keys yourself.

Which permissions does it ask for?

On macOS: Accessibility for Logi Plugin Service, so the keys can type into Terminal; Microphone for the voice helper, asked on the first voice press; and Screen Recording for the Screenshot key, asked on its first use. On Windows none, apart from microphone access for desktop apps if you use voice.

Do I need to import the layout again after an update?

No. The profile belongs to Terminal's entry in Options+, not to the plugin, so updating or reinstalling never touches it. The keys light up again after the update. If a release changes the layout itself, delete the profile and import the new file.

Can I keep my own Terminal profile?

Yes. Skip the import and drag the plugin's actions onto your existing profile instead.

Live status and answers

The Cost, Context, Activity and Session keys say “Set up”.

Live status is off. It is off by default because turning it on edits your Claude Code settings file, adding a status line and five hooks that report state to the keypad. A backup of the file is written first, and your own entries are kept. To turn it on, press Cost once: on macOS a dialog asks Not now or Turn on; on Windows press Cost again within 15 seconds. To turn it off, hold the key: on macOS choose Turn off; on Windows hold again within 15 seconds. On macOS a running session picks it up by itself. On Windows start a new Claude Code session.

The Yes and No keys read “Off”.

They need live status on. A permission prompt reaches the keypad through one of those hooks, so with live status off there is nothing for the keys to answer. Turn it on as above and the keys light up when Claude asks a question.

Yes and No beep and do nothing.

They act only on a permission prompt the plugin can see. If live status is on, the session is waiting on something that is not a permission menu, such as a plain-text question or an idle prompt. Type into the session for those. The refusal is deliberate: guessing at a menu the plugin cannot see is how the wrong thing gets approved.

I have several sessions open. Which one do the keys act on?

Each of the three Session keys shows a project and its state. On macOS the keys follow the Terminal tab in front. Press a Session key to pin one, so the answer and typing keys go to it whatever is in front; press it again to release. On Windows, pin first: Windows Terminal does not say which tab is in front.

What do the amber and red dots mean?

Amber on both answer keys: the agent is waiting on you and approving is routine. Red on Yes: Yes would run something destructive or outward-facing, such as git push or rm -rf. It is a hint, not a gate; the agent's own prompt still holds the command.

Voice

How does voice work? Does anything leave my machine?

Nothing leaves your machine. Press Dictate (you hear a tink), speak, press again: the text is typed into the session and sent. Voice Draft does the same but does not send, so you can correct it first. Go to Project opens a project by name. The first press installs the voice helper, asks for Microphone access, and downloads the speech model once (about 140 MB, the only time it needs the network).

The key says “Model loading”, “Mic denied”, “No speech”, “No target” or “Not typed”.

Model loading means the one-time download is still running; Options+ posts a card when it starts and another when it is ready, so press again after that. Mic denied means the helper was refused: allow it under System Settings → Privacy & Security → Microphone on macOS, or enable microphone access for desktop apps on Windows. No speech means it recorded but heard nothing usable. No target means it transcribed fine but there was no session to type into: nothing pinned and no single obvious session. Press a session key to pin one, then dictate again; the words are kept in the plugin log. Not typed means the session was known but the keystrokes did not land (the terminal closed, or on Windows an elevated session). No helper and No whisper mean the voice runtime is missing: reinstall the plugin.

Can I avoid the model download?

Yes. Place ggml-base.en.bin at ~/.claude/claude-console/whisper/ before the first voice press. The plugin then makes no network request at all.

Go to Project says “No match”, or finds none of my projects.

Say the folder's name as it is; “go to”, “open the” and “project” around it are ignored. The plugin looks for git repositories up to three folders below your home directory, plus every folder a running session is working in. If your projects live elsewhere, list their parent folders, one per line, in ~/.claude/claude-console/project-roots (~ is expanded, # starts a comment) and try again; that file then replaces the search. The first miss after each start also posts a card in Options+ saying what was searched.

Windows

The keys beep and Options+ shows “Windows Terminal required”.

Open Windows Terminal and run the agent in it. The navigation keys drive Windows Terminal and refuse safely when no window is open, rather than doing nothing. Run the agent without administrator rights; an elevated session cannot be reached. For a classic Command Prompt or PowerShell console, set Settings → System → For developers → Terminal to Windows Terminal and start a new session.

Is there a Turn on dialog on Windows?

No. The second press of the same key within 15 seconds is the switch, and the key says so.

What is not available on Windows?

Next Window and Previous Window (they do nothing), the on-screen Turn on dialog, and the macOS cleanup script. In Vizhi for Codex, approval lighting is unavailable on Windows; the keys still answer.

Vizhi for Codex

Codex says “Hooks need review — 7 hooks are new or changed”.

Those are the plugin's hooks, one per lifecycle event, all running the same one-line launcher that writes state files for the keypad. Choose Review hooks, then Trust all and continue. It is a one-time step. If you skipped it, run /hooks inside Codex. Never bypass hook trust globally.

Why do Yes and No never light up on Windows?

Codex's hook runner creates no process on Windows, so Codex never announces an approval to the plugin there. The keypad declares the capability absent rather than guessing. Yes and No still type answers.

Can I install Claude Console and Vizhi for Codex together?

Not on the 1.5.3 preview of Vizhi for Codex: it binds Apple Terminal, and the plugin service activates one plugin per application, so one of the two shows nothing. From Vizhi for Codex 1.6.0 both are universal and can live side by side.

Where is the Cost key?

There is none. Codex reports no spend, and the keypad never shows a value the agent did not report.

Uninstall and support

How do I uninstall cleanly?

Turn live status off first (hold Cost, Turn off), so the entries leave your Claude Code settings. Then in Options+ right-click the plugin, choose Uninstall, and delete the imported profile. Options+ removes only the plugin. On macOS the plugin leaves a cleanup script that removes the rest (voice helper, speech model, its settings entries):

bash ~/.claude/claude-console/scripts/uninstall.sh

If you uninstalled without turning live status off, the leftover entries do nothing and show no error — and on macOS they remove themselves: about a minute after the plugin's folder is gone, the next Claude Code event takes the plugin's entries out of your settings (same rolling backup as Turn off) and leaves ~/.claude/claude-console/unwired-after-uninstall to say so. Windows still needs Turn off first; its steps are in the Claude Console guide.

Where do I report a problem?

On the issue tracker. Attach the plugin log:

• macOS~/Library/Application Support/Logi/LogiPluginService/Logs/plugin_logs/ClaudeConsole.log
• Windows%LOCALAPPDATA%\Logi\LogiPluginService\Logs\plugin_logs\ClaudeConsole.log

For Vizhi for Codex the file is named VizhiCodex.log in the same folder.