Using itChanges
Changes
A change is an agent’s committed work on one branch, shown in the apps so you can
read it and comment on it without a push or a forge. The diff plugin
([plugins.diff]) keeps them.
- Committed code. A change is the branch against its base, from the commit where they forked. Its Uncommitted view shows what is not committed yet, apart: never part of a revision or merged state.
- Revisions. Each new tip is a revision: a new commit, a rebase, a squash, or an amend. Earlier revisions stay browsable, also after the branch is deleted.
- Merged. A change says when it reached its base: merged or fast-forwarded, rebased or cherry-picked, squashed, or partly.
- Links. Commits link to the repo’s forge once they are on its remote. GitHub pull requests link too.
- Kept. Changes are never removed on their own. Agents close their own, managers
their members’; only
vendetta diff forget IDfrom your own shell removes one.
In the apps
Section titled “In the apps”Changes in the sidebar lists every change, filtered by state, project, and agent; its count is changes with open comments. A chat’s menu has Changes for that agent’s. A change has three views:
- Branch vs main (or its base): the whole branch against where it forked, its revisions, and how far the base has moved on since.
- Commits: the branch’s commits, newest first, with author, size, and age; each opens its own diff.
- Uncommitted: staged, unstaged, and untracked changes in the agent’s work tree, read when you open it and when the agent’s turn ends. A machine’s work tree is its container’s, so Uncommitted does not show it; its commits show as any agent’s.
Diffs are unified when narrow and side by side when wide. A view shows its first 300 files, and the first files’ diffs; the rest load when you open them. Lockfiles, generated files, binaries, and very large files start collapsed.
Select a line or a range in the diff, or use a file’s comment button, and write a note. Send them together: they reach the agent as numbered marks, as marks on photos and videos do, and show as threads on the lines, in any view. A thread follows its line’s content: when later code moves it, the thread moves with it; when the line changed, the thread shows as outdated. A comment on uncommitted work stays there until the agent commits: it then moves onto the change’s next revision, on the line with the same content, or shows as outdated when that line changed before it was committed. From then on it shows in Branch vs base and on the commit that added its line.
In the chooser
Section titled “In the chooser”Changes is a tab beside the overview (Tab), and an agent card’s actions (a) have
Changes for that agent’s. A change scrolls as one column, its diff unified: the
arrows move line by line, Enter or ←/→ fold a file, ] and [ go from file to file,
and Enter on the tree’s file opens it on top. Press m on a line, move to take more,
and m again to write the note; m on a file’s header marks the file. M sends the
marks with a message, as the apps send them.
For agents
Section titled “For agents”Agents open and keep changes with vendetta diff (open, update, list, show,
addressed, close; vendetta diff --help), and send their link,
vendetta://page/diff/change-ID, instead of a forge link. The vendetta skill says
how. An agent ending its turn with commits on its branch in no change is told once
per tip (nudge = false turns it off), and its Changes page notes them.
Where it is kept
Section titled “Where it is kept”~/.local/state/vendetta/diff/: changes.json (changes, revisions, merged state,
and where each comment was, never its text, which stays in the agent’s chat), and
mirrors/, a bare copy of each repo with every revision pinned. Vendetta reads a
repo only through that copy, never running its hooks or config.