Changes & the inspector
Keep or discard each change, send notes to the agent, and see what fills the context window.
Changed Files
The inspector (⌥⌘B) opens with Changed Files: every uncommitted change in the project, with lines added and removed. The status bar shows the dirty file count and totals too.
For a file or a single hunk:
| Action | What it does |
|---|---|
| Keep | Keep the changes: stage them. |
| Discard | Discard the changes: restore the file from HEAD. |
| Keep with note / Discard with note | Add "a note for the agent about this change, sent with your next message". |
Keep all and Discard all, next to the totals, do the same for every file. Discard all asks once, and deletes new files.
Commit and pull request
- Keep the files to commit. A commit box appears under the list.
- Write the message. On the default branch, KodaCode also asks for a new branch name, made from the message and the Branch name prefix. It switches to that branch before it commits, so the default branch does not change.
- Click Commit. Only kept files go into the commit.
- Click Create PR →. The pull request screen shows the branch, the target branch, the title, the description and the commits.
- Click the button to push the branch to
originand create the pull request.
The button depends on the access token in Source version control settings:
- With a token saved for the provider and organization, KodaCode creates the pull request and shows its number and link.
- Without one, KodaCode pushes the branch and opens the provider's own new pull request page in your browser. You create it there.
When the branch already has an open pull request, the link reads Update PR #N. The screen shows how many commits are not pushed yet, and loads the pull request's title and description. Push and update pushes the new commits and saves any change to the title or description. Close, Abandon on Azure DevOps or Decline on Bitbucket, ends the pull request without merging after one confirmation. The branch and its commits stay. Only GitLab lets a pull request change to or from a draft after it opens. This needs the access token, because KodaCode asks the provider whether a pull request is open.
KodaCode reads the provider from the remote's address: GitHub, GitLab, Azure DevOps, Bitbucket and AWS CodeCommit. For a self-hosted GitHub Enterprise or GitLab server, add it in the settings with its address.
For a goal's changes, the panel shows Merge, Create PR and Discard. Create PR pushes the goal's own branch and opens the pull request from it. Your checkout does not change.
Waiting crew jobs
Crew jobs that ended without landing show under Waiting crew jobs, whichever session started them. Click a file to see its diff in the job's copy. Apply lands the job in your working tree, uncommitted. Discard removes the copy.
Delegation tree
Sub-Agent Delegation Tree shows the main agent and the agents it handed work to. Manage opens the Agents screen.
Context Graph
Context Window Capacity shows how full the model's context window is. When it reaches the Context ceiling, KodaCode compacts older messages.
Active semantic graph lists the changed files in the code graph. Show in the graph opens one on the graph screen.
Costs and logs
/metrics(⇧⌘U) shows what this session's calls cost: Model calls, by provider, Shell output savings, By command and Older results savings./logs(⇧⌘E) shows what KodaCode logged, filtered by category.