Kode Injector

Help and bug reports

Kode Injector Support

Most problems come from a hostname mismatch, a disabled toggle, or missing local file access. Run the checks below before opening a report.

Quick diagnosis

Check these six things first

  1. 1

    Confirm the rule hostname matches the current page and does not include a path.

  2. 2

    Confirm at least one JavaScript or CSS path points to an existing local file.

  3. 3

    Make sure the rule, its file toggle, the current site, and global injection are all enabled.

  4. 4

    In Chrome or Edge, enable “Allow access to file URLs” in the extension details.

  5. 5

    In Firefox or Native Host mode, check that the current Kode Injector Helper is installed.

  6. 6

    Reload the target tab after correcting the rule or file-access setting.

Read detailed troubleshooting →

Reproducible reports

Include enough context to diagnose the issue

Remove secrets and private source code before sharing logs or screenshots. A minimal safe example is usually more useful than a full project file.

Environment
Browser and version, operating system, Kode Injector version, and selected file-access method.
Reproduction
Exact steps, expected result, actual result, and whether the problem happens with a minimal file.
Diagnostics
Visible error text and relevant browser console output with local usernames, paths, tokens, and private code removed.

Contact

Choose the right channel

Looking for installation help?

The setup guide covers browser file access, creating a first rule, example files, and platform differences.

Open the setup guide