Files
GitHop/README.md
T
Hop 68d8bf2f7d Install portable agent-neutral Hop skill and documentation
Hop-State: A_06FN69X2VW0BAXG4A4DT6V0
Hop-Proposal: R_06FN69VET1STZNKPWK913K8
Hop-Task: T_06FN637799RW5Q7WH9H6PJR
Hop-Attempt: AT_06FN63779BJRBK1VFQ94GRR
2026-07-11 14:48:54 -07:00

90 lines
3.6 KiB
Markdown

# Hop
**Prompt-native version control for coding agents.**
Hop remembers why code changed, not just what changed. Every instruction becomes
a durable project state before an agent starts working. Agents get isolated
workspaces, validate the final result, and safely land accepted work in the
project folder you opened.
Git remains the source-tree and interoperability layer. Hop adds the context
agent workflows are missing: prompts, lineage, checkpoints, validation evidence,
and safe multi-agent integration.
## Why Hop
- **Intent is versioned.** Each prompt is connected to the code it produced.
- **Agents stay isolated.** Parallel tasks do not edit the same working folder.
- **Integration is intelligent.** Compatible changes merge automatically;
genuine conflicts return to an agent for reconciliation.
- **Validation follows the code.** Checks run against immutable work and the
exact final tree before it becomes accepted.
- **Accepted work is visible.** Successful results appear in the selected
project folder without moving your active Git branch or index.
- **History stays local by default.** Detected credentials are redacted before
prompts and evidence are persisted.
## How it works
```text
prompt → durable intent → isolated agent work → validate + merge → accepted code
```
Hop ships an open [Agent Skills](https://agentskills.io/) bundle and a controller
protocol. The skill makes prompt capture the agent's first repository action; a
controller can capture before model delivery. Both use the same state,
workspace, validation, reconciliation, and landing protocol. Codex Desktop is
one bundled integration, not a boundary of the product.
## Install
Hop requires Git 2.40 or newer.
### macOS and Linux
```bash
curl -fsSL https://githop.xyz/GnosysLabs/Hop/raw/branch/main/scripts/install.sh | sh
```
### Windows PowerShell
```powershell
irm https://githop.xyz/GnosysLabs/Hop/raw/branch/main/scripts/install.ps1 | iex
```
The installer adds the Hop CLI and writes the same embedded skill version to
`~/.agents/skills/hop` and `${CODEX_HOME:-~/.codex}/skills/hop`. For CLI-only
installation, source builds, version pinning, custom locations, and
verification, see the
[installation guide](https://githop.xyz/GnosysLabs/Hop/wiki/Installation).
## Get started
1. Install Hop.
2. Open a Git project in an Agent Skills-compatible client, or make it the
controller's working directory.
3. Ask the agent to make a change as you normally would.
That is the full user workflow. You do not run `hop init`, route prompts through
a terminal, or work inside `.hop` yourself. After a task, `hop status` shows the
accepted state and whether the visible project folder is synchronized.
For example, Codex Desktop users restart Codex after installation, select a Git
project, and prompt normally. Other compatible runtimes can read the shared
skill bundle or receive a single-target installation with the explicit
`hop skill install --path /path/to/agent/skills --force` form.
Hop is currently an early alpha. Expect its state model and CLI to evolve before
1.0.
## Documentation
- [Getting started](https://githop.xyz/GnosysLabs/Hop/wiki/Getting-Started)
- [Agent workflow](https://githop.xyz/GnosysLabs/Hop/wiki/Agent-Workflow)
- [Parallel agents and conflicts](https://githop.xyz/GnosysLabs/Hop/wiki/Parallel-Agents-and-Conflicts)
- [Core concepts](https://githop.xyz/GnosysLabs/Hop/wiki/Core-Concepts)
- [CLI reference](https://githop.xyz/GnosysLabs/Hop/wiki/CLI-Reference)
- [Security and privacy](https://githop.xyz/GnosysLabs/Hop/wiki/Security-and-Privacy)
- [Architecture](https://githop.xyz/GnosysLabs/Hop/wiki/Architecture)
- [Product blueprint](docs/product-blueprint.md)