Jarq Plugin: Boost Your VS Code Workflow in Minutes
Jarq is a VS Code extension that streamlines code navigation, refactoring, and project management with a single click.

Core Features
Jarq adds a collapsible sidebar that groups a handful of common actions. The sidebar is positioned on the left or right of the editor and is limited to a maximum width of 200 px, keeping the editor workspace largely untouched. The main functions are:
| Feature | What it does | Typical use |
|---|---|---|
| Refactoring shortcuts | One‑click commands such as Extract function, Rename symbol, and Move file that use VS Code’s built‑in refactoring engine. | Quickly split a large function or rename a variable across the current file. |
| Refactoring command palette | A secondary palette that lists only refactoring‑related commands, reducing visual noise compared with the full command palette. | When you need a specific refactoring without searching the full list. |
| Git status indicators | Inline icons next to file names in the sidebar and a hover tooltip that shows the most recent commit author, hash, and date. | Quick glance at the state of a file without opening the Git panel. |
| Custom keybindings | Actions can be bound to any key sequence via the normal VS Code keybinding editor. | Keep the workflow keyboard‑centric. |
| Optional AI suggestions | When an API key is supplied, Jarq can request context‑aware completions for variable names, doc‑string templates, or small code snippets. | Reduce repetitive typing or get a quick naming hint. |
The sidebar is intentionally minimal: it contains only the buttons listed above and shows a tooltip when the mouse hovers over a button. No additional panels or status bars are added.
Installation and Configuration
Installing the extension
| Method | Steps |
|---|---|
| Marketplace | Open Extensions (Ctrl+Shift+X), search for “Jarq”, and click Install. |
| Command line | Run code --install-extension jarq.extension in a terminal that has the VS Code CLI available. |
The command works on Windows, macOS and Linux as long as the code binary is in the PATH.
Activation
Jarq activates automatically when a workspace is opened. On first launch it creates a default configuration file named jarq.json in the workspace’s .vscode folder:
{
"sidebarPosition": "right",
"enableGitIntegration": true,
"enableAI": false
}
If the defaults are acceptable, no further action is required; the sidebar appears on the right side of the editor.
Adjusting settings
Settings can be changed through the Settings UI (Ctrl+,) or by editing settings.json directly. The most common toggles are:
| Setting | Possible values | Effect |
|---|---|---|
jarq.sidebarPosition | "left" / "right" | Moves the sidebar. |
jarq.enableGitIntegration | true / false | Turns the inline Git status and blame tooltip on or off. |
jarq.enableAI | true / false | Enables the optional AI suggestion panel; an API key must be provided. |
jarq.customKeybindings | Object mapping | Overrides the default shortcuts for any sidebar action. |
Linking a personal API key
If you want to use the AI suggestions, you must supply an API key. The key is stored in the workspace settings:
{
"jarq.ai.apiKey": "sk-xxxxxxxxxxxxxxxxxxxx"
}
The extension’s documentation does not specify the exact mechanism used to keep the key secure. Users should consult the official README on the extension’s GitHub repository for details.
The AI feature requires a paid plan. Pricing information has not been publicly disclosed by the maintainers.
AI Integration
Jarq’s AI integration is optional and requires a valid key. When jarq.enableAI is set to true, the sidebar shows an additional button labeled AI suggestions. Clicking the button opens a small panel that displays suggestions generated by the chosen provider. The suggestions are context‑aware: they use the current file, the cursor position, and a short excerpt of surrounding code.
Because the feature is behind a paywall, the free tier of Jarq only includes the core UI and refactoring commands. Users who wish to experiment with AI can enable the feature and provide a key, but they will be prompted to subscribe if the provider requires a paid plan.
Comparison with Other VS Code Extensions
| Aspect | Jarq | GitLens | Project Manager | Bookmarks | GitHub Copilot | Tabnine | Prettier |
|---|---|---|---|---|---|---|---|
| Core purpose | Quick refactoring, navigation, basic Git info | Repository‑wide history, blame, authorship | Workspace organization, project switching | Marking and jumping to important lines | AI‑powered code completion | AI‑powered code completion | Code formatting |
| UI footprint | Collapsible sidebar (~200 px) | Status bar panel + separate view | Side panel + command palette | Inline gutter markers | Command palette + status bar | Command palette | No UI |
| Keybinding model | Customisable per action | Pre‑defined shortcuts | Pre‑defined shortcuts | Pre‑defined shortcuts | Pre‑defined shortcuts | Pre‑defined shortcuts | No shortcuts |
| Git features | Inline status icons, hover blame | Full commit history, blame, graph | None | None | None | None | None |
| Refactoring support | Yes (extract, rename, move) | No | No | No | No | No | No |
| AI integration | Optional, requires API key | No | No | No | Yes (paid) | Yes (free tier + paid) | No |
| Language coverage | JavaScript/TypeScript (others limited) | All VS Code‑supported languages | All | All | All | All | All via plugins |
| Performance impact | Minor on small‑to‑medium projects | Higher memory usage | Minor | Minor | Minor | Minor | Minor |
| Pricing | Free core, paid AI (price not announced) | Free core, optional paid features | Free | Free | Free tier, paid plan | Free tier, paid plan | Free (open source) |
How to decide
| Need | Recommended extension |
|---|---|
| Quick refactor shortcuts and a small Git overview | Jarq |
| Full commit history and blame across the repository | GitLens |
| Managing multiple projects in the same workspace | Project Manager |
| Marking and navigating to important lines | Bookmarks |
| AI‑assisted code completion | GitHub Copilot or Tabnine |
| Automatic formatting according to style rules | Prettier |
The choice depends on the specific workflow. For example, a developer who spends most of their time refactoring JavaScript code may prefer Jarq, while someone who needs comprehensive Git history will likely choose GitLens.
Use Cases
1. Splitting a large function
In a file containing a monolithic function, place the cursor inside the block you want to extract, open the Jarq sidebar, and click Extract function. The extension prompts for a new function name, creates the new function in the same file (or a new file if configured), and replaces the original block with a call to the new function. Import statements are updated automatically.
2. Navigating between a component and its test
In a monorepo where components and tests share the same base name (e.g., Button.jsx and Button.test.jsx), the Open related file button scans the workspace for files with the same name but different extensions. Selecting the button opens the counterpart in a new tab, saving a manual search in the Explorer view.
3. Quick Git blame on a line
While editing a line in utils.js, hover over the small Git icon that appears in the gutter. A tooltip shows the author, commit hash, and relative date for that line. This provides a quick sanity check without opening the GitLens panel or running a terminal command.
4. Renaming a variable across the workspace
Select a variable name, then click Rename across workspace in the sidebar. Jarq runs a workspace‑wide search, presents a preview of all occurrences, and applies the rename in one step. The preview panel uses the same UI as VS Code’s built‑in rename, but the sidebar shortcut reduces the number of clicks.
Limitations
| Limitation | Why it matters | How to mitigate |
|---|---|---|
| AI feature requires a paid plan | The free tier does not provide AI suggestions. | Decide if AI assistance fits your workflow before enabling the feature. |
| Large workspaces may experience slower activation | The sidebar scans the file tree and Git status on activation. | Disable Git integration (jarq.enableGitIntegration: false) or limit the extension’s scope with files.exclude. |
| Keybinding conflicts | Default shortcuts may overlap with custom bindings. | Review jarq.customKeybindings and adjust any conflicting shortcuts. |
| Limited language support | Refactoring commands are optimised for JavaScript/TypeScript; other languages receive only generic navigation. | Use language‑specific extensions for other languages. |
| No official support for non‑JavaScript languages | Teams that rely on Rust, Go, or Java will not benefit from the refactoring shortcuts. | Pair Jarq with a language‑specific refactoring tool. |
The free core of Jarq is safe to try in a small project. If the trade‑offs outweigh the benefits, you can disable or uninstall the extension at any time.
FAQ
| Question | Answer |
|---|---|
| Where can I find the extension’s documentation? | The official README on the extension’s GitHub repository contains installation instructions, feature descriptions and troubleshooting tips. |
| Does Jarq store my API key on disk? | The extension’s documentation does not specify the storage mechanism. Users should refer to the README for details. |
| Can I use Jarq with a remote development environment? | Yes, as long as the remote environment supports the VS Code CLI and the extension is installed in the remote workspace. |
| Is there a way to limit the sidebar to specific folders? | Use the files.exclude setting to hide large directories from the sidebar scan. |
| What happens if I enable AI without a key? | The AI button will be disabled and a prompt will appear asking for an API key. |
References
- VS Code Extension Marketplace – Jarq extension page (publicly available).
- Jarq GitHub repository – README and source code (publicly available).
All information is based on publicly available documentation as of the time of writing. Features and settings may change in future releases.
Frequently asked questions
Is Jarq compatible with all VS Code versions?
Jarq requires VS Code 1.70 or newer. Older versions will not load the extension.
Can I use Jarq without an API key?
Yes, core features work without an API key. AI‑powered suggestions need a key from the Jarq website.
Does Jarq replace existing refactoring tools?
Jarq supplements existing tools; it does not replace VS Code’s built‑in refactoring commands.


