Edit code with Lemniscate in a JetBrains IDE

The JetBrains plugin's in-editor gestures: autocomplete, inline editing, accepting proposed changes, and what goes through the chat panel.

This page describes what the plugin’s gestures produce. The list of actions, their IDs and their shortcuts is in the JetBrains plugin reference, generated from the code; that reference is authoritative for exact values.

The two places the plugin works

In the editor, with nothing open: autocomplete as you type, inline editing (Ctrl+I), accepting and rejecting proposed changes, and “next edit” mode. These are the gestures this page describes.

In the panel docked on the right: chat, the agent, session history, the configuration page, and applying a code block proposed in the conversation. The panel is a web interface rendered by the IDE’s embedded browser; if your JetBrains distribution does not have one, see the last section of this page.

Edit a selection without leaving the editor

Select the code to change.
Press Ctrl+I (Cmd+I on macOS).
Describe the change in the field that appears in the editor, then confirm.

The proposal is overlaid in the file, block by block: removed lines and added lines appear in place, with no diff window.

You respond block by block, or all at once:

Gesture	Shortcut	macOS
Accept the whole proposal	`Ctrl+Maj+Entrée`	`Cmd+Maj+Entrée`
Reject the whole proposal	`Ctrl+Maj+Retour arr.`	`Cmd+Maj+Retour arr.`
Accept the block under the cursor	`Alt+Maj+Y`	`Alt+Maj+Y`
Reject the block under the cursor	`Alt+Maj+N`	`Alt+Maj+N`

Rejecting restores the original code. When one of these shortcuts is also bound to another IDE action, the plugin puts change rejection first, so that a stray keystroke does not write into your file.

The first time the plugin starts, an example file opens on its own and sums up these gestures, in your IDE’s language (Java, Python or TypeScript). It is written into your Lemniscate configuration folder; you can delete it, it does not reopen.

The bubble above selections

When you select code, two floating buttons appear above the selection. The first opens the chat panel with the selection as context. The second starts inline editing, like Ctrl+I.

To stop seeing this bubble, uncheck Display Editor Tooltip in Réglages › Outils › Lemniscate.

Accept suggestions as you type

Suggestions appear in gray as you type. Tab accepts; typing on dismisses.

They trigger at three moments: when you request them explicitly, when the document changes, and when the IDE’s completion list changes. Pausing the cursor does not trigger them.

To turn off autocomplete, uncheck Enable Tab Autocomplete in Réglages › Outils › Lemniscate. The JetBrains plugin has no quick keyboard toggle for this, unlike the VS Code extension.

The two conditions for “next edit” mode

“Next edit” mode proposes the next change elsewhere in the file and takes the cursor to it. A small window appears, where Tab accepts the jump or the suggestion and Échap cancels.

These two keys are wired into the window itself: they do not appear in Réglages › Keymap and cannot be remapped.

The mode only activates if both conditions are met:

Enable Next Edit is checked in Réglages › Outils › Lemniscate;
your autocomplete model declares that capability.

With an arbitrary model, checking the box produces nothing visible: the second condition is missing.

What Lemniscate sees of your terminal

The plugin requires the IDE’s Terminal plugin in order to install: without it, installation fails.

The agent does not see your IDE’s terminal. It sees the repository working copy, your instruction and the output of the commands it runs itself. Those commands run in the session sandbox, without your permissions, without your environment variables and without network access (security white paper V3, section 4.3).

If the panel shows text instead of an interface

Some JetBrains distributions run on a runtime without an embedded browser (JCEF). The plugin detects this and shows text instead, explaining how to switch to a runtime that supports it, and reminding you that autocomplete and inline editing remain usable without it.

The telltale sign is that there is text to read. A panel that opens empty, with not a word in it, is not this case: that is a bug, and should be reported.