Code Execution & Workspace Tool

The Git Diff Tool

Return the diff of the working tree or between refs so an agent — and you — can review precisely what changed before it’s committed, reviewed, or merged.

Explore VDF AI Agents
SandboxedRuns in an isolated workspace
GovernedEvery action logged
AssignableTo any engineering agent
100%On-premise capable
The Execution Gap

A suggestion isn’t a shipped change

An agent that can only propose code still leaves all the work to a human. To actually deliver, it needs a real, governed workspace where it can run code, edit files, test, and use Git — safely, and without touching anything you didn’t allow.

01

Read-only agents

Suggestions still require a human to run, test, and commit everything.

02

Unsafe execution

Running agent-generated code on real infrastructure is a security risk.

03

No verification

Without tests and builds, an agent can’t know its change works.

04

Ungoverned Git

Direct repo access with no policy or audit is a non-starter in the enterprise.

How the Tool Works

Git Diff, without the risk

Capability

What it does

Show exactly what an agent changed.

it returns the Git diff for the working tree or between two references.

Tool
Git Diff

Assignable to any agent

DiffUnifiedReviewablePrecise

How it works

Predictable, inspectable behavior

Designed to be reliable.

it produces a standard unified diff from the workspace repo, so changes are reviewable by a human or another tool before anything is committed.

Governed
Policy + Audit

Every call logged

ScopedLoggedGovernedOn-prem

Governance

Private, governed, on-premise

Runs inside your perimeter.

Execution runs in an isolated, on-premise sandbox scoped per tenant with full command and file audit logging, so an agent can do real work on your code without unsafe access or anything leaving your perimeter.

100%
On-Prem

Per-tenant, logged

On-premRBACAudit logSovereign
Inputs

Parameters

The git_diff tool accepts these inputs when an agent calls it. Required inputs are flagged.

Name Type Required Description
path string
default: .
Optional Repository directory.
base string Optional Base ref to diff from (e.g. a branch or commit).
staged boolean
default: false
Optional Diff staged changes instead of the working tree.
Where it pays back

Where Git Diff pays back

Change review

Inspect exactly what an agent edited.

PR bodies

Summarize a diff into a pull-request description.

Self-review

Let an agent critique its own diff before committing.

Auditing

Capture the precise change for the record.

How VDF AI connects it

Assigned to agents, orchestrated as networks

On VDF AI, an industry’s use cases map to agents, and you assign tools like this one to those agents. Compose multiple agents into a governed, on-premise network.

ROI Snapshot

What changes after you assign it

Faster
From suggestion to shipped
Verified
Changes tested before merge
Traceable
Every command audited
100%
Code never leaves your perimeter
FAQ

Questions about the Git Diff tool

What is the Git Diff tool?

It returns the Git diff for the working tree or between two references. Assigned to a VDF AI agent, it runs under role-based policy with full audit logging so the capability is safe to use in production.

Can it diff against a branch?

Yes. Provide a base ref to diff the current state against a branch or commit.

Does it show staged changes?

Set staged to true to diff what’s staged rather than the working tree.

Does it run on-premise?

Yes. Like every VDF AI tool, it can run on-premise or in your sovereign cloud, scoped per user and audit-logged, so your data never leaves your perimeter.

How do agents use it?

You assign the tool to an agent under a role-based policy; the agent calls it as one step in a task, and several agents and tools can be orchestrated together as a governed VDF AI Network.

Put Git Diff to work

See the Git Diff tool assigned to an agent and orchestrated in a governed, on-premise network.