[FEATURE]: Expose V2 VCS status and diff APIs #34433

Activity

1. opencode-agent

   added

   2.0

   on Jun 29, 2026
2. github-actions

   assigned

   rekram1-node

   on Jun 29, 2026
3. opencode-agent

   assigned

   nexxeln

   on Jul 2, 2026
4. opencode-agent commented on Jul 2, 2026

   

   opencode-agentBot

   on Jul 2, 2026 – with OpenCode Agent

   ContributorAuthor

   More actions

   Assigned to @nexxeln from the V2 TODO LIST thread.

   Scope reminder from the original split:

   • vcs.status / vcs.diff are repository/worktree state for a Location, independent of a particular session turn.
   • Keep this separate from [FEATURE]: Expose V2 session.diff API #34434 (session.diff), which is session/message-boundary-scoped.

   Aiden noted there was a Dax/Aiden scope discussion in another thread; if found, link it here before finalizing the API shape.
5. opencode-agent commented on Jul 2, 2026

   

   opencode-agentBot

   on Jul 2, 2026 – with OpenCode Agent

   ContributorAuthor

   More actions

   Scope references from Discord:

   1. Original V2 API split:
      https://discord.com/channels/1391832426048651334/1520962938733723720/1521136350936694906

   Relevant distinction:

   • VCS APIs = current repository/worktree status + raw VCS diff for a Location.
   • Session diff API = session-scoped or message-boundary diff, used for last-turn diff, session modified-files sidebar, plugin session diff state, and app review refreshes.

   2. Older snapshot/diff scoping discussion:
      https://discord.com/channels/1391832426048651334/1518799327076810812/1518808524354748446

   Relevant contract:

   • session scope = launch directory
   • snapshot storage/path identity = Git worktree
   • patch files = absolute
   • displayed FileDiff.file = worktree-relative
   • consumers should not need to know both roots, but the implementation must preserve this distinction.
6. rekram1-node

   removed their assignment

   on Jul 2, 2026
7. nexxeln commented on Jul 3, 2026

   

   nexxeln

   on Jul 3, 2026

   Contributor

   More actions

   Implementation up in #35129. Also did the requested pass on how git-welded V2 is and what a second VCS (hg/jj) would take — summary of the coupling audit:

   Already agnostic (after #35129)

   • Wire contracts: Vcs.FileStatus, FileDiff.Info, Vcs.Mode renamed to working | branch (no git literals on the new surface)
   • Core seam: Vcs.Service is the adapter interface; the git implementation is one file (packages/core/src/vcs/git.ts) selected by location.vcs?.type. An hg adapter supporting status/diff/branch is roughly ~250-450 LOC behind the same interface.

   The real blocker for a second VCS

   • Detection: packages/core/src/project.ts Project.resolve only discovers .git (fs.up({ targets: [".git"] })), so location.vcs can never be anything else. Widening means touching core/project.ts, core/project/schema.ts (Vcs union), schema/src/project.ts (Literal("git")), plus UI guards (~8-12 files total).
   • Agent-visible copy: system-context/builtins.ts says "Is directory a git repo", plus assorted TUI/app copy that leaks git.

   Git-only territory (keep gated or hidden for non-git)

   • Workspaces/worktrees: git_worktree is the copy strategy ID down to the DB (project/sql.ts), and all create/move/delete flows assume it (~600-1000 LOC to generalize — not worth it unless the target VCS has a worktree equivalent)
   • Repository clone/cache: repository.ts / repository-cache.ts are git-remote-native
   • Snapshots: stay git per discussion — invisible to users, uses its own git store

   Suggested follow-ups

   1. hg (or jj) adapter: detection widening + adapter file + hg in CI — its own PR
   2. Plugin-registered VCS backends (the "Google doesn't have to fork" path): needs plugin API design; the adapter seam in feat(core): expose V2 VCS status and diff APIs #35129 is the hook point
   3. Rename the SnapshotFileDiff schema identifier to something neutral once the legacy SDK can absorb the break (V2 clients now standardize on FileDiff.Info)
8. opencode-agent commented on Jul 3, 2026

   

   opencode-agentBot

   on Jul 3, 2026 – with OpenCode Agent

   ContributorAuthor

   More actions

   Status from @nexxeln/Shoubhit: current VCS APIs are in, and Mercurial support is in.

   Remaining follow-up is the plugin API for VCS adapters, for systems like jj. Filed the focused follow-up as #35162.

   Source: https://discord.com/channels/1391832426048651334/1520962938733723720/1522589081282937052
9. opencode-agent commented on Jul 5, 2026

   

   opencode-agentBot

   on Jul 5, 2026 – with OpenCode Agent

   ContributorAuthor

   More actions

   Completed by merged PR #35129: V2 VCS status/diff APIs and Mercurial support are in. Remaining extensibility work continues in #35162 / PR #35166.
10. opencode-agent

    closed this as completedon Jul 5, 2026