Hexforge

Talk it over. Approve the plan. Merge the pull requests.

Hexforge plans work on your GitHub repository, writes each change on its own branch, runs your tests, can have two models review it, and opens pull requests you merge top to bottom. Nothing is built until you approve the plan.

Works with OpenAI, Claude and DeepSeekYour keys, your checks, your rules

Example
Task Plan awaiting approval

Add a breakdown of task costs, including planning, implementation and review.

  1. 1Record what each run spends
    Implement and review a change · stored data needs a review
  2. 2Add up the spend per task
    after step 1, from its branch
  3. 3Show the breakdown on the task page
    after step 2, from its branch
After Approve & run Running
  1. Record what each run spendsdonehexforge/auto/3f2c9a41-run-spend-a1
  2. Add up the spend per taskrunninghexforge/auto/3f2c9a41-task-totals-a1
  3. Show the breakdown on the task pagependinghexforge/auto/3f2c9a41-cost-panel-a1

Each step opens its own pull request. One that builds on another starts from its branch; steps that do not run side by side.

How it works

From a conversation to stacked pull requests

  1. Talk it over

    Say what you want in your own words, with files and pictures if they help. Hexforge reads the code, asks what only you can decide, and picks how to run it. Type / to choose yourself: the workflow, a document, or no plan.

    You press Start
  2. Approve the plan

    A planner splits the work into steps, states the approach they share, and says which workflow each runs on and why. Move a step to another workflow, drop it, or ask for a revision.

    You press Approve & run
  3. Watch the steps run

    Steps that do not build on each other run side by side. Each writes its change and runs your gate command; review workflows add two reviewers. A failed step is tried again, then waits for you.

    If it waits: Retry or Resolve & continue
  4. Merge

    Every step that changes code has its own branch and pull request; a step that builds on another starts from its branch. Review them and merge top to bottom, first step first.

    Wrong after all? Redo the step
What you control

You steer. Hexforge shows its work.

Settings → Execution & checks

Your tests decide

Set a gate command, such as your build and test suite. A change has to pass it before it counts as done.

Project → Rules

Your house rules

Write down how your team works. Code rules go to the models that write code and to the ones that judge it, design and plan rules to the ones that decide and slice the work, document style rules to the ones that write a document, and pull request rules to the ones that write the pull request. A text left blank takes the console's default, where it keeps one.

New task → / → Document

A document when you need one

Ask for a document instead of code. It is written and handed to the chat, whole, with its file to download.

New task · on a branch

Your branch, your pull request

Name a branch or an open pull request in the talk, such as "continue pull request #2300". The plan reads that branch, and every pull request of the task targets it. Hexforge never pushes to your branch.

Settings → Execution & checks

A cap on what it spends

Set the most one design or one plan may spend on its models. Every talk shows what it has spent, and every model call its tokens and price.

Workflows · canvas

Workflows you can read

Every run follows a workflow drawn as steps on a canvas: model steps, checks, decisions, parallel reviews, loops with limits. Use the shipped ones or build your own.

Automations · New task

Reviews on demand, or on their own

Ask a talk to review pull request #12, or let an automation run a workflow when a pull request changes, when commits are pushed, or on a schedule. Set a rule up in a form or describe it in a chat; Hexforge checks GitHub every minute, so no webhook is needed. Two reviewers judge the change and post their verdict on the pull request.

People · seats

Seats for your team

Viewers read, operators start their own work and write workflows, maintainers manage settings and people. Invite by email with Google sign-in.

Models

Bring your own keys. Put each model where it fits.

One project model does all the work by default. Make a role under any name, give it a stronger, cheaper or different model with the effort it thinks at, and every step that asks the role uses it. A role with no model runs on the project model.

the role’s own model project model

Keys live in the project's credentials, sealed and never shown again. With a key stored, the lists of models are your vendor's own, so a new model is offered as soon as the vendor lists it.

The two reviewers ask roles of their own. Put the second on another vendor, and every diff is judged by a model family other than the one that wrote it.

Every model call is recorded with its tokens and price, and every run keeps a record of each step on the way.

Example
Resultrunning
Steps7 ran
Elapsed6m 12s

Model call deepseek-v4-pro · 1 turn · 41,208 in, 3,912 out · $0.07 · 48.3s

  1. plan approved, 3 steps
  2. step 1 started from the base branch
  3. step 1 passed the gate, both reviewers approved
  4. step 2 started from the branch of step 1
Good to know

Four promises

Approval first

A task builds nothing until you approve its plan.

Finished is not merged

Hexforge opens pull requests. Merging stays with you.

A run keeps its snapshot

Editing a workflow or a setting never changes a run already going.

Restarts lose nothing

Runs keep working through a restart, and tasks continue where they were.

Get started

One project, four settings, first task

Create a project for a repository and fill in four things; the gate command is the one you may leave for later. When its overview no longer asks you to finish the setup, press New task.

Invited by a teammate? Sign in with Google using the invited address.

  1. RepositoryPaste the GitHub link and press Clone repository. A private repository needs a GitHub token first.
  2. Model keyStore your OpenAI, Claude or DeepSeek key in the project's credentials.
  3. ModelPick the provider, the base model and, if you like, its effort.
  4. Gate commandYour build and tests, for example make test. Left blank, changes skip the check.