The Git Branch Tool
List, create, or switch Git branches so an agent does its work on a dedicated branch — keeping changes isolated and reviewable instead of touching your main line directly.
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.
Read-only agents
Suggestions still require a human to run, test, and commit everything.
Unsafe execution
Running agent-generated code on real infrastructure is a security risk.
No verification
Without tests and builds, an agent can’t know its change works.
Ungoverned Git
Direct repo access with no policy or audit is a non-starter in the enterprise.
Git Branch, without the risk
Capability
What it does
Create and switch branches for isolated work.
it lists, creates, or switches Git branches in the workspace repository.
Assignable to any agent
How it works
Predictable, inspectable behavior
Designed to be reliable.
branch operations are logged and default an agent’s work onto a feature branch, so changes stay isolated from your protected branches until reviewed.
Every call logged
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.
Per-tenant, logged
Parameters
The git_branch tool accepts these inputs when an agent calls it. Required inputs are flagged.
default: . Optional Repository directory.
How the Git Branch tool works in practice
Git Branch is a code execution & workspace tool you assign to a VDF AI agent. It lists, creates, or switches Git branches in the workspace repository. Its hallmarks — Branch, Isolate, Create — let an agent rely on it as a dependable step in a larger task rather than a brittle one-off script.
Under the hood, branch operations are logged and default an agent’s work onto a feature branch, so changes stay isolated from your protected branches until reviewed. It expects action as required input, so calls are explicit and easy to audit. Every call is scoped to the requesting tenant and written to an audit log, so the capability is safe to run inside a regulated, on-premise environment — the same governance model behind every VDF AI tool.
Teams reach for Git Branch when they need to handle isolated changes, feature flow, and safety. It rarely works alone — pair it with Git Status, Git Commit, and Git Create Pull Request to build a complete, governed workflow, then compose those steps into an on-premise VDF AI Network.
Where Git Branch pays back
Isolated changes
Put an agent’s work on its own branch.
Feature flow
Create a branch per task automatically.
Safety
Keep protected branches untouched until review.
Parallel work
Let multiple agents work on separate branches.
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.
What changes after you assign it
Questions about the Git Branch tool
What is the Git Branch tool?
It lists, creates, or switches Git branches in the workspace repository. 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.
Does an agent commit to main directly?
No, by design. Work defaults to a feature branch that goes through a governed pull request.
Can it list branches?
Yes. Use the list action to enumerate existing branches.
What inputs does the Git Branch tool need?
It requires action, and optionally accepts name and path. Each parameter is validated when an agent calls the tool, and the full call is logged for audit.
Which tools pair well with Git Branch?
Git Branch is commonly assigned alongside Git Status, Git Commit, and Git Create Pull Request. On VDF AI you compose several tools and agents into a single governed, on-premise network.
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.
Assign Git Branch to these agents
These VDF AI agents can be assigned this tool. Open an agent to see the full toolkit it can run.
Tools that work well alongside this one
Where this tool delivers value
Put Git Branch to work
See the Git Branch tool assigned to an agent and orchestrated in a governed, on-premise network.