The sidebar does not appear
Open Options and confirm that the exact Gitea origin, port, and deployment subpath are enabled. Reapprove Chrome site access if it was revoked.
Documentation and help
Check the common fixes below. If the issue remains, report it with the minimum details needed to reproduce it.
Report an issueOpen Options and confirm that the exact Gitea origin, port, and deployment subpath are enabled. Reapprove Chrome site access if it was revoked.
Sign in to the same Gitea instance in the active tab. If its API does not accept the browser session, configure a minimum-scope read-only token over HTTPS.
Include the Gitea version, visible route shape, and whether the deployment uses a subpath. Remove private repository and branch names before posting.
Use Retry after connectivity returns. The extension keeps the underlying Gitea page usable and shows a local error category for troubleshooting.
Open the extension Options page. Remove one instance to delete its token, cache, and repository state, or choose Clear all data to remove every local extension record.
Uninstalling Gitea Code Tree also removes its extension-local Chrome storage. Revoking site access stops injection but does not by itself delete saved configuration.
Never post authentication tokens, cookies, private domains, repository names, file paths, code, or exported browser storage. A Gitea version, sanitized URL pattern, error category, and reproduction steps are usually enough.
For privacy questions or details that should not be public, email aqqzdsthl@gmail.com.