Cody autocomplete showing no suggestions in your Swift files? Here is a focused troubleshooting checklist covering sign-in, extension conflicts, file context, and settings to get inline completions working again.
The typical symptom is simple: you type in a Swift file and Cody offers no inline suggestions, even though chat may still work.
Start by separating the two features. If chat works but completions do not, the issue is autocomplete-specific, not your whole connection.
Check the Cody status indicator in your editor's status bar. It often shows whether completions are enabled, loading, or errored.
Work through the checks below in order. Most no-suggestion cases come down to sign-in, a disabled setting, an extension conflict, or missing context.
Autocomplete requires an authenticated session with an account that has current Cody access. Open the Cody panel and confirm you are signed in, not stuck on a login screen.
Remember the 2025 plan changes: the standalone Cody Free and Pro tiers were discontinued. If your access lapsed, completions can silently stop while the extension stays installed.
Verify you can log in to your Sourcegraph instance in a browser with the same account. A revoked or expired account is a common root cause.
If you recently switched instances or organizations, sign out of Cody and sign back in to refresh the connection.
Open your editor settings and search for Cody autocomplete. Confirm the completions setting is turned on; it can be toggled off accidentally or by a synced setting.
Some setups let admins disable autocomplete at the instance level. If you are on an enterprise plan and completions are off everywhere, ask whether a policy disabled them.
Also check any language-specific enable or disable lists. Make sure Swift is not excluded from autocomplete in your configuration.
After changing a setting, reload the editor window so the extension re-reads its configuration.
Multiple AI assistants fighting over inline suggestions is a frequent cause of missing completions. Two extensions cannot both own the ghost-text slot cleanly.
Temporarily disable other AI completion extensions, then reload and test Cody alone. If suggestions return, you have found the conflict.
Decide which assistant owns inline completions and disable inline suggestions in the other, rather than uninstalling if you use both.
Also disable non-AI extensions that aggressively provide inline hints if the conflict persists, then re-enable them one at a time.
Completions improve dramatically with context. Open the project at its root and keep related Swift files open so Cody has material to draw from.
In a brand-new or nearly empty file, suggestions may be sparse simply because there is little to predict. Add a function signature or a few lines and try again.
If your file is enormous, very large files can slow or suppress suggestions. Try in a normally sized file to isolate the issue.
Confirm your ignore rules are not excluding the file or its dependencies from context, which would starve completions.
Open the Cody output or log channel in your editor. Errors there often name the exact problem, such as authentication failures or blocked requests.
Corporate networks, VPNs, and proxies can block the requests completions rely on. If logs show network or TLS errors, that is your lead.
Test on a different network if possible. If completions work off the VPN, coordinate with IT to allow the required endpoints.
Note any rate-limit messages. If you have hit a usage limit, completions can pause until the limit resets.
If everything looks right but suggestions still do not appear, reset. Sign out of Cody, reload the window, and sign back in.
Update the Cody extension to the latest version. Completion bugs are fixed regularly, and an old build may be the culprit.
As a stronger reset, uninstall the extension, restart the editor fully, then reinstall and reauthenticate.
Reloads and clean reinstalls clear stale state that toggling settings alone will not fix.
If completions still fail after sign-in, settings, conflict, context, and reset checks, gather evidence before escalating.
Capture the Cody log output, your editor and extension versions, and a note on whether chat works. This distinguishes a personal setup issue from a service problem.
For enterprise deployments, contact your Sourcegraph administrator, since policies and instance health are outside your local control.
Check Sourcegraph's documentation and status resources too, in case a known issue or recent change explains the behavior.
Occasionally the problem is not Cody at all but the editor's state. A window that has been open for days can accumulate stale extension state that a reload clears.
Confirm the file is a real Swift file on disk, not an unsaved or untitled buffer, since some completion paths need a saved file to work well.
Check that you have not accidentally entered a mode or view where inline suggestions are suppressed, such as a diff view.
Ruling out these mundane causes early saves you from deeper debugging when a simple reload would have fixed it.
Inline completions appear as you pause typing, and they depend on enough surrounding code to predict from. In a sparse file, expect fewer suggestions.
Give Cody a running start by writing a clear function signature or a few lines of a SwiftUI view before expecting completions to flow.
Accepting a suggestion is usually a single keypress, while continuing to type dismisses it. Confirm your accept key is not rebound by another extension.
Knowing the trigger model helps you tell a real bug apart from normal behavior in a nearly empty file.
Once completions work, keep the extension updated so you get fixes rather than living with an old build's bugs.
Standardize your AI tooling so two assistants are not silently fighting over inline suggestions on the same machine.
Document your working settings, so if a synced setting flips a toggle, you can restore the known-good configuration quickly.
A little hygiene here keeps autocomplete reliable instead of something you re-diagnose every few weeks.
Before blaming Cody, make sure the missing suggestions are its and not another provider's. Editors show completions from several sources, and it is easy to misattribute them.
Hover over or inspect a suggestion when possible to see which extension produced it. If it is not Cody, your fix lies elsewhere.
Disable other providers briefly to isolate Cody's behavior on its own.
Correct attribution keeps you from tuning the wrong extension while Cody sits fine the whole time.
The two features are separate. Chat working confirms sign-in, so focus on the autocomplete setting, extension conflicts, missing file context, or a disabled completions policy.
Yes. Two inline-suggestion providers often conflict. Disable other AI completion extensions, reload, and test Cody alone to confirm, then choose one owner for inline suggestions.
They can. The standalone Cody Free and Pro tiers were discontinued in 2025. If your account no longer has active Cody access, completions stop even though the extension stays installed.
With little surrounding code, Cody has little to predict. Add a function signature or a few lines, keep related files open, and completions typically appear.