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.