Troubleshooting

No suggestions appearCopy Anchor Link

1. Confirm you are using zsh in Apple Terminal or the VS Code integrated terminal.
2. From the repository root, run pnpm build:app and wait for the build to finish.
3. Load the integration again with source "$PWD/packages/cue/zsh/cue.zsh".
4. Check that packages/cue/dist/cli.js exists and that Node.js is available in your shell.
5. Check System Settings → Privacy & Security → Accessibility and allow Cue if macOS requested access.

Try git ch or cd at a fresh prompt; suggestions appear as you type. Sourcing the integration launches the built app. If Cue was rebuilt from outside a terminal, restart Cue so it loads the new app bundle.

The popup stays after a suggestion disappearsCopy Anchor Link

Cue hides the popup when the latest completion result is empty. If the old panel is still visible, press Escape once, then edit the input. Restart Cue after building a new version.

The popup is in the wrong placeCopy Anchor Link

Cue anchors the popup to Apple Terminal’s live caret. In VS Code, it combines the zsh cursor position with the integrated terminal viewport. Verify Cue remains enabled under System Settings → Privacy & Security → Accessibility and that the integrated terminal is focused. If the position is still wrong, include a screenshot, macOS display scaling, and your monitor arrangement when reporting it.

Tab prints text into the terminalCopy Anchor Link

Reload the current shell integration:

source "$PWD/packages/cue/zsh/cue.zsh"

Cue binds Tab to the native suggestion selection flow. Another plugin loaded afterward may replace that key binding.

The suggestion doesn’t match the installed commandCopy Anchor Link

Cue reads its bundled Fig command spec, which can be broader than the exact executable version installed on your Mac. For Visual Studio Code CLI flags, type code - to see options. For normal paths, type code ; for commands that accept paths, type a partial path or rm to see matching files and folders.