ChatCode will not open / run
Restart the app → check whether Windows blocked/quarantined the file → confirm you use a supported Windows version → download again from the official site if the file is not intact.
TROUBLESHOOTING
Do not change random settings. Start with the right symptom.
Check from the simplest layer: app → project → permissions → AI connection → network/remote → account/license. Following this order avoids unnecessary configuration changes.
⌕
AI cannot see the project
Open ChatCode → confirm the project is still listed → verify the folder path still exists → first use a “list projects, do not edit files” prompt.
AI can read but cannot edit
This is usually a permission issue, not a connection issue. Check whether the project has Sửa file enabled; create/delete/rename and task execution are separate permissions.
Connector reports offline / unavailable
Check that the project computer is on → ChatCode is running → Internet works → the connector link is still correct. With a dynamic URL, a restart can change the link.
URL changes after restart
If your plan/AI uses a dynamic URL, copy the new link from ChatCode and update the connector. Do not manually assemble tokens or edit the URL.
No create-connector button
Do not assume this is a ChatCode bug. Custom connector availability depends on the AI provider, plan, workspace, and sometimes web/mobile support.
Wrong GitHub account / repo
Check the linked account, remote origin, and project before stage/commit/push. ChatCode should not silently change origin as a quick fix.
Remote / deploy does not work
Confirm the server profile is bound to the right project, the host/path is correct, and credentials are valid. On production, do not use destructive commands to test connectivity.
Windows warns about the downloaded file
Only continue after confirming the file came from the official site and its hash matches the release. ZIP may reduce browser download warnings; Windows can still inspect the extracted file.
License / device / account issue
Sign in to Account to inspect your license and devices. Do not send the full license key to support; send the error code and only a masked key hint.
No close symptom match. Open Help Center or contact support.
!
When you need support.
Send enough evidence to avoid repeated back-and-forth.
Include
ChatCode version · Windows version · AI platform · current step · error message/code · what you expected to happen.
Do not include
Full license key · full connector URL · token · password · private key · .env files or credentials.