The prompt-native forge
-Turn a clear outcome into accepted, verified work.
-Hop gives people and AI agents one shared workflow for building software: state the goal, run isolated attempts, review the evidence, and accept the result.
-The control layer for coding agents
+Keep the prompt.Prove the work.Land the patch.
+Hop captures your request before work begins, gives every coding-agent attempt an isolated workspace, and attaches checks to the exact code they evaluated. Review a frozen proposal, then land only the result you trust.
+Git stays underneath. Your repositories and tools keep working.
+-
+
-
+
+ + Requested outcome · captured first + Explain Hop clearly on the homepage. + Illustrative prompt state, stored before project effects ++
+
-
+ + Attempt 01 + Human + Paused +++ Attempt 02 + Codex + Selected path ++
+
-
+
+ + Checkpoint · exact tree + Homepage candidate + Passed render · mobile · tests ++
+
-
+
+ + Proposal · frozen + Ready for review + The candidate cannot drift ++
+
-
+
+ + Accepted · shared state + Chosen result landed + Visible project root synchronized ++
+
The missing context
+Git tells you what changed. Hop keeps the decisions around the change.
+Stop reconstructing an agent run from terminal scrollback, branches, and trust-me summaries.
+-
+
- 01What was requested? +
- The prompt, captured before any project file changes. +
- 02Who or what tried? +
- Every human and agent attempt, isolated and attributable. +
- 03What exactly passed? +
- Check evidence attached to the immutable tree it evaluated. +
- 04Which result became truth? +
- The frozen proposal deliberately accepted into shared state. +
One task, end to end
+A chain of custody for agent-written code.
+Each Hop command advances the work without separating intent from implementation or proof.
+-
+
-
+ 01
+ +
Capture intent before effects
The request becomes a durable prompt state before an agent reads or edits the project.
hop begin+
+ -
+ 02
+ + Attempt +
Work in isolation
Every attempt gets its own workspace, so agents can explore without colliding with your accepted tree.
+ -
+ 03
+ +
Verify the exact result
Checks run against an immutable checkpoint. Later edits cannot change what the evidence means.
hop check+
+ -
+ 04
+ +
Freeze the candidate
A proposal is a fixed outcome for review, complete with its diff, evidence, and causal history.
hop propose+
+ -
+ 05
+ +
Land deliberately
Only the chosen result advances the accepted state. Unrelated workspace changes stay out.
hop land+
+
Evidence is attached, not implied
+Nothing important is allowed to drift.
+Checks name the tree they tested.
A green result always points back to one exact checkpoint.
Frozen means frozen.
The proposal you review cannot quietly become a different proposal.
Acceptance is an explicit event.
The actor, policy, evidence, and result stay connected in the record.
Git compatible by design
+Hop adds a native history for agent work. It does not replace Git.
+Repositories, commits, diffs, and standard Git clients remain available. Hop changes the primary story from file history to requested outcomes and verified results.
+| Git view | Hop view |
|---|---|
| Branch or worktree | AttemptOne isolated approach |
| Commit or tree | CheckpointThe exact evaluated state |
| CI status | EvidenceProof bound to that state |
| Pull request | ProposalA frozen candidate outcome |
| Merge | AcceptAdvance shared truth |
One agent or many
+Start with intent. End with an accepted result.
+Give every agent run a reviewable chain of custody.
{{if .IsSigned}} - Create a repository - Explore work + Create a repository {{else}} - Get started - See how it works + Create a Hop account {{end}}A better unit of collaboration
-Software work begins with intent, not a branch.
-Git remains the durable home for your files. Hop makes the work around those files legible: what was asked for, who attempted it, what was checked, and which outcome became shared truth.
-Keep the why attached
-Each task starts with the requested outcome and retains its causal context, so nobody has to reconstruct intent from a terminal history.
-Try work without collisions
-Human and agent attempts run in isolated workspaces. Compare different approaches without putting your main line at risk.
-Review proof, not promises
-Checks are bound to immutable checkpoints, making it clear exactly what was verified before a proposal is accepted.
-How Hop works
-A calm, visible path from request to shared truth.
--
-
- 1
Open a task
Describe the outcome you need in plain language.
- - 2
Launch an attempt
Work yourself, direct an agent, or run both approaches side by side.
- - 3
Inspect the evidence
Review diffs, checkpoints, and the checks attached to them.
- - 4
Accept the outcome
Choose the verified proposal that should become the shared state.
-
Ready when you are