Task context
Context is the information the agent uses to understand your project and produce a correct change. The more relevant the task context is, the fewer assumptions the agent has to make.
Good practice is to add just enough context to point the agent to the right code: the relevant files, the current changes, and any examples that show the expected behavior.
Add context
On the New Task page, you can reference files and folders, Git branches, and Git commits of the selected repository, and upload files from your machine. Once the task runs and the Air Teams editor opens, the task's cloud environment is behind the task input, so you can also reference local changes and add code or terminal output straight from the editor.
Add context from the task input
In the task input, type
@.Select a context item from the list: Files and Folders, Git Branches, Git Commits, or, in a running task, Local Changes.
Alternatively, start typing after
@. The search runs immediately through files and folders.Press Enter to add the selected item.
To add more context items, type
@again and repeat the same steps.
Upload a file from your machine
Under the task input, click
and select Upload from Computer.
Select the file. It appears in the task input and goes to the agent with your prompt.
Add context from the editor
Use editor selection when a specific snippet is the most relevant context for the task. This works well when you want to point the agent to the exact code that needs attention, for example, the buggy logic, the API boundary, or the code you want to refactor.
Select any code and click Add to Task to attach it to the task. If you want to leave feedback for a follow-up iteration, click Add Comment instead – see Comment on changes.
Add terminal output
In the Terminal tool, select the output you want the agent to see, for example, an error message or a failing test run.
Right-click the selection and select Add Terminal Selection to Task.
To attach a whole file or folder, right-click it in the Files tool and select Add to Task.
Files and folders
Attach files when the change is local and you already know the file to edit. Attach folders when the change spans multiple files in the same area.
Prefer a small folder over the entire repository. Large context can make it harder for the agent to focus on the correct code.
Git branches
Reference a Git branch when the task depends on code that is not on the branch the task starts from. This is useful when you want the agent to inspect another line of work or compare approaches.
Git commits
Reference a commit when you want the agent to explain a change, identify the cause of a regression, or use a known-good version as a baseline.
Commits are also useful as evidence: this behavior worked in commit X.
Uploaded files
Upload a file when what the agent needs isn't in the repository: a log from production, a screenshot of a broken page, a specification, or sample data.
Terminal output
Add terminal output when the agent needs to see what happened when you ran something: a stack trace, a build error, or a test report. Select only the relevant part, not the whole session.
Local changes
Attach local changes when you want the agent to continue from the edits you made in the task by hand. This is useful for finish what I started tasks, or when you want the agent to review a diff and suggest fixes.
Local changes reduce back-and-forth because the agent sees the exact state of the task's working tree.