Issue Trackers
Linear issue #243
Linear issue #253 (blocked)
Linear issue #248 (done)
Issue #210 (blocked)
Issue #219 (gateway scope)
PR #456 (merged)
+ more
Your agents outpace your board. Your AI project manager keeps up.
Thor keeps your backlog, issues and roadmap current as plans change. You ship more, and nothing slips through the cracks.
Shipping got fast. Coordination didn't.
Most software teams don't have a project manager. Someone does the job on the side: filing issues after meetings, cleaning up the backlog, checking work against the roadmap.
Thor takes that job off their plate, and checks with you before it changes anything.
Meetings to issues
Before
Someone turns a 45-minute planning call into GitHub issues by hand, if they get to it.
With Thor
Thor drafts the issues with owners and a link to where they were agreed. You approve, Thor files them.
Sprint planning transcript
MON 9:14
Notes:
6 action items, 3 owners named out loud.
None of them are in GitHub yet.
Thor · Draft issues
#482
6 issues ready to file
3 owners
Linked to the call
Issues stay current
Before
The plan changes in a Slack thread. The GitHub issue still says the old thing.
With Thor
Thor drafts the update to the issue, so the board matches what the team decided.
From #eng-platform
YESTERDAY
Priya:
let's push the export work to next sprint.
Issue #318 still says this sprint.
Thor · Issue update
#318
Move #318 to next sprint
Out of date
Source: #eng-platform
Backlog cleanup
Before
The backlog has 214 open tickets. Some shipped months ago, some are duplicates, and nobody wants to go through them.
With Thor
Thor finds the tickets that already shipped, repeat each other or went stale, and drafts the cleanup. You approve, Thor closes them.
Backlog
214 OPEN
Oldest:
opened in March, no activity since.
Nobody has groomed it in weeks.
Thor · Backlog cleanup
214
18 tickets to close or merge
6 already shipped
4 duplicates
8 stale
Roadmap alignment
Before
The roadmap says this quarter is about onboarding. Half the sprint is work nobody can tie back to it.
With Thor
Thor checks open issues against the roadmap and flags what doesn't fit. You decide what stays.
Q4 roadmap
OCT 1
Goal:
ship self-serve onboarding by December.
7 open issues don't map to any goal.
Thor · Roadmap check
Q4
7 issues off the roadmap
No linked goal
Source: Q4 roadmap
Follow-ups
Before
A pull request waits on review for three days, and nobody notices until standup.
With Thor
Thor nudges the right person once, so work keeps moving and nobody has to chase.
Pull request #491
3 DAYS
Review:
requested from Jon on Thursday.
No activity since.
Thor · Follow-up
#491
Asked Jon about the review
1 message
Sent to Jon only
Status without the meeting
Before
You piece together where the sprint stands from GitHub, Slack and three people's memory.
With Thor
Ask Thor, or read the recap. It already knows what moved and what's stuck.
From #eng-leads
FRI 4:02
Dana:
where are we on the release?
Asked in four places this week.
Thor · Weekly recap
AUTO
9 of 14 issues closed
2 blocked
1 with no owner
How your AI project manager knows what changed
Every update Thor drafts comes from its context graph. That's a live map of who's working on what and what was decided, across GitHub, Linear, Slack and your meetings.
Docs & Specs
+ more
Video Meetings
Sprint Planning
Sprint Demo & Review
Daily Standup
Architecture Sync
Engineering All-Hands
Design Critique & Review
Product Sync
Security Review Call
+ more
Chat Platforms
#eng-platform thread
#standup (yesterday)
Project handoff thread
#product (drift warning)
Engineering Channel chat
General Standup thread
Release handoff post
Product Team (scope shift)
+ more
What did the team ship this week?
Team Updates & Recaps
Drift Notification
Drift Notification
Generated Specs & Tasks
PR description & test plan
DraftAgents & Apps
Thor proposes. You approve.
Thor keeps track of what your team decided. When something changes, it drafts the update, and nothing lands until you say yes.
What's decided
Every decision, owner and deadline, pulled from your meetings, threads and issues.
Launch Readiness
Decision
Ship on Aug 10
Commitment
Finalize GA scope
Owner
Jason Kim
Status
On track
Slack
Github
Docs
What changed
When a thread or meeting changes the plan, Thor drafts the update for you to approve.
Change spotted
Update drafted
You approve
Issue updated
Who needs to know
Your team and your coding agents get the same up-to-date answer, wherever they work.
The same answer, everywhere
Human
Agent
New Tool
Clear about what it isn't
Not a chatbot you have to prompt
It doesn't wait for you to ask.Thor spots what changed and drafts the update without being asked.
Only shows up when something needs you.And when you do want to ask, it already knows the answer.
Not another board
Works in the GitHub or Linear board you already use.No new tracker to move to, and nothing to migrate.
Doesn't change anything on its own.Thor drafts the update. You approve it before it lands.
Not a meeting summarizer
A summary isn't the point.Notes are a byproduct, not the goal.
Knows what was actually decided.Understands well enough to act on it, not just recap it.
Not a coding agent
Doesn't write code.Doesn't replace the coding agents your engineers use. Feeds the ones you already use.
Gives it the context it's missing.Claude Code, Cursor, whatever your team runs.
Ask Thor anything.
It already knows where things stand.
Thor keeps track of what your team is working on, so you can ask it what you'd ask a teammate and get a straight answer.
Y
You
Just now
What has George been working on?
T
Thor
Thinking...
T
Thor
Just now
Here's what George has been working on this week:
- Completed PR #456 for authentication refactor (merged Tuesday)
- Currently reviewing database migration plan in #eng-backend
- Opened Linear issue #789 for Redis caching implementation
- Had 3 meetings: Sprint planning, Architecture review, 1:1 with Tyler
T
Thor
Just now
Yes, 3 engineers are currently blocked:
- Sarah is waiting on a review for PR #234 (API rate limiting refactor), open for 2 days with Marcus and Dev tagged as reviewers
- James has PR #301 (payment webhook integration) pending review since yesterday, flagged as high priority but with no reviewers assigned yet
- Priya is blocked on the new onboarding flow implementation until the product spec in Notion is approved, waiting on sign-off from the PM team
T
Thor
Just now
Here's the current status of the database migration:
- Overall progress: 8 of 12 issues complete
- Sarah Chen completed the schema conversion for the users table yesterday and has moved on to the orders table
- James Okafor is currently running validation scripts on the migrated data from Phase 6, with results expected by EOD
- Next milestone: Full staging environment cutover scheduled for Thursday
- Risks: 2 tables have unresolved warnings that need review before production cutover
T
Thor
Just now
Here's a quick brief to help you prep for your 1:1 with George:
What George has been working on George completed PR #456 for the authentication refactor (merged Tuesday) and opened Linear issue #789 for the Redis caching implementation. He's currently reviewing the database migration plan in #eng-backend.
Potential talking points
- PR #612 (error handling improvements) has been open for 4 days without a reviewer assigned, worth checking in on
- George left a comment on the architecture review doc flagging concerns about the proposed caching strategy, may be worth discussing
- His last 3 PRs have averaged 3 days to review, which is above the team average
Wins to acknowledge
- The authentication refactor he led shipped cleanly with no post-merge issues
- He proactively flagged a potential bottleneck in the migration pipeline last week
Open questions you might want to ask
- Is he still on track for the Redis caching ticket given the current migration workload?
- Does he need any support getting reviewers on his open PRs?
T
Thor
Just now
Your last meeting on the database migration was Tuesday, February 11th at 2:00 PM.
- Attendees: Sarah, James, Priya Nair, Tyler (PM), and you
- Duration: 47 minutes
- Key decisions made: Agreed to prioritize the orders and users tables before moving to the analytics tables, and confirmed Thursday as the target date for the staging environment cutover
- Action items from that meeting: James to run data validation scripts by EOD Friday, Sarah to document schema conversion process for handoff, Tyler to get sign-off on the analytics table spec from the PM team
- Note: 2 action items from that meeting are still open, James's validation results are in and Sarah's documentation is still pending
T
Thor
Just now
Here's what I found and added to Linear Issue #123 (Redis Caching Implementation):
Description updated with the following context:
- From the Architecture Review meeting (Feb 13th): George flagged concerns about cache invalidation strategy for user session data, specifically around edge cases where multiple services write to the same key. The team agreed this needs to be resolved before implementation begins.
- From #eng-backend (Feb 14th): Marcus shared a link to an internal doc outlining the proposed TTL values for each cache layer. James replied suggesting a shorter TTL for the orders service given its write frequency.
- From the Sprint Planning meeting (Feb 10th): This ticket was flagged as a dependency for the payment webhook integration (PR #301), meaning a delay here could push back James's work as well.
Get going in a few minutes
STEP 01
Connect your tools
Link Thor to GitHub, Linear, Slack, Google Meet, and Drive. Takes 2 minutes.
STEP 02
Bring Thor into the conversation
Add Thor to the Slack or Teams channels and meetings where your team plans work.
STEP 03
Thor starts working
Thor builds its context graph of your team and starts keeping your issues current. You'll hear from it when something needs you.
See what Thor keeps moving for you.
One AI project manager. A different job off every team's plate.
For Leaders
Thor tracks commitments, surfaces what needs you, and keeps the whole picture current.
Explore Thor for leaders
For Engineers
Your issues stay current without the grooming, and your coding agents get the decisions and history they'd otherwise miss.
Explore Thor for engineers
For Product
Thor turns planning calls into issues and remembers what was tried, ruled out and decided, before the team commits.
Explore Thor for product
For AI Partners
Thor keeps every AI rollout's decisions and status straight, and leaves each client with a context graph of their own, not just a training deck.
Explore Thor for AI partnersFAQs
What is Thor?
Thor is your AI project manager for software teams. It does the work project managers do: organizes the backlog, keeps tickets and boards up to date, coordinates across your tools, and keeps the roadmap aligned. It's powered by Thor's context engine: one living record of what your team decided, kept current from Slack, meetings, GitHub, Linear, and your docs, so the next person or coding agent never starts from a guess. Thor drafts the updates that keep that record honest, and a person approves them before anything official changes.
What is an AI project manager?
An AI project manager does the upkeep a project manager would. It turns meetings into issues, keeps tickets current when plans change, follows up on work that stalls, and checks work against the roadmap. Unlike a chatbot, it doesn't wait to be asked. Thor is an AI project manager for software teams. It works in GitHub, Linear, Slack, Teams and your meetings, and a person approves every change before it lands. Our guide covers what an AI project manager does for software teams, step by step.
Who is Thor built for?
Thor is purpose-built for software engineering and technical teams that are moving too fast and feeling overwhelmed with administrative overhead. It's ideal for team leads, engineering managers, and founders who feel the pain of coordination tax most acutely.
Does Thor change things on its own, or do I approve first?
Thor proposes and a person approves. Thor drafts the change, a new issue, a new owner, a status update, a doc edit, shows you where it came from, and waits for someone to accept it before anything in your tools changes. Nothing becomes official just because an AI sounded sure.
How is Thor different from ChatGPT or a general AI assistant?
Thor doesn't wait to be asked. A general assistant answers from whatever you paste into the chat, so two people asking the same question can get two different answers, and nothing gets written down as decided. Thor reads the work itself, keeps one shared record of what's decided and what's gone stale, and comes to you when a commitment is aging or a ticket no longer matches what the team agreed. Every answer shows where it came from. General AI assistants are designed to answer general questions, from medical diagnosis to child care to weather reports. Thor is focused on a narrow mission: keeping your team's work honest and up to date.
Do I have to invite another bot to all my meetings?
Nope. You have enough bots to deal with. Thor isn't an awkward guest you have to remember to add to every call. It works by hooking into the meeting transcripts your team already generates in Google Meet, Zoom, and Microsoft Teams.
Do I need to be a workspace admin to set up Thor?
Not at all. You can initiate the setup in minutes using standard, secure third-party authorization like GitHub OAuth. If an integration requires broader admin approval, Thor will provide a simple, shareable link for your workspace admin to grant the necessary permissions.
What is the pricing for Thor?
Every plan gets unlimited people, meetings, and connected tools. You only pay for actions, which are the finished things Thor produces: a ticket created, a doc updated, a question answered. Free is $0 with 25 actions a month, Team is $199 with 300, and Enterprise is custom. See thor.ai/pricing for the full breakdown of what counts.
How does Thor turn meetings into tasks?
After your meeting ends, Thor reads the transcript and figures out what actually needs to happen next. Then Thor drafts a plan: either the action items can be converted to issues, or a document update can be triggered to capture any decisions that were made, or Thor can follow up with Sarah about that API thing you discussed on the call but already forgot about. You look over Thor's suggested next steps, give it the thumbs up, and Thor actions it. Nothing lands in your tracker until someone says yes. Transcription needs to be switched on in Google Meet or Zoom, since Thor never joins the call.
How accurate is Thor with technical conversations?
Thor is specifically tuned for software development and product team conversations. However, our key feature is the "human-in-the-loop" design. Thor always proposes a plan for your approval before taking any action, giving you the chance to add any necessary nuance or corrections.
Will this create more notification spam for my team?
No, the opposite. By centralizing follow-ups and creating structured action plans, Thor reduces the random "just checking in" pings on Slack. You can configure how and when Thor communicates to fit your team's existing workflow and minimize unnecessary noise.
How does Thor protect my data?
Thor is SOC 2 Type II compliant, and we've completed a Cloud Application Security Assessment (CASA), the App Defense Alliance standard for apps that access sensitive Google user data. Thor is a new product from the team behind Zenhub, who have a decade-long track record of building enterprise-grade developer tools with security at their core. We apply the same standards to everything we build.
Do you train your AI models on my company's data?
Absolutely not. Your data is yours alone. We never use customer data, conversations, or meeting transcripts to train our models.
Does Thor have access to read or write our source code?
No. Thor's integration with tools like GitHub is strictly limited to project management functions like creating, updating, and commenting on issues. It has read access to your codebase in order to understand the context of the work and access the relevant documentation (typically stored in markdown files). Thor cannot push directly to your codebase.
Is there an audit trail for actions taken by Thor?
Yes. The conversation record stores who asked, which tool ran, and what came back. We can provide that record on request. It is not a screen in the product yet. On GitHub and Linear, a write uses the authorization of the person who asked, when they have connected that tool, so the tool's own history shows them. A system you connect yourself is written as the organization credential, so that system's history shows the credential, not the Slack user.