01◎
Start with a goal
Describe the outcome the team is working toward. Keep intent attached to the work.
INTENT, MADE EXPLICIT NEWGIT / AGENT-NATIVE VERSION CONTROL
Version control
for the age of AI agents.
Git records the state of your code. NewGit records the reasoning around it. Goals, proposals, evidence, evaluations, approvals, and repository history become part of one auditable development system built for humans and AI agents working together.
Human decisions stay visible.
Open source · Git compatible · MCP · Agent API
THE WORK, WITH ITS CONTEXTNEWGIT / FLOW
GOAL G-02A✓
Make sign-in resilientOne goal · multiple approachesCHANGE A
Refresh token flowworkspace / agent-1CHANGE B
Session rotationworkspace / agent-2EVIDENCE RECORDED
Unit tests passedExplicit command · attached to changePROPOSALHUMAN REVIEW
Ready for a decisionRationale + evidence + approval✓
INTEGRATEDAtomic by design
snap · 9f31…Every step is versioned.01 — 05
MORE THAN A SNAPSHOTA BETTER RECORD OF HOW SOFTWARE GETS MADE
GOALS, NOT GUESSWORK✳EVIDENCE, NOT ASSUMPTIONS✳DECISIONS, NOT CONVENTIONS✳GOALS, NOT GUESSWORK✳EVIDENCE, NOT ASSUMPTIONS✳DECISIONS, NOT CONVENTIONS✳
THE MISSING LAYER
Git remembers what changed.
NewGit remembers why.
Branches and commit messages were never designed to carry the full story of work shared between people and agents. NewGit makes that story part of the repository.
THE OLD QUESTION
“
What changed?
A snapshot. A diff. Maybe a commit message.
− if (session.expired) return null;+ await refreshSession(session);
THE BETTER RECORD
“
Why, what, and what proves it?
One connected, reviewable thread—from intent to an approved integration.
GOAL→CHANGE→EVIDENCE→DECISION
A TRACEABLE PATH FORWARD
Intent to integration.
One connected thread.
Concurrent work can explore alternatives without losing shared context. The team can see what was tried, what was checked, and what was approved.
02⌘
Explore in workspaces
Isolated spaces let people and agents pursue different approaches in parallel.
ALTERNATIVES, PRESERVED03⌁
Attach the evidence
Record explicitly requested checks; distinguish deterministic results from AI-generated opinions.
CLAIMS, WITH CONTEXT04↗
Review, then integrate
Proposals put rationale, evidence, and approval in view before transactional integration.
DECISIONS, AUDITABLE START SMALL. KEEP THE CONTEXT.
A familiar CLI.
A more complete history.
NewGit gives teams a practical set of repository tools with an agent-native workflow model. Try the core commands first; add structured goals, evidence, and proposals as you need them.
Browse the CLI reference →$ newgit init myproject
Initialized NewGit repository in myproject
$ newgit goal create "Make sign-in resilient"
Created goal goal_8f2d1
$ newgit workspace create agent-session
Workspace agent-session ready
$ newgit verify
✓ Repository structure is valid
RUST · CONTENT-ADDRESSED · OPEN BY DESIGNMIT OR APACHE-2.0
BUILT ON A FEW STRONG IDEASTrust the record.
Trust the record.
Not the guess.
A.
Evidence stays honest
Supported checks are recorded explicitly. AI opinions are labeled as AI-generated—not passed off as machine facts.
B.
AI stays optional
The repository workflow works without a model. Agents use the same operations and validation rules as the CLI.
C.
Decisions stay reviewable
Proposals connect rationale, evidence, and approvals. Integration is handled transactionally.
✳More context in the repository.
People still set the bar.
People still set the bar.
AN EARLY, OPEN PROJECTBuilt in the open.
Built in the open.
Clear about what’s next.
NewGit is a pre-1.0 production candidate under active development—not labeled production ready. Review the current release gates and known limitations before choosing a deployment model.
Read known limitations → THE NEWGIT MODEL
From commits to context.
Code is only one part of the development record. Select a concept to trace the relationships around a change.
TRADITIONAL OBJECTS
NEWGIT
DEVELOPMENT CONTEXT
Related concepts illuminate one another. Select any node.CONCEPT MAP / 01
BUILT FOR AI AGENTS
Agents shouldn't be guests in the repository.
NewGit treats agents as first-class participants in software development while preserving human control, traceability, and recoverability.
HUMAN OVERSIGHTAUDITABLE ACTIONSEVIDENCE-BACKED CHANGESRECOVERABLE HISTORY
A TRACEABLE AGENT LOOPNO IMPLICIT EXECUTION
AG
Agent inspects repositorycontext.read · goal.load
09:41:02AG
Change proposed in workspaceworkspace.update · proposal.open
09:42:18✓
Requested checks recordedevidence.attach · unit_test
09:43:07H
Human reviews and approvesapproval.granted · integration
09:46:33✓ CHANGE INTEGRATED snap · b72c…
MCP + AGENT INTERFACES
A repository agents can actually understand.
NewGit includes an MCP stdio server and JSON-oriented CLI/API interfaces. Agents interact through the same repository operations and validation rules as the CLI.
Read the agent guide →01 CODING AGENT human-directed
↓ MCP stdio · JSON CLI / API
02 NEWGIT OPERATIONS same validation rules
↓ explicit, auditable operations
03 REPOSITORY RECORD goals · evidence · history
INTERACTIVE WALKTHROUGH
Watch a change
become a decision.
Step through a simulated workflow built from NewGit concepts. Each state adds context to the record.
WORKFLOW SIMULATIONNOT A LIVE REPOSITORY
EVENT 01 / 08
A developer defines the goal.
Intent is captured before code changes begin, giving people and agents a shared target.
goal.create · "Improve authentication reliability"GOAL · OPEN
REAL ENGINEERING, NOT VAPORWARE
Built like infrastructure.
Substantial implementation, documented boundaries, and an honest maturity label. Verify the evidence in the repository.
01 / STORAGECrash-aware transactionsJournaled operations · recovery02 / INTEGRITYVerify before trustObject checks · structural verification03 / TESTINGFailures are exercisedConcurrency · chaos · fault injection04 / INTEROPERABILITYGit paths, with limitsImport / export · smart HTTP subset05 / SECURITYExplicit trust boundariesRoles · audit records · threat model06 / SUPPLY CHAINDependencies in viewSBOM · license summary
PRODUCTION CANDIDATE / PRE-1.0 Review release gates ↗
GIT COMPATIBILITY
Keep Git.
Add a new layer.
NewGit is not a Git replacement. Git import/export and a documented smart-HTTP compatibility slice provide bridges to existing workflows—within clearly stated limits.
See the compatibility details →EXISTING GIT REPOSITORIES import · export · Git clients
↕
NEWGIT distinct repository model
↓
GOALSPROPOSALSEVIDENCEEVALUATIONSHISTORY
↕
HUMANSAI AGENTS
Agents → Loops →
Graphs → Systems
As software agents grow more capable, development looks less like isolated edits and more like a continuous system of goals, actions, observations, evaluations, and decisions.
NewGit is designed for that transition. OPEN SOURCE · PUBLIC REPOSITORY
See the machine.
Explore the code, tests, security model, and current roadmap. No invented metrics—just the project itself.
Explore the repository ↗MAKE THE NEXT CHANGE MORE LEGIBLE
Keep the reasoning
close to the code.
Explore the project, inspect the evidence, and help shape what comes next.