Troubleshooting
Work through the item that matches your symptom. If none of them applies, open a support ticket with your platform, the build version and the steps to reproduce.
A feature from this documentation is missing
Check three things, in this order:
- Is the feature PRO? Docker and Libraries need a PRO account. Sign in with an account that has PRO; see feature access. AI chat is not PRO; if an agent is missing, it is the next two points.
- Are you signed in in the IDE? The IDE decides what to show from your account, so a signed-out window shows the Free features only.
- Is it a platform limit? Docker and language servers are desktop-only. The platform matrix lists every case.
The portal is locked after signing in
The portal stays locked until your email address is verified. Complete verification, then reload. If the verification message never arrives, check spam and then ask on Discord.
An agent is not in the agent selector
Claude Code, Codex, Copilot, Cursor, Kiro, OpenCode and Cline are local AI agents, so all of the following must be true: you are on a desktop platform, the agent is installed on that machine, it is configured with a login or an API key, and your account is allowed to use it. Free and custom OpenAI-compatible providers work without any of this and are a good way to confirm that chat itself is fine.
The model replies but never edits files
The selected model rejected tool use. Genexy continues the turn as text-only chat and says so. Switch to a model that supports tools; the conversation context is kept across the switch. See AI Chat.
An AI action never runs
An action that changes something waits for approval. Look for the pending request in the conversation and choose Always, Once or Deny. If you would rather not be asked, enable Autopilot, but review the resulting diff in Git Changes.
Bash is missing from the terminal menu
On Windows, Bash appears only when bash.exe exists, normally through WSL or Git for Windows. On macOS and Linux the
menu lists the shells actually installed. Genexy Shell is always present.
A command works in Bash but not in Genexy Shell
Genexy Shell implements its own command set and cannot execute arbitrary system binaries. Use a native desktop terminal
for anything that must run as an operating-system process. Type help to see what your build includes.
Completion and errors do not appear in the editor
Code intelligence needs a language server, which needs the matching toolchain on your machine: the Go toolchain for Go,
npm for TypeScript, PHP or HTML/CSS, Ruby’s gem for Ruby, and so on (the
language table lists each one). Watch the status bar: it reports scanning, installing, starting and finished. If a server
stalls after large external changes, restart it for that language. On mobile there is no language server at all.
The layout is broken after dragging panels
View → Reset Layout restores the default arrangement. Zoom resets with Ctrl+0.
Docker shows nothing
Docker Engine must be installed and running before the panel can list anything; Genexy does not start it. The panel uses
the same local Docker context as the docker command, so verify it in a terminal first.
A vulnerability scan returns nothing
First check the status line under the panel header. It reports how many packages were checked and whether any lookup failed; a failed or partial scan leaves rows looking clean without having verified them, so rerun it.
A genuinely clean result means nothing matched in the advisory database, not that the project is free of vulnerabilities.
The scan reads declared dependencies rather than performing a full build resolution, so transitive dependencies known
only to your build tool can be missing. Dependencies marked no version (unresolved Maven properties, version catalog
entries, workspace:/git/path references) are not scanned at all, and entries marked ~ were scanned against the
lowest version of a declared range. Committing a lockfile (package-lock.json, Cargo.lock, poetry.lock) makes those
exact. The scan also needs network access to reach OSV.dev.
Beta builds change often. Before spending time on a problem, check Changelog and Download in the portal to confirm you are on the current build.