Code view

The code view lets you read what the agent changed. Open a ticket and scroll to the Code card. It is read-only: nothing on it edits a file, commits or pushes.

When to use it

Use it to review a change before you approve it, to see why the reviewer passed it, or to look back at what a shipped ticket did. It needs no setup and uses no model work.

What it shows

Changes lists every file the ticket changed, with how many lines were added and removed. Choose a file to see its diff. Next to the diff, Why shows what the run recorded about that file: the evidence the review cited for each acceptance criterion, the findings of the review and the independent check, and the findings of the security scan. Above the list you see the run's overall decision, the review summary, the risks it named and what the agent says it did.

Where the change comes from depends on the ticket:

• A shipped ticket shows the commit it made.
• A ticket waiting for you (Needs review, or a change held for approval) shows the change its last run left, before anything is committed. Choose Review Changes in the notice at the top of the ticket to jump there. Read it, then choose Approve & commit or Reject.
• A ticket the agent is still working on shows its work in progress, marked Work in progress, not committed yet. It can still change while the run goes on, so open the ticket again to see the latest.
• A ticket that has not run yet has no changes to show.

Files shows the project's files as a tree: the commit the ticket shipped, or the ticket's own branch, or the project's working branch. Files the ticket changed are marked A (added), M (changed), D (deleted) or R (renamed), and a folder shows how many changed files it holds. Choose a file to read it with line numbers and colors for its language.

The Code theme menu switches the colors: Reqursor (the default), GitHub, Solarized or High contrast, each with a light and a dark version that follows the dashboard. The choice is kept in your browser.

The file:line evidence links in the Verdict card open the file's diff in the Code card, at that line.

Who can see it

Every role can, Viewers included, because it is the same work the ticket page already describes. An API token needs the code:read permission to read it. An install without a valid license still shows it, like the rest of its history.

What it never shows

• Files that are likely to hold secrets. Env files, private keys and certificates, credentials files such as .npmrc and credentials.json, and the folders .ssh, .aws, .gnupg and .docker are listed by name with Hidden for safety. Their content and changes are never shown.
• Anything inside .git.
• Secrets inside other files. The same masking that protects run logs hides stored secrets and anything shaped like a token or key before a file or a diff reaches your browser.

Links are shown as the path they point to and are never followed. A change still in progress is read from the folder the agent works in, read-only, so a file in progress can be shown half done.

Limits

When it says something is missing

• "The project's repository is not cloned on this install yet." The code view fills in once the project has a clone, for example after its first run.
• "The commit this ticket shipped is not in the project's clone." The commit was made on another machine or removed. The ticket's other records stay.
• "No change is recorded for this ticket yet." The ticket has not run yet.
• "The agent has not saved any file changes yet." The ticket has run or is running, but nothing changed on its branch yet, or its folder is busy just now. Look again in a moment.