Git Backup Remote
An external Git repository, connected over SSH, that receives a copy of an agent's workspace after each task.
Git backup remote is an optional configuration on an Agenhood agent that connects the agent's workspace to an external Git repository over SSH, so a copy of the agent's files is pushed out automatically every time a task finishes, independent of Agenhood's own snapshot storage.
How it works in Agenhood
Every Agenhood agent owns a persistent workspace volume that survives restarts, pauses, and archival. When a git backup remote is configured, the operator supplies an SSH deploy key scoped to a remote Git repository, for example one hosted on GitHub, GitLab, or a self-hosted Git server. Once that key is in place, Agenhood commits and pushes the current state of the workspace to the remote after each completed task, with no manual step required on an ongoing basis.
This is separate from Agenhood's built-in automatic snapshots, which are internal restore points the platform keeps for non-destructive rollback within its own storage. A git backup remote instead sends a copy of the workspace to storage the operator controls, expressed as ordinary Git commit history rather than Agenhood's internal snapshot format. Restoring from the remote is a manual process: an operator clones or pulls the repository and copies the needed files back into the agent's workspace, which differs from the one-click rollback that Agenhood's own snapshot timeline provides.
Why it matters
Because the backup lives outside Agenhood's own storage, it stays available even if the platform's database, storage layer, or the agent's container is lost or misconfigured. It also gives the workspace a full, browsable commit history that can be inspected, diffed, or checked out with standard Git tooling, on a timeline separate from the agent's runtime state. Teams that already review and audit changes through Git gain a natural way to bring agent produced files into that same process, and an operator can scope the deploy key narrowly, for example granting write access to only the single backup repository rather than a broader account.
Related concepts
Pushing generated or working files to an external version control system on a recurring trigger, whether a deploy, a build, or in this case task completion, is a common pattern across development and agent infrastructure; it is not specific to Agenhood. Deploy keys, SSH based remotes, and automatic commits are standard Git and DevOps mechanisms, applied here to an agent's working files instead of an application's source tree.