Thor vs. Unblocked: Two Kinds of Context for Agents

If you’re looking for a way to give Claude Code or Cursor more than the code, you’ll run into both Thor and Unblocked. They get compared because they use similar words. Both talk about context for coding agents, and both connect to Slack, GitHub, and Linear. The jobs they do are different, and the right pick depends on which problem you actually have.

Unblocked is an engineering knowledge engine. It reads your code, pull requests, issues, docs, chat, CI, and production tools, and answers questions about them for people and coding agents. Thor keeps a current record of what your team decided across Slack, GitHub, Linear, and meetings, and proposes updates to your tickets when a decision changes, which a person approves. Unblocked helps an agent understand the codebase. Thor helps it know what’s been decided.

Full disclosure: we make Thor. Everything about Unblocked here comes from its public website, docs, and pricing page as of October 2026. If something’s changed, tell us and we’ll fix it.

At a glance

What Unblocked does well

Unblocked is built around one question: what does an engineer, or an agent, need to know to work correctly in this codebase? It reads across a wide range of engineering tools and answers in a web app, in Slack and Teams, in VS Code and JetBrains, and through an MCP server that coding agents can query before they start work.

Three things stand out:

• Breadth of engineering sources. It connects to every major code host, including self-managed GitLab and Bitbucket Data Center, plus Jira, Confluence, CI pipelines, Datadog, and Sentry. If your team runs on Atlassian or a self-hosted stack, that matters.
• Code-level answers. “Why does this service retry seven times?” or “Where is rate limiting handled?” are the kinds of questions it’s made for, with answers drawn from code, pull request history, and docs together.
• Built-in code review and a coding agent. It reviews pull requests and can take a task and hand back a draft pull request, all through your normal review process.

If your main problem is that engineers, or agents, spend too long working out how the codebase works, Unblocked is aimed squarely at that.

What Thor does differently

Thor is aimed at a different gap: the record of the work goes out of date. Decisions get made in a meeting or a Slack thread, and the Linear ticket or GitHub issue never hears about it. A coding agent then reads the ticket and builds what the team already changed its mind about.

Thor is the context infrastructure for AI-native software teams. It keeps one current record of what your team decided, changed, and left stale across Slack, GitHub, Linear, and meetings. Three things follow from that:

• It reads meetings. Decisions and action items from Google Meet, Zoom, and Teams calls become part of the record, with a link back to where they were made.
• It keeps tickets in sync. When a decision changes, Thor proposes the update to the Linear or GitHub issue. A person approves it before it becomes official, and every change can be undone.
• Agents get the decision, not just the ticket. Through Thor’s MCP server, a coding agent can ask for a context pack on a Linear or GitHub issue and get back the related decisions, docs, meetings, and work. We’ve written more about why that matters for coding agents.

Thor isn’t a code search engine and doesn’t review pull requests. It doesn’t connect to Jira, GitLab, or Confluence today. If those are central to how you work, that’s worth knowing up front.

Which one should you use?

Choose Unblocked if your hardest problem is understanding a large or old codebase, your team runs on Jira, Confluence, GitLab, or Bitbucket, or you want AI code review in the same product.

Choose Thor if your hardest problem is decisions not reaching the tickets, your team works in Slack or Teams with Linear or GitHub, and you want someone to approve every change before it becomes official. Thor also handles the follow-through around that record: standups, meeting action items, and weekly status updates.

Use both if you want agents that understand the code and know what’s been decided. They don’t overlap much: Unblocked answers “how does this work?”, and Thor answers “what did we decide, and is the ticket still right?” Both connect to coding agents over MCP, so an agent can use each for its own question. Our list of the best MCP servers for engineering teams covers how to keep that setup small.

FAQ

Is Thor an alternative to Unblocked?

Partly. Both give coding agents context beyond the code. Unblocked focuses on engineering knowledge: code, pull requests, docs, and production tools. Thor focuses on keeping the record of decisions current across Slack, meetings, Linear, and GitHub, and updating tickets when things change. Some teams will want one, some both.

Does Unblocked update Linear or Jira tickets?

Not according to its public docs. It reads Linear and Jira as sources, and its MCP tools are read-only. It does write in the code host: review comments, failure reports, and draft pull requests.

Does Thor read meeting transcripts?

Yes. Thor connects to Google Meet, Zoom, and Microsoft Teams meetings and pulls out decisions and action items, linked to where they were said. Unblocked doesn’t list meetings as a source.

How do Thor and Unblocked price?

Unblocked charges per user: $29 per user per month billed annually, or $35 monthly, with Enterprise on request. Thor charges for completed work rather than seats: Free is $0 with 25 actions a month, Team is $199 a month for 300 actions, and Enterprise is custom. Check each pricing page for current details.

Can I use Thor and Unblocked together?

Yes. Both offer MCP servers, so a coding agent like Claude Code or Cursor can connect to both. Use Unblocked for questions about the code, and Thor for what the team decided and whether the ticket is still accurate.

See what your coding agent gets back when it asks Thor what the team decided. Book a demo.