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.

{{if .IsSigned}} Create a repository Explore repositories {{else}} Create a Hop account Trace the workflow {{end}}

Git stays underneath. Your repositories and tools keep working.

Example task / Homepage rewrite Illustrative record
  1. Requested outcome · captured first Explain Hop clearly on the homepage. Illustrative prompt state, stored before project effects
  2. Attempt 01 Human Paused
    Attempt 02 Codex Selected path
  3. Checkpoint · exact tree Homepage candidate Passed render · mobile · tests
  4. Proposal · frozen Ready for review The candidate cannot drift
  5. 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.

  1. 01

    Capture intent before effects

    The request becomes a durable prompt state before an agent reads or edits the project.

    hop begin
  2. 02

    Work in isolation

    Every attempt gets its own workspace, so agents can explore without colliding with your accepted tree.

    Attempt
  3. 03

    Verify the exact result

    Checks run against an immutable checkpoint. Later edits cannot change what the evidence means.

    hop check
  4. 04

    Freeze the candidate

    A proposal is a fixed outcome for review, complete with its diff, evidence, and causal history.

    hop propose
  5. 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.

How familiar Git collaboration concepts map to Hop
Git viewHop view
Branch or worktreeAttemptOne isolated approach
Commit or treeCheckpointThe exact evaluated state
CI statusEvidenceProof bound to that state
Pull requestProposalA frozen candidate outcome
MergeAcceptAdvance 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 {{else}} Create a Hop account {{end}}