Troubleshooting
Common setup and workflow issues, and where to look first
The docs feel slow or stale
Public docs and FAQ should now be served statically. If they still feel slow, hard refresh first and make sure you are not testing through a stale preview. If content looks wrong only after a language switch, verify that the account language toggle actually changed the current language state.
Figma scan does not show the project you expect
Check that the Figma file is linked to the right Stil project and that you are signed into the same account in both Figma and the Console. Most mismatches come from linking the wrong project or using different accounts between browser and plugin.
GitHub push or PR creation is failing
Open project settings and verify the GitHub connection, selected repository, branch, and path settings first. If repository browsing is unavailable, re-link GitHub before debugging anything else. Stil cannot generate the correct push flow if the repo connection is half-complete.
MCP authentication fails
If you are using the hosted MCP endpoint, confirm that your project API key is configured as the bearer token. If you are using local stdio, make sure STIL_WORKSPACE_DIR points at a workspace that actually contains exported .stil data. Authentication and workspace resolution failures can look similar, so check both.
Gate marks expected changes as review or blocked
Inspect the classification details and impact context before treating it as a false positive. The change may be structurally safe but still high impact. If the rule really does not fit your team, adjust the relevant Gate policy or custom rule pack instead of bypassing the signal silently.