Start with Hop

What Hop adds

Git records source trees and talks to remotes. Hop adds the causal and operational layer required by autonomous coding work:

• Durable intent: every prompt is a first-class state, including follow-ups, failures, cancellations, and no-op requests.
• Isolated execution: attempts work in detached project workspaces instead of racing in the visible folder.
• Evidence: checks bind commands, output, exit codes, and source-tree identity.
• Safe acceptance: landing validates the exact integrated tree, synchronizes the selected project root, and safely aligns ordinary Git when every condition is proven.
• Intelligent concurrency: Git three-way merge composes compatible same-file edits; genuine ambiguity becomes an agent reconciliation task.
• Host independence: core workflows work with GitHub, GitLab, Gitea, generic Git servers, and local bare remotes without hosted Actions.

Version 1.1.4

These docs describe the public v1.1.4 release. This release keeps ordinary Git truthful after Hop lands accepted work: when the visible files are proven safe, Hop fast-forwards the intended local branch and index without rewriting files or using reset --hard. Existing projection-only repositories can repair themselves automatically or use hop sync-git for an exact blocking reason and safe next action. GitHub remains the canonical source and release host, while core Hop workflows continue to work with any Git remote.