About Thor

We built Zenhub to keep builders building. Thor is what's next.

Shipping code got fast, but keeping everyone aligned is still slow and brittle. Thor fixes that part, and gives you confidence that you're building the right thing.

2014Zenhub2026Thor

git logGraph
  1. 2014ZenHubROOT

    The first project management tool built natively in GitHub. A board that lived where the code did, not in another tab.

  2. 2015–2025Decade of releases

    Boards, sprints, reports, roadmaps. Every year it got better at showing you the work.

  3. 2024The coordination gapUNMERGED

    Every board we built still needed a person to go update it. Nobody fixed that, us included.

  4. 2026ThorHEAD

    So we stopped building boards. Thor keeps the record itself, and asks when it can't tell.

Keeping the record honestLive

Software development has never moved this fast. Engineers can now ship in a few hours what used to take a week. But coordination hasn't kept up. It still moves at human speed. We move cards to reflect work that happened days ago. We write status reports so someone feels informed. We sit in standups half the room could skip. Nobody likes this work, but the alternative is worse: people working on the wrong things, blockers surfacing too late.

Launch plan · PRDEdited 3d ago

Ship behind a feature flag.

ONB-214Backlog

Descoped to next sprint.

main · a41f2cMerged yesterday

Flag removed. Shipped to everyone.

One feature, three tools, and no way to tell which one is current.

The PRD says one thing. The ticket says another. The code took a third approach.

Nobody dropped the ball; the team just moved faster than its paper trail. An agent following your prompt does exactly what it says, wrong parts included.

Why we're building Thor

Thor isn't another place to write things down. It reads the places your team already works and syncs to its record of what happened. So “where are we on this?” has an answer that doesn't depend on who last remembered to update a ticket.

  • From a meetingJust now

    You cut the backfill migration from scope. The PRD still says it's in.

    Thor spots the decisions that never make it back into the doc

  • Blocked work2h ago

    Priya has been waiting for staging access since Monday.

    Blockers surface without anyone having to escalate them

  • CommitmentThis week

    “I'll send that over.” Five days ago.

    Thor remembers who said it, and checks back

Why us, and why now

We've spent the last decade building tools for engineering teams. In 2014 we launched Zenhub, the first project management tool built natively in GitHub. It is still running, and teams still plan real work on it. Ours included.

Thor is our bet on what comes next: AI handles the coordination, so humans spend their time on what only humans can do. Figuring out what to build, why it matters, and whether it's any good.

— The Thor team

FAQs

Isn't this just search?
No. Search helps you find what was written down. Thor keeps track of what's happening around the work: what changed, what's blocked, who owns what, and where attention is needed.
Can't MCPs just do this?
Raw MCPs give agents access to tools. They don't give agents a durable picture of how the work connects across tools. Without Thor, every question becomes a fresh reconstruction job.
Is this only for agents?
No. Agents need operational context to act well. Humans need it to know where to pay attention. Thor gives both a clearer picture of what's actually happening.