Checks every commit you push against what you asked your coding AI for

Build with AIand you lose track ofwhat you're building.

DevHive reads your intent from what you asked your coding AI and from your tests, then checks every commit you push against it.
Where the intent falls short, it asks first instead of filling it in.

Open to invited teams first

  • It doesn't run your codeIt only reads your repositories
  • It doesn't change your codeIt only proposes the connection setup as a PR
  • It doesn't make up intentWhen intent falls short, it asks first
  • It doesn't judge right or wrongIt only checks the code against the intent as written
Features

From request to answer,
without opening the code

From collecting your requests to asking about missing intent, DevHive follows each commit and takes on the work along the way.

01Requests

Gather scattered intent, one line each

Pulls requirements out of what you asked your coding AI, your test code and your own answers, one per row.

02Commit check

Every requirement gets a verdict

Row by row, it marks whether the changed code in a pushed commit keeps the requirement, keeps it only if assumed, differs from it, has no code for it, or can't be told.

03Flow

Follow the changed code with example values

Shows what each changed function calls as boxes and arrows, and fills in how an example value flows at each step.

04Code map

Reads your repository first and maps its functions

Links function calls from syntax alone, with no model call. The code behind each verdict, the tests that reach it and what spills outside the request all come from this map. Click a function to see its neighbors.

05Assumptions

What the request left open is marked as an assumption

When the AI decided something the request never said, it's marked 'Only if assumed'. If it's right, confirm it as an answer; if not, send a fix request.

06Questions

What isn't written becomes a question

What the request doesn't say is asked, not filled in. Your answer goes into the intent and the commit is checked again.

07Fix request

Questions and fix requests go to your coding AI

See a Differs or an Unknown, send a fix request, and your coding AI picks it up and fixes it. Push the new commit and it's checked again.

Questions that go back to the developer look like this

What happens when the coupon is larger than the payment?Does the coupon apply to web and app checkout too?What happens to a coupon past its end date?What happens if the pay button is pressed twice?The request and the tests disagree. Which one is right?
How it works

Here's how one commit goes through

Connect DevHive to the coding AI you use and ask as you always do. When you push, DevHive takes the commit, checks it against your intent and, if there's something to look at, puts it in Needs attention.

  1. 01

    Connect your coding AI and ask

    MCP and a hook keep the request text

  2. 02

    Intent comes from requests and tests

    Each requirement row quotes its source

  3. 03

    Every pushed commit is checked

    Marked as asked, only if assumed, differs, no code or unknown

  4. 04

    Missing intent becomes a question

    Your answer goes into the intent and the commit is checked again

Coding AI

Works with the coding AI you use

Connect over MCP and your coding AI keeps your request text and answers DevHive's questions.

DevHive MCP

One per person

https://getdevhive.com/mcp

Claude Code

Adds .mcp.json and the request hook to your repository. Open it from the repository's top folder.

Codex

Add it once to your global settings and approve the hook.

For teams

Bring repositories and people
into one project

Split the work by role, and every action is on record.

08Projects

Several repositories, one project

Reads only the repositories you allow in the GitHub app.

09Roles

Each role can do different things

Only admins change settings and members.

10Activity

Every action is on record

Requests, commits, checks and questions, in order.

11Korean · English

Use it in two languages

The app screens and the questions come in Korean and English.

DevHive doesn't judge whether your request is right.It only checks the code against the requests and tests as written.

What it couldn't check stays UnknownWhat the AI assumed is marked as assumedPeople approve and merge
FAQ

Questions people ask
before they start

Does it run my code?

No. It only reads the repositories you pick. It doesn't install or build anything.

Does my code go to an AI model?

Yes. To check a commit it sends the changed files, the request text and parts of the tests to an AI model. You choose which repositories it can read when you install the GitHub app.

Which coding AIs does it work with?

Claude Code and Codex. They connect over MCP, and a hook sends the request text. The Connect your coding AI screen writes the setup files.

Which languages can it read?

When you connect a repository, it builds a map of its function calls first. TypeScript and JavaScript are read down to individual functions. Other languages are read file by file.

What if my intent is wrong?

DevHive doesn't judge whether your intent is right. It only checks the code against the intent as written, and what it couldn't read stays Unknown.

Does it approve or merge for me?

No. People approve and merge on GitHub. DevHive only checks commits and asks.

Do the results show up on GitHub?

It can leave commit check results on GitHub. It doesn't write PR comments or reviews.

What GitHub permissions does it need?

Reading code and commits, proposing the connection setup as a PR, and leaving commit check results on GitHub.

See whether you got
what you asked for

Open to invited teams first