Accept changes
Accepting changes means moving the result of an agent task into the place where you continue normal development. In most workflows, this means applying the changes to a local branch, committing, and pushing them to a remote repository (either directly or through a pull request).
How you accept changes depends on where the task ran. In JetBrains Air, you accept changes from the merged diff shown in the Task Changes editor tab.
Accept changes from local workspace
If the task ran in Local Workspace, the agent applied changes directly to your working copy. To accept them, commit and push.
Commit changes
Open the Task Changes editor tab and review the staged files.
Enter a commit message and click Commit.
Push the commit to the remote repository.
Alternatively, commit and push from the Changes tool.
Accept changes from isolated environments
If the task ran in Git Worktree or Docker, JetBrains Air kept the agent isolated from your local working copy. After review, choose how to bring the result back to your local workspace.
Apply Locally: copies the uncommitted changes from the task branch to your local workspace.
Checkout Branch Locally: creates a new local branch and adds a commit with the message Auto-committed changes. The commit can include one file or all changed files, depending on where you run the action.
- How isolation works
When you start a task in an isolated environment, JetBrains Air creates a dedicated branch for the task (for example,
air/<task>) and a separate working directory managed by JetBrains Air. Your local project directory stays on the branch you started from (for example,main).Example structure:
# Your local working copy (unchanged while the agent runs) ~/Projects/my-project/ (branch: main) # Air-managed task working copy (isolated) ~/Library/Caches/JetBrains/Air/tasks/ air/<task>/ my-project/ (branch: air/<task>)
Apply changes locally
In the Task Changes editor tab, click Apply Locally.
JetBrains Air copies the changes from the task worktree back to your current working copy as uncommitted changes.
Choose how to integrate the changes: create a new branch and open a pull request, or commit and push directly to the current branch.
Check out branch locally
In the Task Changes editor tab, open the Apply Locally drop-down menu.
Click Checkout Branch Locally.
JetBrains Air checks out the task branch in your local working copy. The branch typically has the same name as the task branch, with a suffix
-copy, e.g.,air/add-new-feature-copy.Push the branch to the remote repository or open a pull request as usual.
Revert changes
Revert changes when you do not want to keep the result.
Revert a single file
Open the Changes tool. You can use the following options:
Navigate to in the main menu.
On the tool panel, click Changes.
On the Task Changes tab, click Revert next to the file name.
Revert all changes from a task
Open the Changes tool. You can use the following options:
Navigate to in the main menu.
On the tool panel, click Changes.
On the Task Changes tab, click Revert All.
Stage and commit changes
Stage the files you want to include, then commit the result. Staging means selecting which changes will go into the next commit. Only staged changes are included in a commit. Changes that are not staged stay in your working copy.
Stage files
Open the Changes tool. You can use the following options:
Navigate to in the main menu.
On the tool panel, click Changes.
In the Changes tool, select the files you want to stage.
You can click the file and select changes inside the file that you want to include.
Commit staged changes
Open the Changes tool. You can use the following options:
Navigate to in the main menu.
On the tool panel, click Changes.
In the Changes tool, enter a commit message in the commit message field.
Click Commit.
Roll back to a commit
To roll back to a specific commit, use the History tool.
Open the History tool
Navigate to in the main menu and select History.
On the tool panel, click History.
Reset the current branch to a commit
In the History tool, right-click the commit you want to roll back to.
Select Reset Current Branch To Here.
Select the reset mode:
Mixed — Keep All Changes
Keep — Keep Only Uncommitted Changes
Hard — Discard All Changes
