diff --git a/deploy/gitea/templates/home.tmpl b/deploy/gitea/templates/home.tmpl index b0e25da..0e5088c 100644 --- a/deploy/gitea/templates/home.tmpl +++ b/deploy/gitea/templates/home.tmpl @@ -1,1300 +1,435 @@ {{template "base/head" .}} -
-
-
-
-

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.

-
+
+
+

Agent-first version control

+

Tell agents what to build.Hop handles the Git.

+

Run one coding agent or many. Hop captures the request, isolates every attempt, combines concurrent edits, and routes real conflicts through an agent reconciliation loop. Once checks pass, the agent lands the result automatically by default. You do not have to manage a branch or write a commit.

+
+ {{if .IsSigned}} + Create a repository + Explore repositories + {{else}} + Create a Hop account + Why use Hop? + {{end}} +
+

Git stays underneath for compatibility. The mechanics disappear from your workflow.

+
-
-
- 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. -
  2. -
    - Attempt 01 - Human - Paused -
    -
    - Attempt 02 - Codex - Selected path -
    -
    3. -
  3. - -
    - Checkpoint · exact tree - Homepage candidate - Passed render · mobile · tests -
    -
    4. -
  4. - -
    - Proposal · frozen - Ready for review - The candidate cannot drift -
    -
    5. -
  5. - -
    - Accepted · shared state - Chosen result landed - Visible project root synchronized -
    -
    6. -
-
+
+
+

One instruction in. Working code out.

+

From prompt to landed code, without Git ceremony.

+

Hop runs the version-control workflow around your agents. You stay focused on the outcome.

+
+
    +
  1. + 01 +

    Prompt captured

    +

    Your instruction becomes durable state before any agent touches the project.

    +
    2. +
  2. + 02 +

    Agents work in parallel

    +

    Each agent runs in its own Hop workspace. Several can edit the same files at the same time.

    +
    3. +
  3. + 03 +

    Hop reconciles

    +

    Compatible hunks merge automatically. A real conflict starts an agent reconciliation loop, then runs the checks again. Ordinary code conflicts never get handed back to you.

    +
    4. +
  4. + 04 +

    Code lands

    +

    After required checks pass, the agent lands by default and Hop synchronizes the project. No manual commit, rebase, or merge.

    +
    5. +
+
+ +
+
+

Why not just Git?

+

Git stores code. Hop runs the work.

+

Git was designed to track and exchange source history, not to coordinate autonomous coding agents. Hop keeps Git underneath, then adds an agent workflow with state, isolation, evidence, reconciliation, and automatic landing after checks.

+
+
+ + + + + + + + + + + + +
Comparison of standard Git workflows and Hop
WorkStandard GitHop
StartYou create a branch or worktree.Starting a task creates an isolated agent attempt.
Save progressYou decide when and how to commit.Checks and follow-ups capture immutable checkpoints.
Parallel editsIncompatible overlapping edits require manual conflict handling.Hop three-way-merges compatible edits and sends unresolved conflicts through agent reconciliation.
VerifyValidation is conventionally attached to commits.Hop records evidence for the exact checkpoint and requires checked reconciliation.
FinishYou merge, rebase, and clean up.The agent lands checked work automatically by default.
-
-
-
-

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. -
  2. - 02 -

    Work in isolation

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

    - Attempt -
    3. -
  3. - 03 -

    Verify the exact result

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

    - hop check -
    4. -
  4. - 04 -

    Freeze the candidate

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

    - hop propose -
    5. -
  5. - 05 -

    Land deliberately

    Only the chosen result advances the accepted state. Unrelated workspace changes stay out.

    - hop land -
    6. -
-
-
- -
-
-
-

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}} -
+
+
+

Git compatibility without Git busywork.

+

Keep Git-compatible hosting and tooling underneath. The day-to-day branch, commit, rebase, and conflict choreography disappears.

+ {{if .IsSigned}} + Create a repository + {{else}} + Create a Hop account + {{end}}
{{template "base/footer" .}}