Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jitera.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Chat

Click the ”+” icon and try in a new dialog. If the issue persists, please contact support@jitera.com.

​
Visual Studio Code Extension

This is often resolved by sending a reply saying “Please output in an applicable format.” Additionally, including the word “file” in the prompt for code generation, such as “Create a code file for xxx,” makes it more likely to be output (when only the copy button is displayed, no actual code file is created, and a code block is output as reference information).
The AI chat references files within the imported branch by default, but it is possible to reference the currently open active file or files mentioned with @. For details, please refer to the VSC extension manual.
Please check the status at this URL and attach a screenshot: ‣
To check the details of the error, please try the following steps:1. Provide the logs folder under the following directory as a zip file:
C:\Users\<Username>\.jitera\logs
2. If the logs folder does not exist in the location mentioned in step 1:Open VS Code Help > “Toggle Developer Tool”.Open the Logs tab, clear the logs once, then right-click on the log when the error occurs and save it.Then send the logs to your support contact.
This content is for Jitera’s SaaS version. If you are using a self-hosted version from one of our partners, please contact your partner.
Please respond appropriately to each error message, but please check if the following URLs are blocked by proxies or similar. If they may be blocked, please add them to your allowlist:Additionally, please contact your support team for Jitera’s public IP address and consider adding it to your allowlist if necessary. Note that you can perform partial functionality diagnostics with the following steps. If you encounter errors, please also send the diagnostic logs for smoother support.

​
Jitera Eclipse Extension

We apologize, but it is not supported. Please refer to Eclipse Extension for supported versions.
1. Provide the logs folder under the following directory as a zip file:
C:\Users\<Username>\.jitera\logs
2. If the logs folder does not exist in the location mentioned in step 1:
  • Go to Settings > Jitera and change to display the debug menu
    • The Jitera menu will now be displayed
  • Select Log from the Jitera menu > Get logs from Java

​
GitHub (SaaS) / GitLab (Self-Hosted) Integration Import

  • Click the “Authorize More Repositories” button to confirm that your GitHub account has authorized Jitera to access the repository you want to import.
  • Confirm that your GitHub account has Admin permissions for the repository.
Whether a repository is empty depends on GitHub’s determination logic, so Jitera cannot specify the exact conditions. However, it appears that uploading only a few files to the root directory may be considered empty. As a solution, we have confirmed that creating a folder such as “src” in the root directory and placing about 2 code files within it will make it eligible for import.
The Organization Owner may need to approve the Jitera application. Please check with your Organization Owner. This applies when “Cancel Request” is displayed next to the Organization name when you click the “Authorize More Repositories” button (we apologize for the inconvenience as this is a GitHub-side screen that Jitera cannot modify).
If the repository you want to import exists only on your company’s Organization, approving Jitera on your personal GitHub account (displayed at the top) will allow the Continue button to appear or allow you to proceed directly to the repository selection screen. If you want to restrict Jitera’s access to personal repositories, you can also limit permissions to specific repositories only.GitHub personal account authorizationGitHub continue buttonGitHub repository selection
Click on a different option in the repository access selection area once, then click back to the original option. This will activate the Save button without changing the settings, allowing you to proceed. Since this is a GitHub-side screen that cannot be modified, we apologize for the inconvenience. However, installing the application on both your personal account and your organization’s account will skip this screen.
There is no need to specify it as the AI automatically analyzes the content used in existing code.
The chat feature does not directly reference the imported branch but references a mirrored branch, so this branch is automatically created.
  • Confirm that your GitLab account has admin privileges.
  • Verify that the host URL you entered is not the repository URL (the top page URL should be the correct setting).
  • Also confirm that your GitLab version is 16.8 or later.
Versions 16.8 and later are supported.
Both editions are supported. However, please note the supported versions mentioned above.
We apologize, but it is not supported. Only self-hosted versions are supported. Source code import is possible using Jitera CLI, so please refer to the Jitera CLI manual.

​
Jitera CLI Integration Import

In a proxy environment, perform the proxy settings described in the Jitera manual.If the error is not resolved, run the set DEBUG=* command and send the obtained logs to your support contact.For instructions on how to run DEBUG mode, please refer to the DEBUG mode procedure in CLI manual.
This occurs because the OSS library used in the current Jitera CLI adds specific paths to Windows Defender’s exclusion settings to improve performance. It is a temporary, minimal bypass only during execution, not a complete disabling of Defender settings. If you do not want to bypass, please uncheck the following setting during installation.Windows Defender bypass checkbox

​
Screen (Beta Feature)

There may be cases where the URL does not change during screen transitions or authentication, or the screen state remains fixed without transitioning after authentication. For some technologies (such as ASP), Playwright cannot automatically detect due to security reasons. In this case, you can detect it by directly specifying the URL of the screen after login using the ”+” button on the screen page.Also, if you press the “Configure” button for the test account and the Playwright authentication code is generated, you can create a test suite manually in the “Test” tab, paste the Playwright authentication code into the code field of the test step, and execute it to determine whether the issue is with the authentication code itself or whether the authentication code is functioning normally and there is another cause.