Git compatibility

Keep Git. Change the workflow.

Developers keep their Git clients. Agents get native interfaces. Both paths read and write the same authoritative repository state.

Two paths, one state

Developers keep cloning, fetching and pushing with the Git clients they already use, over HTTP or SSH. Agents work through Strata's native interfaces: they get a workspace, submit candidates, receive structured conflicts and read and write context. Both paths read and write the same authoritative repository state.

Fig. 04 — Two paths, one stateSchematic
DevelopersGit clientsclone · fetch · push
Coding agentsNative interfacesworkspace · submit · conflict · context
GIT HTTP / SSH
MCP · gRPC
AUTHORITATIVE REPOSITORY STATEone history · provenance per change
POSTGRESQL · S3-COMPATIBLE OBJECTS

Supported operations

Compatibility is scoped to the operations covered by tests. The following are exercised by the reported private evaluation over Git HTTP and SSH.

OperationTransportStatus
cloneGit HTTP / SSHEvaluated
fetchGit HTTP / SSHEvaluated
pushGit HTTP / SSHEvaluated

Known limitations

The complete, operation-level compatibility matrix is maintained in the repository's release-readiness documentation. It is not reproduced here because it could not be verified against the source from this handoff. Treat compatibility as scoped to tested operations until that reference is published.

EVALUATION · NOT YET PRODUCTION-READY

by Anyabelle