Troubleshooting and limitations

If terminal autocomplete is not appearing, start with the simple checks first.

Quick checklist

Check each of these before assuming the feature is broken:

• Terminal autocomplete is enabled in Settings > Terminal
• if this is an SSH session, the Conduish companion was allowed to install under ~/.conduish
• if this is an SSH session, the companion is installed and healthy
• the current shell is one of the supported shells for the type of session you opened
• the bundled autocomplete runtime, sidecar, and specs are available

Why suggestions might not appear

Today, the most common reasons are:

• the setting is disabled
• the remote companion is not installed or not healthy
• the current shell is unsupported
• the bundled autocomplete runtime or resources are missing

Current limitations

The current implementation has some important limits:

• shell support is not universal
• completion generators are not supported equally across shells
• SSH autocomplete has more prerequisites than local autocomplete
• unsupported shells are disclosed as support limits rather than treated as fully supported
• missing runtime or resource pieces can result in silent absence of suggestions

Session-specific expectations

For local terminals, support is simpler because everything runs on the same machine as the terminal session.

For SSH terminals, support is narrower because Conduish depends on:

• a healthy companion install
• a successful remote shell probe
• a shell that supports the current generator execution path

If you need the background on those SSH-specific requirements, read SSH autocomplete and the companion.

If the goal is to remove the feature instead of debugging it, use how to uninstall.