llms.txt: machine-readable documentation index. Markdown version of this page is also available.

JetBrains Air Help

Interact with the agent

Once a session is started, Air in IDEs hosts it in the Agent Session View, where you can interact with the agent. By default, the view opens in a separate editor tab, and you can also open it in the Chat tool window.

Agent Session View overview

The Agent Session View holds one conversation with an agent. Here you can find your messages and the agent's replies, add context, configure the agent's settings, and perform other actions.

Agent Session View with numbered callouts for run mode, project, prompt library, context, voice input, send, agent preset, settings, and authorization.
  1. Run mode: Choose where the agent runs:

    • Local – on your machine, in the project directory.

    • Temporary Worktree – on your machine, in a separate Git working copy of the project.

    • Cloud – on JetBrains infrastructure, in a cloud clone of your repository.

  2. Project: Select the project that the session works with.

  3. Prompt library: Save prompts and reuse them for recurring tasks instead of typing them again.

  4. Add: Attach project files, folders, commits, or other context to the request.

  5. Start Voice Input: Dictate your request instead of typing it. Air in IDEs turns the recorded speech into prompt text.

  6. Send: Send the request to the agent.

  7. Agent preset: Click the selected agent to choose another agent preset.

  8. Agent settings: Configure the model, effort, and operation mode for the next request. The availability of these settings depends on the agent.

  9. Authorization: Select the authorization source that the agent works through. For more information, refer to Select the authorization for a session.

After you send the first prompt, a context indicator also appears in the text field.

Agent Session View with the context indicator tooltip open, showing the percentage of context used and the used, available, and capacity token counts.

Hovering over it shows how much of the model's context window is used in the current session. Prompts, attached context, and agent responses contribute to this usage, and the indicator updates as the session continues.

Configure agent settings

The chosen preset starts the agent with pre-configured settings, such as the model, effort level, and operation mode. You can change these settings for the current session using two controls below the text field:

Session controls under the prompt field showing the selected agent, the model and effort selector, the operation mode selector, and the authorization source.
  • Model and effort settings: To configure the model and its settings, either click the model name or press Ctrl+Shift+M and select the required options:

    Model and effort settings popup opened above the text field for Codex, showing the Model row with 6 Astra selected, the Effort slider set to High, and Fast mode turned off.
    • Model – click to open the list of available models and select the model that processes your requests.

    • Effort – use the slider to select how much reasoning effort the model uses.

    • Other model-related options – enable or disable other model settings, such as Fast mode.

  • Mode: Choose which actions the agent can perform without asking for confirmation. The popup can also hold agent modes, such as Plan or Goal.

    Mode list opened above the text field for Codex, showing the Read-only, Workspace access, Auto review, and Full access modes with Read-only selected, and Plan and Goal turned off.

Reduce AI credit usage with Eco mode in Junie

Junie, JetBrains' coding agent, provides an Eco mode that can reduce AI credit usage by sending routine implementation work to a smaller, cheaper companion model while keeping your selected model for planning and more complex tasks. Junie selects the companion model automatically, so you do not need to choose it separately.

Eco mode does not replace the model that you select. Junie uses your selected model to plan the task and make complex decisions. After planning, it routes suitable routine implementation steps to the companion model. The work of both models appears in the same session, as one conversation with the agent. The companion model can differ depending on the selected model, its provider, and the effort level.

Eco mode is not available for every model. Whether you can turn it on depends on the selected model, its provider, and the effort level. The free Lite model of Junie Lite does not support Eco mode.

To turn Eco mode on or off, use the Eco mode option in the model and effort settings. When Eco mode is on, appears next to the model and effort settings below the text field.

Model and effort settings popup for Junie with Claude Opus 5.5 selected, the Effort slider set to Medium, and Eco mode turned on, and the Eco mode icon next to the model and effort below the text field.

If you select Default in the Junie model list, Eco mode is turned on automatically. This option offers a recommended balance between the quality of the results and the cost.

Attach context

Click Add in the text field to search for context to add. The popup lists the recent files first and offers the following sources:

Context picker listing Project Files and Folders, Upload from Computer, Context from Screen, Commits, and Skills, plus a list of recent files.
  • Project Files and Folders: Any file or directory in the project.

  • Upload from Computer: A file outside the project, such as a log or a specification.

  • Context from Screen: A screenshot. On macOS 14 and newer, this opens the native window and display picker, which can capture another application even when its window is behind the IDE, and shows an Attach/Retake/Cancel preview before you add the capture.

  • Commits: One or more commits from the repository history.

  • Skills: A skill that tells the agent how to perform a specific kind of task.

Air in IDEs adds these attachments to the prompt that the agent receives, so the agent works with the context required for the task.

Request field with two project files attached as context and the Summarize files, Map impact, and Find duplication suggestions above them.

As an alternative, you can use the Add to Agent Context action to hand a specific part of your project to an agent. To do this:

  1. Right-click a selection in the editor, a file in the Project tool window, a console, a test in the test runner tree, or a change in a version control view.

  2. Select Add to Agent Context from the context menu.

    Project tool window context menu for a selected file with the Add to Agent Context option highlighted above Find Usages.

Compose and send a request

To prepare a prompt for the agent, write your request in the text field using natural language. If you need to span the request across multiple lines, press Shift+Enter to start a new line.

Alternatively, you can dictate the request, reuse your previous prompts, use suggestions provided by Air in IDEs when composing a prompt, accept follow-up prompts suggested by the agent, or reply to a part of an agent response.

Dictate a prompt

Instead of typing a request, you can dictate it. Click Start Voice Input in the prompt field, dictate the request, and click to finish the recording.

Agent Session View with the Start Voice Input button highlighted and the recording of a request.

Air in IDEs transcribes the recording and adds it to the prompt.

Use prompt suggestions

After you add context, Air in IDEs can show predefined prompt suggestions in the text field. The suggestions are based on the type and context of the attachments and help you formulate a request for them.

Request field with two project files attached as context and the Summarize files, Map impact, and Find duplication suggestions above them.

Click a suggestion to add it to the request, then edit as needed before sending it.

Use follow-up prompts

After completing a task or a step, some agents can suggest a follow-up prompt for the next possible action. For example, an agent can offer to commit the changes after editing files, or to delete the files that it found safe to remove. The suggestion appears in the empty text field.

Text field showing the commit this follow-up suggestion below a list of four files changed since the last turn.

Press Tab to insert the suggested prompt into the text field, then edit it as needed and send it to the agent.

Reply to a part of an agent response

To ask the agent about a specific part of its response, select the text in the response and click Reply next to the selection.

Agent response with part of the text selected and the Reply button shown next to the selection.

Air in IDEs adds the selected text to the text field as a quote. The request is not sent yet, so add your question or comment after the quote, then send the request to the agent.

Reuse prompts

To reuse your previous prompts, click the Open prompt library button in the top-right corner of the text field and select the required entry from the Prompts dialog.

Prompts dialog listing previously used prompts, each labeled Recent and tagged with the agent and whether it starts a new or existing thread.

You can save a prompt by clicking the Save to Prompts button next to it. Saved prompts appear at the beginning of the list.

Add a prompt to a queue

While the agent is working, you can draft another prompt in the text field and add it to the queue. The agent processes queued prompts in order after it finishes the current request.

  1. While the agent is working, type your next prompt in the text field.

    Agent Session View showing a draft follow-up prompt in the text field and the button for adding that prompt to the queue.
  2. Send the request. The prompt is added to the queue, and the queue counter shows the number of prompts waiting to be processed.

To manage a queued prompt, use the controls displayed next to it:

Agent Session View with a queued prompt's more-actions menu open, showing Edit Message, Delete, Open in New Chat, and Turn Off Queueing.
  • Click Send now to send the prompt immediately.

  • Click the button and select Edit Message to change the prompt, Delete to remove it, or Open in New Chat to start a new session with the selected prompt.

    Select Turn Off Queueing to stop sending the agent queued prompts, pausing their execution.

  • Hold a queued prompt by the icon and drag it to the required position in the queue.

If the queue is paused, click Resume next to the queue header to continue processing the queued prompts.

Agent Session View showing a paused prompt queue and the Resume control next to the queue header for continuing queued prompts.

Answer agent questions

Sometimes an agent might request specific details from you. In these cases, Air in IDEs displays an interactive form containing a question and a list of suggestions on how to proceed with the task. The session pauses until you submit or dismiss the form, and your answer is added to the chat as a single summary block.

Agent Session View showing an agent question with numbered answer choices, a recommended option, and Skip and Submit controls.

Use the up and down arrow keys to navigate the choices. Press Enter to confirm the selected choice, or press Esc to close the form.

06 November 2026