# Extension Settings

VSCode

**1. Enable / Disable** Enjinx

Enable or disable Enjinx extension.

**2. Editor Buttons**

Choose to show or hide Enjinx buttons over functions and classes in the editor.

**3. JavaScript Tests Config-1: Run Working Directory**

Specify the working directory for running JavaScript/TypeScript tests. This setting is crucial for ensuring tests run in the correct context.

* **Path**: Use the absolute path to the root directory of your project (where your `package.json` resides).

**Important:** if this setting is configured, please configure the `JavaScript Tests Config-2: Run Command` setting as well.

**4. JavaScript Tests Config-2: Run Command**

Specify the command for running a single Javascript/Typescript test file. The placeholder `TEST_FILEPATH` will be replaced with the actual test file path.

**For example**:

* `npx jest --runTestsByPath TEST_FILEPATH`
* `npx ts-mocha TEST_FILEPATH --require ./test/mocha/setup.ts`

**Important:** if this setting is configured, please configure the `JavaScript Tests Config-1: Run Working Directory` setting as well.

**5. JavaScript Tests Config-3: Run Default Imports**

List default imports to prepend to JavaScript test files, separated by , enhancing test file setup.

**6. Code Completion**

Enable or disable code completion.

**7. Code Completion: User Instructions**

Input custom instructions for code auto-completion. These will be used by Enjinx's AI models to better align with your coding style.

**8. Agent Settings- On Save: Improve**

When saving a file, `/improve` will automatically run and suggest improvements for every mid-sized changeset.

**9. Agent Settings- On Save: Issues**

When saving a file, `/issues` will automatically run and detect issues for every small-sized changeset. JetBrains 1. Editor Buttons

Choose to show or hide Enjinx buttons over functions and classes in the editor.

**2. Enable / Disable** Enjinx **Gutter Icons**

Choose to show or hide Enjinx gutter icons appearing alongside your code.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://enjinx.gitbook.io/enjinx/enjinx/publish-your-docs/extension-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.