# Changelog Source: https://docs.thor.ai/changelog Product updates and announcements **August 2026** ### New Microsoft Teams Support Thor now lives in **Microsoft Teams**, the same way it already lives in Slack. Add Thor from the [Teams Store](https://teams.microsoft.com/l/app/30a7590a-b1e9-4ef7-9dc0-f40f7daf3558?source=thor-docs) or from [thor.ai/get-started](https://www.thor.ai/get-started). An admin connects your Microsoft organization, then Thor walks each person through linking their Microsoft account and their meeting and work tools. You can chat with Thor in a personal chat, a channel, or a group chat. Standups, post-meeting recaps, reminders, and issue creation land in Teams the same way they do in Slack. Thor can also find and summarize past Teams conversations. The Thor app has **Connections** and **Notifications** tabs so you can manage integrations and quiet hours without leaving Teams. You 9:02 AM Hey @Thor @Thor, send me my stand-up notes for today. You 9:02 AM Hey @Thor @Thor, send me my stand-up notes for today. Thor App Today at 9:00 AM πŸ—“οΈ Standup Summary for Alex Rivera - Tue, August 25 Completed βœ…Atlas β€’ Ship the Teams onboarding path β—¦ πŸ™ #5166 Add to Teams button on /get-started Upcoming πŸ•’Atlas β€’ Review yesterday's pricing sync action items β—¦ πŸ“… Aug 24 - Pricing sync Thor Bot Today at 9:00 AM πŸ—“οΈ Standup Summary for Alex Rivera - Tue, August 25 Completed βœ…Atlas β€’ Ship the Teams onboarding path β—¦ πŸ™ #5166 Add to Teams button on /get-started Upcoming πŸ•’Atlas β€’ Review yesterday's pricing sync action items β—¦ πŸ“… Aug 24 - Pricing sync you prompt β€Ί Use the Thor MCP to get my standup for today. thor response Completed: Ship the Teams onboarding path (#5166) Upcoming: Review yesterday's pricing sync action items ### New Agent Profiles You can now create **agent profiles** in the webapp: a named profile for a product, with its own instructions, linked products, and scheduled automations. Anyone in the organization can set one up. Automations can post a report to a Slack or Teams channel, or do the work without posting a final report. Say something like "switch to the Atlas profile" in chat and Thor will use that profile's instructions for the conversation. ### New Issue Context Packs When Thor has something worth adding, it now writes a folded briefing onto the GitHub or Linear issue body. A person sees one line, `Additional context (powered by Thor AI)`. A coding agent reading the issue sees the full **context pack**: parent work, related PRs, governing docs, meetings, and decisions. You can also pull the same pack from the Thor MCP. If you do not see the block on your tickets yet, email [support@thor.ai](mailto:support@thor.ai). [Learn more](/usecases/tasks). ### New GitHub Docs as Context Thor now indexes markdown from your connected GitHub repositories: README files, docs folders, and agent-instruction files like `AGENTS.md`, `CLAUDE.md`, and `.cursor/rules/`. Enable or remove individual files from the **Documents** page in the webapp, then ask Thor questions grounded in what the repo actually says. ### New Hours Thor Can Reach You You can now set the hours Thor is allowed to message you, per day, in your own timezone. A reminder or nudge that comes due outside those hours is **held, not dropped**. It arrives when your hours open, usually within about ten minutes. If you ask Thor to remind you at 11pm, Thor asks first. Say yes and it still goes out then. Replies are never held: if you message Thor at midnight, Thor answers at midnight. Set this from **Notifications** in the webapp, the Teams Notifications tab, or Slack's Manage Notifications modal. ### Improved MCP Standups, Evidence, and Feedback The Thor MCP server can now **fetch a standup** (yours or a teammate's), **post a standup as a thread reply**, pull **work item evidence**, search that evidence, and apply status or blocker feedback without leaving Cursor or Claude. Standup output can be JSON, markdown, Slack, or Teams. [Learn more](/usecases/standups). ### Improved Standup Completed vs Upcoming Daily standups now split work into **Completed**, **Upcoming**, and **Cancelled**, so yesterday's shipped work is not mixed in with what is still open. Large Slack standups are also packed by product so the message stays readable instead of getting truncated. ### Improved Faster GitHub & Linear Updates Issue and pull request changes from GitHub and Linear now reach Thor as they happen, instead of waiting for the next scheduled sync. Standups, reminders, and MCP answers stay closer to the current state of the ticket. ### Improved Slack Thinking Steps When you ask Thor something in Slack, the reply now shows **thinking steps** as Thor works: what it is looking up, and where it is in the answer. You can tell it is still going, instead of staring at a silent typing indicator. ### Minor Thread Work Item Quality Thread summaries now only become work items when a **human** actually said something in the thread. Bot-only chatter is ignored. **June 2026** ### New Notion & Google Docs Support ![documents](https://mintcdn.com/thor/YYCrix9H3kEt1_oM/images/documents.png?fit=max\&auto=format\&n=YYCrix9H3kEt1_oM\&q=85\&s=9613b03974d2eef4b5fea3dfdda1bd5a) Thor now supports **Notion** and **Google Docs** as document context in the data layer. Connect your accounts from **Your Connections** in the Thor Slack app, then ask Thor to check whether work aligns with a spec, draft issues from a requirements doc, or answer questions grounded in what your team already wrote. A new **Documents** section in the webapp lets admins see which pages and docs are registered, share document access with teammates, and spot connections that need attention after a reconnect. [Learn more](/usecases/docs). ### New Team Glossary ![team-glossary](https://mintcdn.com/thor/YYCrix9H3kEt1_oM/images/team-glossary.png?fit=max\&auto=format\&n=YYCrix9H3kEt1_oM\&q=85\&s=4b3418c9c99a3916d82dc4bdee96029c) Thor now builds an organization-specific **Team Glossary** from your issues, Slack messages, and meeting transcripts β€” product names, project codenames, abbreviations, and internal jargon. Matching terms are injected into Thor's prompts so standups, meeting summaries, and agent replies use the vocabulary your team actually uses. Browse and review extracted terms from the **Team Glossary** page in the webapp. ### New External Specialist Agents (Beta) Organizations can register **external specialist agents** (via the A2A protocol) and have Thor delegate focused sub-tasks to them β€” for example, a security review agent or a domain-specific coding assistant. Thor discovers available specialists, gathers relevant context, and orchestrates multi-round conversations, with an optional confirm-before-call step in Slack. Admins can delete registered agents from the webapp. Contact [support@thor.ai](mailto:support@thor.ai) to enable this for your organization. ### Improved Monday Kickoff The Monday kickoff message has been redesigned as a **strategic product dashboard**: priorities are grouped by product and project with richer narrative context, so the start-of-week briefing reads less like a flat task list and more like a focused planning brief. [Learn more](/usecases/reminders#weekly-messages). ### Improved Team Projects The **Team Projects** page now supports filtering, search, sorting, and pagination for large organizations. Thor also regenerates project groupings daily and requires at least two related work items before creating a new project, reducing one-off noise in your project taxonomy. ### Improved Work Item Status Sync Work items now reconcile their status automatically when linked GitHub issues or pull requests are closed or merged, keeping Thor's view of in-flight work aligned with your systems of record without manual updates. ### Improved Google Meet Transcript Reliability Google Meet transcripts are now ingested through the **Google Meet API** as the canonical source, with a fallback to Meet transcript entries when Drive export fails. A backfill path is available for calendar events that were missing transcript attachments. ### Improved MCP Work Item Tools The Thor MCP server now exposes tools to **list your work items** and **update their status** directly from Cursor, Claude, or any other MCP client β€” so you can triage and sync progress without switching back to Slack. Cursor's native OAuth redirect URI is also supported for MCP dynamic client registration. [Learn more](/usecases/tasks). ### Improved Issue Creation with Templates When Thor creates GitHub or Linear issues on your behalf, it now applies your repository's **issue templates** where available, producing better-structured tickets out of the box. ### Improved Standup & Post-Meeting Formatting Standup summary headers and section formatting have been refreshed for clarity. Post-meeting messages are easier to identify at a glance, action item owners are formatted more consistently, and non-user owners (teams or bots) are attributed correctly. ### Improved Work Item Quality Thor now filters out overly broad work items that span too many unrelated sources, relaxes similarity thresholds where appropriate, and reduces runaway expansion β€” so the work activity in your standups and summaries stays focused on real, actionable items. ### Improved Recurring Reminders Recurring reminders now fire correctly on **weekday-only** schedules and respect your local timezone when rendering trigger times. ### Minor Thread Nudge Timing Slack thread nudges no longer count weekend hours toward the quiet period, so threads are not nudged prematurely on Monday morning. ### Minor Weekly Reminder @-Mentions When Thor replies in a thread for a weekly recap or kickoff reminder, the message now @-mentions you so it is easier to spot in busy channels. ### Minor Connection Validation Thor now prevents duplicate Slack or Microsoft providers from being connected to the same organization and surfaces a clear validation error during OAuth if a connection already exists. ### Minor Meeting & Thread Privacy Accuracy Fewer meeting and Slack thread work items are incorrectly flagged as private, and Teams meeting transcripts are included reliably in meeting search results. **April 2026** ### New Thor MCP Server Thor's Model Context Protocol (MCP) server is now generally available, so you can connect Thor securely to Cursor, Claude, and any other MCP-compatible client. Using Thor as the data source for your AI workflows is faster, cheaper, more accurate and more reliable than needing to build your own multi-MCP data pipelines. [Learn more](/quickstart). ### New Automation Configuration in Slack ![slack-automations](https://mintcdn.com/thor/ZicLt5N2ZynC2LYK/images/slack-automations.png?fit=max\&auto=format\&n=ZicLt5N2ZynC2LYK\&q=85\&s=bf33a0b4d2889316752b203d07c2ba7a) You can now manage all of your Thor automations and reminders directly from the Thor Slack app's "Home" tab. Browse your active datetime triggers at a glance, create new ones (including fully custom automations), and edit or delete existing ones from an overflow menu β€” no need to leave Slack. Previews and timezone-aware scheduling make it easy to confirm exactly when each automation will fire. [Learn more](/usecases/reminders#manage-automations-from-slack). ### New New Webapp & Automated Project Categorization ![projects](https://mintcdn.com/thor/ZicLt5N2ZynC2LYK/images/projects.png?fit=max\&auto=format\&n=ZicLt5N2ZynC2LYK\&q=85\&s=3b44d339e6ee3ebf5198aec342d63fb0) The Thor webapp has been rebuilt from the ground up with new configuration options for personal settings, organization connections, team management, and integration health. Alongside the redesign, Thor now automatically categorizes your work into Products and Projects: a new "Team Projects" insights page surfaces the groups Thor has identified across your tools, and a new background classifier continuously detects new products and tracks scope drift over time. ### Improved Standup Summary Categorization & Context Standup summaries received a major refresh: items are now grouped by the products and projects they belong to, work items are rendered directly inside the standup message, and a new "Share" button lets you quickly forward a standup to a teammate or channel. "Show TLDR" buttons are now available on both individual and manager standups. [Learn more](/usecases/standups#whats-in-your-standup). ### Improved Post-Meeting Messages Post-meeting messages are now delivered as DMs only, keeping channels quieter and conversations more personal. Each message now includes the decisions made during the meeting (not just action items), and any action item that was previously discussed in another meeting is flagged with a "Previously Discussed In" reference. End-of-day reminders are batched into a single message instead of one per item. [Learn more](/usecases/meetings#get-a-summary-of-meeting-action-items-and-decisions). ### Improved Reminders with Quick Actions Thor App Friday at 1:00 AM On Monday in the standup, you planned to update the Thor change log, create new feature videos, and refresh the docs for this week's recent changes. Let me know if you want help turning that into tracked issues or prioritizing the work. πŸ™ #46243 feat: migrate changelog from Headway to Plain Help CenterπŸ™ #2838 Thor v1.2 (March Public Launch) Thor Bot Friday at 1:00 AM On Monday in the standup, you planned to update the Thor change log, create new feature videos, and refresh the docs for this week's recent changes. Let me know if you want help turning that into tracked issues or prioritizing the work. πŸ™ #46243 feat: migrate changelog from Headway to Plain Help CenterπŸ™ #2838 Thor v1.2 (March Public Launch) you prompt β€Ί Use the Thor MCP to show my open reminder about the changelog and docs work, with the linked issues. thor response Reminder β€” changelog, feature videos, docs refresh \#46243 feat: migrate changelog from Headway to Plain Help Center \#2838 Thor v1.2 (March Public Launch) Reminders that include work items now show inline quick action buttons, so you can update status or take the next step without typing a single word. Recurring reminder messages also have feedback and cancel buttons to make them easier to manage. [Learn more](/usecases/reminders#quick-actions-on-reminders). ### Improved Slack Thread Search Thor now has a dedicated Slack thread context tool: when you link or forward a Slack message, Thor will load the full thread (respecting private-channel access) and use keyword-first matching with semantic fallback to find the right conversation. Standup generation also recovers more gracefully when something goes wrong upstream. Try asking Thor, "I remember some time ago we were discussing \_\_\_. Help me find it." [Learn more](/usecases/meetings#find-a-past-slack-discussion). ### Improved Data Connection Preview When you connect a new data provider, Thor now shows your data immediately rather than making you wait for the next sync. The preview also suggests actionable next steps tailored to which tools you've connected so far. ### Improved Google Meet Gemini Notes Google Meet Gemini Notes ingestion has been overhauled β€” Thor now matches Gemini Notes to meetings via the conference space hangout link and filters attendees more accurately. Work item summaries generated from meetings are now more succinct and use richer work-activity context. ### Improved Calendar Status Per Installation When you connect multiple Google accounts to Thor, each calendar now reports its own connection status truthfully, so you can quickly tell which account needs attention if data goes missing. ### Improved GitHub App Approval Flow When a GitHub App installation is approved, both the requester and the approver now receive a notification once approval and the initial sync are complete. The approver's GitHub user is also automatically linked to their Thor account. ### Minor Integration Re-authorization in Settings Thor will now more clearly flag which providers need re-authorization, so admins can fix broken connections before they cause missing data. ### Minor Delete Organization Organization admins can now delete their entire Thor organization directly from the webapp, with a confirmation step and full cascading cleanup of related data. ### Minor Multi-Name User Lookups When asking Thor about multiple people at once (e.g. "what are Alice and Bob working on?"), Thor now resolves all of the named users in a single lookup for faster, more reliable answers. ### Minor PR Merge Activity Accuracy Fixed a class of issues where merged pull requests were attributed to the person who clicked "Merge" rather than the actual PR author, and where some development contributions were missing from standup activity entirely. ### Minor Issue Creation Robustness Eliminated duplicate issues that could occur when post-meeting "Create issue" buttons were clicked multiple times in quick succession. Thor will now also prompt you to choose a repository when no default is set, instead of silently failing. [Learn more](/usecases/tasks#convert-a-slack-thread-into-a-task). ### Technical Linear Authentication Hardening Thor now supports Linear refresh tokens, so long-running Linear connections stay authenticated automatically without requiring users to manually reconnect. **February 2026** ### New Slack Thread Nudges Thor will now nudge Slack threads which have been abandoned or forgotten and still require resolution or further assistance. This helps ensure that no conversation falls through the cracks. ### New Thor MCP Server (Beta) You can now connect Thor to your existing AI workflows via MCP. Ask any question that Thor is already good at answering, get a list of your work activity, and prepare for daily standups. Contact us to get early access. ### Improved Standup Quality & Detail Standups have received a number of quality improvements: * GitHub commits made outside the main branch and without a linked PR now contribute to work activity. * Improved detection of blockers, which are now surfaced more prominently in standup summaries. * Work activity summaries now more clearly highlight high-level goals and reduce technical jargon. * Every standup summary now includes additional detail and clear source attribution, with call-outs for recently shipped or completed work items. * If your Slack server has application-specific emojis, Thor will now make use of them. ### Improved Issue Search Accuracy We're continuing to make Thor's internal data memory management more context-aware and optimized for accuracy of issue search. Asking Thor to find that one specific issue you vaguely remember working on 6 months ago is now more reliable. ### Improved Meeting Attendance Detection Thor now more accurately detects meeting attendance even when a user has not RSVP'd to the calendar event. ### Improved Meeting Transcript Reliability Missing meeting transcripts are now detected and users are prompted to fix the problem with clear instructions. Additionally, highly delayed Google Meet transcript processing is now handled more reliably, ensuring transcripts are correctly linked to their meetings. ### Improved Issue Creation Speed Issues are now created 2x faster. Thor will continue to perform additional analysis, refinement, categorization, and grooming in the background. Thor will prompt you if any additional human input is needed. ### Improved Response Speed Thor's initial response time to prompts has been significantly improved. In some cases, the first reply previously took several minutes β€” this should no longer be the case. ### Minor Weekly Report Accuracy Weekly recap (Friday) and kickoff (Monday) reports now more accurately exclude work done over the weekend. ### Minor Post-Meeting Action Item Due Dates Post-meeting action items will now default to end-of-day when no specific due date is mentioned, ensuring no commitment is missed. Thor will now hunt you down if you say, "Guys, let's do it!" but don't actually say who owns the work, or when it's due. ### Technical Google Data Connection Reliability Fixed reliability issues with Google data connections and re-authentication flows. **January 2026** ### New Standup Reviews for Managers For managers who want to help their teams stay on track, Thor can now automatically send a list of each team member's standup summary to their manager. See [Standup Reviews for Managers](/usecases/standups#standup-reviews-for-managers) for more details. ### Improved Standup Formatting & Context Standup messages from Thor now include more context (GitHub commits, meeting reminders, past & upcoming meetings) and more detailed formatting of work items and sources. ### Improved Standup Corrections/Feedback You can now reply to Thor's standup summary with feedback and corrections, and Thor will incorporate this feedback into your tracked work activity. ### Improved Standup Time Configuration Users can now individually configure the time of day when they want to receive their standup summary by going to the "Home" tab in the Thor Slack app and clicking "Your Notifications". ### Improved Meeting Context in Tasks When Thor creates a task on your behalf, it will now automatically include the context of the meeting in the task description. This meeting context is weighted based on relevance and aims to enrich context for coding agents. ### Improved Automatic Reminder Controls In the past Thor would sometimes try to be "too eager" when acting on post-meeting action items, and attempt to automatically send messages and create tasks you never asked for. Moving forward, Thor will only do this if it was explicitly told to do so. ### Improved Prompt for Missing Task Context When you ask Thor to create a task on your behalf, Thor will now detect if it doesn't have enough useful context and prompt you for additional information. This helps ensure accuracy and completeness of the task description. ### Minor Support for Google Calendar Group Invites When checking for meeting attendees, Thor will now automatically expand group invites (eg. "[engineering@acme.com](mailto:engineering@acme.com)") into individual attendees to ensure that each team member's attendance is captured accurately. ### Minor User Controls for Linear & GitHub Connections Individual users can now open the "Your Connections" dialog and ensure Thor has correctly linked their personal Linear & GitHub accounts to the organization. This can be used to diagnose and fix data connection issues. ### Minor Detection of Unconnected Meeting Participants When Thor detects that you attended a meeting with someone in your organization who hasn't configured Thor yet, it will now notify you of this and offer to share the meeting notes with them. ### Minor Meeting Cancellation Support Thor now properly detects and handles cancelled meetings. They will be removed from context for standups and reminders. ### Technical Upgraded to Gemini 3.0 Thor uses several different AI models under-the-hood to perform different tasks. We've recently upgraded our base models to Gemini 3.0, which should result in improved performance and accuracy. **December 2025** ### New Friday Recap & Monday Kickoff Have Thor automatically send you a weekly recap at the end of Friday, and a Monday kickoff message at the start of the week. See [Weekly Messages](/usecases/reminders#weekly-messages) for more details. ### New Google Calendar Integration When you connect your Google account, Thor will now automatically can your past and upcoming calendar events and include that data in your standups and reminders. **NOTE:** *If you have connected to Google previously, you will need to re-authorize your connection to enable the additional calendar access.* ### New Zoom Integration You can now have Thor automatically create tasks and reminders from your Zoom meetings. See [Zoom Configuration](/usecases/meetings#zoom-configuration) for more details. ### New Coding Agent Integration Thor will now automatically assess your tasks for coding agent suitability and offer to auto-assign them to Cursor, Claude, Tembo or Charlie. See [Delegate to Coding Agents](/usecases/tasks#delegate-to-coding-agents) for more details. ### New Task Subscriptions Thor can now subscribe to task events and notify you of important updates for tasks you care most about. See [Task Subscriptions](/usecases/tasks#task-subscriptions) for more details. ### Improved Automatic Task Categorization When you ask Thor to create a task on your behalf, it will now automatically tag the issue with the right labels, and set the most appropriate issue type based on the task description. ### Improved GitHub Integration Thor can now handle updating your GitHub issues with additional metadata, such as issue types, blocking/blocked by relationships, sub-issue management, and parent issue assignment. Thor can also help you close and re-open issues. ### Minor Connection Management Data connection which impact your entire organization are now separated into a new "Organization Connections" dialog, separate from your personal connections (now in "Your Connections"). This can be managed from the "Home" tab in the Thor Slack app. ### Minor Thor Message Removal Sometimes Thor might post a message in a Slack channel that you don't think is relevant, or adds noise. You can now ask Thor to remove that message by either replying in the thread with "remove this message" or by giving Thor a link to the message with the instruction "remove this message". ### Technical Weighted Work Activity Classification When Thor captures work activity from your Slack, GitHub, Linear and meeting data, it will now automatically give each work activity a contribution weight. Items which you own will be will be treated with more urgency and importance than items you simply review or comment on. # GitHub permissions Source: https://docs.thor.ai/github-permissions Why Thor asks to write to your repositories, what it can change, and how to approve it. Thor connects to GitHub through a GitHub App called **Thor Assistant**. It reads your issues, pull requests, and code so it can answer questions and keep work in sync. Thor now also asks for **Contents: Read and write**. With it, a **doc update** automation can open pull requests that keep your markdown docs current, without anyone pasting a personal access token into Thor. Until an owner approves, nothing changes. Thor keeps working exactly as it does today. # What Thor can change Write access is only used by doc update automations, and only inside the limits you set: * **Only your doc roots.** Thor edits markdown files in the repositories and paths you set as **Doc roots** on the automation. Nothing else. * **Only its own branches.** Every change goes on a `thor/doc-update/` branch and arrives as a pull request. Thor never pushes to your default branch. * **Never merges.** Thor asks the document's owner to review, and a person on your team decides whether it goes in. * **Short-lived access.** For each run, Thor gets a token from GitHub that expires within the hour and only covers the doc-root repositories. * **Verified commits.** GitHub signs Thor's commits as Thor Assistant, so they show as **Verified**. Everything else Thor does with your code, like answering questions and working in a sandbox, stays read-only. # Approve the update An owner of the GitHub organization needs to accept the new permission. GitHub emails owners when Thor asks for it. **1. Open your GitHub App installations** For an organization, go to `https://github.com/organizations//settings/installations`. For a personal account, go to `https://github.com/settings/installations`. In Thor, the doc update automation's settings link straight to this page. **2. Configure Thor Assistant** Click **Configure** next to **Thor Assistant**. GitHub shows a banner saying Thor Assistant is requesting updated permissions. **3. Accept the new permissions** Click **Review request**, check the list, and click **Accept new permissions**. One approval covers everything Thor is waiting on, so if GitHub lists more than Contents, that's expected. Once you accept, the **GitHub pull requests** section of your doc update automation says Thor opens pull requests with its GitHub App. You don't need to save anything. > [!NOTE] > > Not using doc update? You can leave the request. Thor keeps working with the access you already gave it. # If you already use a personal access token Your doc update automation keeps using its saved token until an owner approves. After that, Thor opens pull requests as Thor Assistant and deletes the saved token after its first successful run. You can then revoke the token in GitHub. # Doc roots in one GitHub organization A doc update automation's doc roots must all come from one GitHub organization or account. Thor's access is granted per organization, so one run can only write to one of them. For docs in two organizations, create one automation for each. # If a ruleset blocks Thor GitHub rulesets apply to Thor like they do to anyone. If a ruleset targets every branch, Thor can't create its `thor/doc-update/` branches, and the run reports that GitHub refused the change. The fix is to leave Thor's branches out of the ruleset: 1. Open the ruleset in your repository or organization settings. 2. Under **Target branches**, add an exclusion for `thor/doc-update/**`. 3. Save. Your default branch keeps its protection, and Thor's changes still reach it only through a reviewed pull request. > [!WARNING] > > Avoid adding Thor Assistant to the ruleset's bypass list instead. A bypass applies to every branch the ruleset covers, including your default branch. Rulesets that require signed commits don't need any change, since Thor's commits are already verified. # Remove Thor's access Uninstall Thor Assistant or narrow its repository access from the same installations page. If you remove a doc-root repository from Thor's access, the doc update automation can no longer save with that repository. Questions? Email [support@thor.ai](mailto:support@thor.ai). # Introduction Source: https://docs.thor.ai/index Meet Thor. Thor is your new AI teammate who happens to be really good at all the project management stuff that you hate doing. Thor lives in Slack or Microsoft Teams, joins your conversations, and handles the coordination overhead that comes with building software. ## Setting up Get Thor installed in Slack or Microsoft Teams and start using it to manage your projects. > [card] [Start here](/quickstart) > > Follow the quickstart guide. ## What can Thor do? Learn about the different ways you can use Thor to offload your project management tasks. > [card] [Meetings](/usecases/meetings) > > Convert meeting notes into actionable tasks and reminders for your team. > [card] [Tasks](/usecases/tasks) > > With a single command, Thor can summarize, assign, categorize and organize your tasks. > [card] [Documents](/usecases/docs) > > Use Notion and Google Docs as additional Thor context when checking alignment, drafting issues, and answering questions. > [card] [Reminders](/usecases/reminders) > > Create a recurring reminder with Thor's internal data context, reasoning and summarization engine. > [card] [Stand-ups](/usecases/standups) > > Have Thor automatically generate your daily stand-up notes every morning. > [!NOTE] > > Thor is powered by large language models (LLMs). While Thor strives to be accurate and helpful, AI-generated responses β€” including summaries, task descriptions, and other outputs β€” may occasionally be inaccurate or incomplete. We recommend reviewing Thor's outputs before acting on them. ## Get in touch > [card] [Support & Feedback](/support) > > We want to hear from you! By using Thor, you are agreeing to our awesome [Terms of Service](https://app.thor.ai/terms) and [Privacy Policy](https://app.thor.ai/privacy). # Quickstart Source: https://docs.thor.ai/quickstart Get Thor installed and connected Get Thor installed in your coding agent, Slack, or Teams. > [tab] MCP > > The agent steps use `https://app.thor.ai/mcp`. If your company has its own Thor address, use that host instead of `app`. You sign in with the Slack or Google account you already use for Thor. You only see data you already have access to. > > [YouTube video player](https://www.youtube.com/embed/b0y61mn8HXE) > > > [accordion] Claude Code > > > > Thor has an [official Claude Connector](https://claude.ai/directory/thor-ai) for Claude Desktop, Claude Code, and Claude on the web. In Claude Code's terminal, two lines add Thor. The first adds Thor, the second signs you in. > > > > ```bash theme={null} > > claude mcp add --transport http thor https://app.thor.ai/mcp > > claude mcp login thor > > ``` > > > [accordion] Cursor > > > > [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=thor\&config=eyJ1cmwiOiJodHRwczovL2FwcC50aG9yLmFpL21jcCJ9). One click adds Thor. > > > > Or install the [Thor plugin](https://cursor.com/marketplace?pluginId=36062695) for skills that make Thor easier to use in Cursor. > > > > Or add this to `~/.cursor/mcp.json`. > > > > ```json theme={null} > > { > > "mcpServers": { > > "thor": { > > "url": "https://app.thor.ai/mcp" > > } > > } > > } > > ``` > > > > Cursor asks you to sign in the first time it calls a Thor tool. Approve it with your work account. > > > [accordion] Codex > > > > Two lines in your terminal. The first adds Thor, the second signs you in. > > > > ```bash theme={null} > > codex mcp add thor --url https://app.thor.ai/mcp > > codex mcp login thor > > ``` > > > [accordion] Gemini > > > > Paste this line into your terminal. Gemini asks you to sign in the first time you use Thor. > > > > ```bash theme={null} > > gemini mcp add --transport http thor https://app.thor.ai/mcp > > ``` > > > [accordion] Other agents > > > > Paste this URL where your agent lets you add a tool or connector. It will ask you to sign in. > > > > `https://app.thor.ai/mcp` > [tab] Slack > > > [!NOTE] > > > > You need to be an admin of the Slack workspace to install the Thor Slack app. > > **1. Install the Slack app** > > Go to the [Installation Page](https://www.thor.ai/get-started) and click **Add to Slack**. Select your Slack workspace and complete the installation. > > **2. Set up organization connections** > > Open Thor in Slack, go to the **Home** tab, open **Organization Connections**, and connect the data sources you want Thor to use. > > **3. Add your meeting platform** > > If you use **Google Meet**, open **Your Connections** and connect your Google account. > > If you use **Zoom**, ask your Zoom admin to open **Organization Connections** and connect your Zoom account. > > If you use **Microsoft Teams** meetings, ask an admin to connect Microsoft from **Organization Connections**, then link your own Microsoft account from **Your Connections**. See [Meetings](/usecases/meetings). > > **4. Add your task management platform** > > If you use **GitHub Issues**, ask your GitHub admin to open **Organization Connections** and set up the GitHub app. Then open **Your Connections** and confirm your personal GitHub account is linked. > > If you use **Linear**, ask your Linear admin to open **Organization Connections** and set up Linear. Then confirm your personal Linear account is linked from **Your Connections**. > > **5. Add your documentation** > > If your team keeps specs and decisions in **Notion** or **Google Docs**, open **Your Connections** and connect those accounts. > > For **Notion**, connect your Notion account and select the pages you want Thor to use as team context. > > For **Google Docs**, connect your Google account. > > **6. Say hi** > > Open the **Messages** tab in the Thor Slack app and start chatting. > > See [Meetings](/usecases/meetings) for more on how Thor can help. > [tab] Teams > > > [!NOTE] > > > > You need permission to install apps in your Microsoft Teams organization. An admin then connects your Microsoft organization so Thor can see calendar and meeting data. > > **1. Install the Teams app** > > Go to the [Installation Page](https://www.thor.ai/get-started) and click **Add to Teams**, or install Thor from the [Teams Store](https://teams.microsoft.com/l/app/30a7590a-b1e9-4ef7-9dc0-f40f7daf3558?source=thor-docs). > > **2. Connect Microsoft** > > Open Thor in Teams. An admin should connect your Microsoft organization when Thor prompts, or from the **Connections** tab under **Integrations**. Then each person opens **Connections** and links their own Microsoft account under **Your Accounts**. > > **3. Add your meeting platform** > > Microsoft Teams meetings use the Microsoft connection from the previous step. Transcription also needs to be turned on. See [Meetings](/usecases/meetings). > > If you use **Google Meet**, open **Your Accounts** on the **Connections** tab and connect your Google account. > > If you use **Zoom**, ask your Zoom admin to connect Zoom from **Integrations** on the **Connections** tab. > > **4. Add your task management platform** > > If you use **GitHub Issues**, ask your GitHub admin to connect the GitHub app from **Integrations** on the **Connections** tab. Then open **Your Accounts** and confirm your personal GitHub account is linked. > > If you use **Linear**, ask your Linear admin to connect Linear from **Integrations**. Then confirm your personal Linear account is linked from **Your Accounts**. > > **5. Add your documentation** > > If your team keeps specs and decisions in **Notion** or **Google Docs**, open **Your Accounts** on the **Connections** tab and connect those accounts. > > For **Notion**, connect your Notion account and select the pages you want Thor to use as team context. > > For **Google Docs**, connect your Google account. > > **6. Say hi** > > Open your personal chat with Thor and start chatting. In a channel or group chat, @mention Thor so it knows you are talking to it. > > See [Meetings](/usecases/meetings) for more on how Thor can help. Once Thor is connected, ask it for a [stand-up](/usecases/standups) or your [tasks](/usecases/tasks). > [!NOTE] > > **Need help?** Please [reach out](mailto:support@thor.ai) and we'll be happy to help. # Support Source: https://docs.thor.ai/support Get help with Thor We want to hear from you! Tell us what you wish Thor could do better. A member of the Thor support team will typically respond within 24 hours. > [card] [Get Help](mailto:support@thor.ai) > > To report a bug, or get help with Thor, please email us at [support@thor.ai](mailto:support@thor.ai). > [card] [Send feedback](mailto:support@thor.ai) > > Click here to share feedback, or tell Thor directly: "I have feedback for the Thor team # Troubleshooting Source: https://docs.thor.ai/troubleshooting Common issues and solutions > [accordion] Thor is not responding to me in Slack > > A few things to check: > > 1. If you're trying to message Thor inside a channel, make sure you're mentioning Thor via `@Thor` in the message. This is not required when sending Thor a direct message. **Tip**: If you've already sent message but forgot to tag Thor, you can edit your message to include the `@Thor` mention and Thor should retry processing the request. > 2. Have you invited the `@Thor` bot into the channel? If not, sending the `/invite @Thor` command in the channel. > 3. Is Thor leaving an πŸ‘€ emoji on the message? If not, it's possible Thor is still working on processing the request. If you still get no response after a few minutes, please contact support. > [accordion] Thor keeps asking me which repository I want to use every time > > Just tell Thor: > > > [!NOTE] > > > > Hey `@Thor`, set `` as my default repository from now on. > > After that it should stop asking you. > [accordion] Thor's Google app is blocked due to Google Advanced Protection > > If you experience an authorization error from Google's Advanced Protection Program when connecting your Google account to Thor, you may be able to whitelist Thor as a trusted app via the Google Admin Console. > > If you are the admin of a Google Workspace account, you can whitelist Thor as a trusted app: > > 1. Go to your [Google Admin Console](https://admin.google.com/ac/owl/list?tab=configuredApps) > \[!NOTE] If you are unable to access this Console page, please ask your Google Admin to whitelist Thor > 2. At the top of the "Configured apps" list, click "Configure new app" > 3. In the "Search for app" field, enter "Thor" and click "Search" > 4. From the list of search results, click the "Thor" app with the "337058528615" Client ID > 5. Select the Google organization unit you want to whitelist Thor for, then click "Continue" > 6. Check the "Trusted" checkbox and click "Continue" > > After that, you should be able to retry connecting your Google account to Thor. > [accordion] Thor is not able to find the Google Meet transcripts for my meetings > > There could be several things at play here. > > First, check to make sure you have enabled automated meeting transcripts for all your meetings. As a Google Admin, you can do this via [these instructions](https://support.google.com/a/answer/12076932). > > > [!WARNING] > > > > If this is the first time you're enabling transcripts for your Google organization, we aware that any existing recurring meetings will NOT have transcripts enabled. The organization-wide setting only applies to future meetings. To ensure existing meetings have transcripts enabled, you will need to edit the calendar event, remove the existing Google Meet conference entry, save the calendar event, then edit the calendar event again, re-add the Google Meet conference entry, and finally save the calendar event again. > > Second, check to make sure your meetings have a transcript generated. Typically this will show up as an attached Google Doc in the meeting details. If it's missing, you will need to further debug the lack of transcripts on the Google Meet / Google Admin side. > > Finally, make sure you have authorized Thor with access to your Google organization. You can do this by opening the Thor "Home" tab in Slack, clicking on "Your Connections", and verifying that your Google account has been connected correctly. If you're not sure, you can click on "..." and choose "Re-Authorize". Or simply send Thor a message: "Hey `@Thor`, re-authorize my Google account". > [accordion] Thor isn't using my Notion pages or Google Docs > > A few things to check: > > 1. Make sure the document provider is connected. Notion and Google Docs are connected from "Your Connections" in the Thor Slack app (not "Organization Connections"). Open the Thor "Home" tab in Slack, click "Your Connections", and verify that Notion or Google is connected. > > 2. For Notion, only the pages you selected during the connect flow are indexed. To add more pages later, reconnect Notion from "Your Connections" and update your page selection. > > 3. It can take a little time after connecting for your documents to be indexed before Thor can use them. > > 4. If Thor stops referencing a document it previously knew about, the connection may need attention after a reconnect. Check the "Documents" section in the webapp to see which pages and docs are registered and which connections need attention, then reconnect the provider if needed. > > > [!NOTE] > > > > Learn more about how Thor uses your documents in the [Documents](/usecases/docs) guide. # Uninstall Source: https://docs.thor.ai/uninstall How to fully remove Thor ## Removing specific providers and data connections You can disconnect any data providers (eg. GitHub, Google, Notion, Zoom, Linear, etc...) from Thor from the "Home" tab of the Thor Slack app. Click the "Configure" button next to "Settings" and then click the "..." menu next to the provider you want to disconnect and select "Disconnect". Removing those data providers will degrade the functionality of Thor by removing its ability to automatically use the context from those providers or to push updates back to them. ## Full uninstallation To fully uninstall Thor, disconnect all the data providers making sure to disconnect the Slack provider last. Please make note the "Term and Termination" section of our [Terms of Service](https://app.thor.ai/terms) for impacts to your service. Also make note of "Data Retention Periods" and "Procedure for Handling Requests for Data Deletion (Right to Erasure)" sections of our [Privacy Policy](https://app.thor.ai/privacy) to information about what happens to your data after you uninstall Thor. For any additional questions or special requests, please contact support at [support@thor.ai](mailto:support@thor.ai). # Documents Source: https://docs.thor.ai/usecases/docs Use Notion and Google Docs as additional Thor context when answering questions, drafting issues, and checking alignment. # Pre-requisites To use documents as Thor context, connect the platforms your team writes specs and decisions in. Thor supports **Notion** and **Google Docs** (via Google Drive). Thor only has access to documents you explicitly share β€” not your entire Drive or Notion workspace. > [accordion] Notion > > In Slack, open the Thor app, go to the **Home** tab, and click **Your Connections**. In Teams, open the **Connections** tab and use **Your Accounts**. Connect your **Notion** account and select the pages you want Thor to index during the OAuth flow. > > Indexed pages are added to **team shared context** β€” everyone in your organization can ask Thor about them, even if they have not connected their own Notion account. > > To add more pages later, reconnect Notion from **Your Connections** and update your page selection. > [accordion] Google Docs > > In Slack, open the Thor app, go to the **Home** tab, and click **Your Connections**. In Teams, open the **Connections** tab and use **Your Accounts**. Connect your **Google** account. > > Thor only has access to Google Docs you have shared β€” not your full Google Drive. ## Manage documents in the webapp ![documents](https://mintcdn.com/thor/YYCrix9H3kEt1_oM/images/documents.png?fit=max\&auto=format\&n=YYCrix9H3kEt1_oM\&q=85\&s=9613b03974d2eef4b5fea3dfdda1bd5a) The **Documents** page shows every Notion page and Google Doc Thor can access β€” who shared it, when it last synced, and whether it's **shared with the team**. Search, filter by source or status, and spot connections that need attention after a reconnect. # Use cases ## Check whether work aligns with a spec Ask Thor to compare in-flight tasks against a product spec, PRD, or decision doc. Thor searches and reads the synced document, then cross-references your issues, threads, and meeting context from the [data layer](/why-thor/data-layer): You 1:12 PM Hey @Thor @Thor, are our latest auth migration tasks aligned with this spec? [https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9](https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9) and our Q2 roadmap? You 1:12 PM Hey @Thor @Thor, are our latest auth migration tasks aligned with this spec? [https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9](https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9) and our Q2 roadmap? Thor App 1:12 PM Mostly β€” ENG-1842 and ENG-1849 match the spec. The rollback checklist the team discussed in the last meeting is entirely missing though. Want me to draft that issue? Thor Bot 1:12 PM Mostly β€” ENG-1842 and ENG-1849 match the spec. The rollback checklist the team discussed in the last meeting is entirely missing though. Want me to draft that issue? you prompt β€Ί Use the Thor MCP to check whether our latest auth migration tasks are aligned with this Notion spec: [https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9](https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9) thor response Mostly aligned β€” ENG-1842, ENG-1849 match. Gap: rollback checklist (spec Β§4) has no task yet. ## Draft an issue from a document Have Thor read a spec or design doc and turn it into a well-scoped GitHub or Linear issue: You 2:05 PM Hey @Thor @Thor, go through this doc [https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms](https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms) and generate Linear issues for any work we didn't track yet. You 2:05 PM Hey @Thor @Thor, go through this doc [https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms](https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms) and generate Linear issues for any work we didn't track yet. Thor App 2:05 PM Drafted **ENG-1902: Add versioned /v2 endpoints for customer export**. That was the big missing piece. Includes the auth, pagination, and rate-limit notes from the doc. Want me to assign it? Thor Bot 2:05 PM Drafted **ENG-1902: Add versioned /v2 endpoints for customer export**. That was the big missing piece. Includes the auth, pagination, and rate-limit notes from the doc. Want me to assign it? you prompt β€Ί Use the Thor MCP to draft a Linear issue for the API changes in [https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms](https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms) thor response Created ENG-1902: Add versioned /v2 endpoints for customer export ## Summarize or answer questions about a document Ask Thor to read a specific page or search across your team's shared documents: You 3:30 PM Hey @Thor @Thor, what does our deployment runbook say about rollback? You 3:30 PM Hey @Thor @Thor, what does our deployment runbook say about rollback? Thor App 3:30 PM Rollback is done in two steps: revert the release tag, then run `make deploy-previous` from ops. If DB migrations ran, follow the "forward-fix" section instead of a hard rollback. Want the exact runbook section? Thor Bot 3:30 PM Rollback is done in two steps: revert the release tag, then run `make deploy-previous` from ops. If DB migrations ran, follow the "forward-fix" section instead of a hard rollback. Want the exact runbook section? you prompt β€Ί Use the Thor MCP to check what our deployment runbook says about rollback. thor response Revert release tag β†’ make deploy-previous. If migrations ran: use forward-fix, not hard rollback ## List documents Thor can use See which Notion pages and Google Docs are registered for your team: You 4:01 PM Hey @Thor @Thor, do we have any documents for the auth migration? You 4:01 PM Hey @Thor @Thor, do we have any documents for the auth migration? Thor App 4:01 PM Yes! Many. Auth Migration Spec, Q2 Roadmap Decisions, Onboarding Spec, Deployment Runbook, Pricing v2, and API Export Design. Want me to give me a synopsis of each? Thor Bot 4:01 PM Yes! Many. Auth Migration Spec, Q2 Roadmap Decisions, Onboarding Spec, Deployment Runbook, Pricing v2, and API Export Design. Want me to give me a synopsis of each? you prompt β€Ί Use the Thor MCP to list which documents you have access to. thor response Yes! Many. [https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9,https://www.notion.so/acme/Q2-Roadmap-Decisions-c4e91a7f2b384d0e9f1a6c8d5e2b0a47,https://www.notion.so/acme/Onboarding-Spec-1234567890abcdef1234567890abcdef,https://docs.google.com/document/d/3k9QmN2pLx7vRcYwE4tHsUaBdFgHjKlMnOpQrStUvWx,https://www.notion.so/acme/Pricing-v2-1234567890abcdef1234567890abcdef,https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms](https://www.notion.so/acme/Auth-Migration-Spec-8f3a2c1b9e0d4a67b2c5d8e1f0a3b6c9,https://www.notion.so/acme/Q2-Roadmap-Decisions-c4e91a7f2b384d0e9f1a6c8d5e2b0a47,https://www.notion.so/acme/Onboarding-Spec-1234567890abcdef1234567890abcdef,https://docs.google.com/document/d/3k9QmN2pLx7vRcYwE4tHsUaBdFgHjKlMnOpQrStUvWx,https://www.notion.so/acme/Pricing-v2-1234567890abcdef1234567890abcdef,https://docs.google.com/document/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms) ## Keep docs in GitHub up to date Specs and decision docs that live as markdown in a GitHub repository can fall behind what the team decides in meetings and Slack. A **doc update** automation keeps them current. Add it to an agent profile from **Agent profiles** in the webapp, then pick the repositories and paths Thor should keep up to date as **Doc roots**. Thor checks your recent meeting and thread summaries for decisions that change one of those docs. It opens a pull request with just the edited lines, quotes the source, and asks the doc's owner to review. Nothing is merged without a person on your team. Until Thor can open pull requests, it lists the proposed changes in its report instead. To open pull requests, Thor needs an owner of your GitHub organization to approve its write permission, or a personal access token saved on the automation. See [GitHub permissions](/github-permissions) for what Thor can change and how to approve it. # Meetings Source: https://docs.thor.ai/usecases/meetings Convert meeting notes into actionable tasks and reminders for your team. # Pre-requisites To have Thor automatically take actions after your meetings end, you will need to connect at least one meeting transcription platform. Thor supports **Google Meet**, **Zoom**, and **Microsoft Teams**. > [accordion] Google Meet Configuration > > In order for Google Meet meetings to be captured by Thor, your Google Meet meetings need to have transcriptions enabled. For detailed Google Admin instructions on how to do this, see [Turn meeting transcription on or off](https://support.google.com/a/answer/12076932?hl=en). For detailed instructions on how to enable transcriptions for a specific meeting, see [Use Transcripts with Google Meet](https://support.google.com/meet/answer/12849897?hl=en). > > > [!NOTE] > > > > NOTE: Enabling Gemini notes and summaries is not required for Thor. > [accordion] Zoom Configuration > > In order for Zoom meetings to be captured by Thor, your Zoom meetings need to have transcriptions enabled and cloud recording must be active. Additionally, all meeting participants must be signed-in members of your organization for Thor to process the meeting. For detailed instructions on how to enable audio transcripts for cloud recordings, see [How to enable audio transcripts for cloud recordings](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0065911). > [accordion] Microsoft Teams Configuration > > Thor reads Teams meeting transcripts through your Microsoft connection. An admin connects your Microsoft organization from **Organization Connections** (Slack) or **Integrations** on the **Connections** tab (Teams). Each person then links their own Microsoft account from **Your Connections** / **Your Accounts**. > > Teams meetings also need transcription turned on. Your Microsoft admin can allow transcription in the Teams admin center, and individual meetings need a transcript generated. See [Enable transcription in Teams meetings](https://learn.microsoft.com/en-us/microsoftteams/meeting-transcription) and [View live transcription](https://support.microsoft.com/en-us/office/view-live-transcription-in-microsoft-teams-meetings-dc94e43e-ef14-4ad9-8c65-a3dfbdb7b1d9). # Use cases ## Get a summary of meeting action items and decisions [YouTube video player](https://www.youtube.com/embed/2fHoSmIVZRU) A few minutes after a meeting ends, Thor will automatically DM each participant with a list of action items and decisions from that meeting. If an action item was already discussed in an earlier meeting, Thor will flag it with a "Previously Discussed In" reference back to that conversation. From there you can ask Thor to: 1. Create a task from an action item 2. Add a comment to an existing task (if one already exists) 3. Remind you about an action item later that day 4. Follow-up with you if you haven't completed the action item the next day If you have multiple outstanding action items at the end of the day, Thor will batch them into a single end-of-day reminder rather than sending one message per item. The message will look something like this: Thor App Today at 9:49 AM Here's a quick recap of action items from today's Core Weekly Kick-off meeting. Would you like me to create issues for them? I've also noted 1 decision below. **1.** Evaluate effort to support import from GitHub Projects for customers with single repo migrations. β‹― A customer trialing the platform wants to migrate a single GitHub Project into Zenhub; currently, there is no direct importer for this. Graeme will experiment to see if a solution can be developed or recommend alternatives. πŸ’¬ Previously discussed in meeting: May 4 Β· 15 Min Meeting between Graeme Stapleton and Meg Reed Thor Bot Today at 9:49 AM Here's a quick recap of action items from today's Core Weekly Kick-off meeting. Would you like me to create issues for them? I've also noted 1 decision below. **1.** Evaluate effort to support import from GitHub Projects for customers with single repo migrations. β‹― A customer trialing the platform wants to migrate a single GitHub Project into Zenhub; currently, there is no direct importer for this. Graeme will experiment to see if a solution can be developed or recommend alternatives. πŸ’¬ Previously discussed in meeting: May 4 Β· 15 Min Meeting between Graeme Stapleton and Meg Reed you prompt β€Ί Use the Thor MCP to summarize action items from today's Core Weekly Kick-off. thor response 1. Evaluate effort to support import from GitHub Projects for single-repo migrations (Previously discussed: May 4 Β· Graeme Stapleton / Meg Reed) ## Plan your day or week Because Thor has access to your calendar, recent work activity and context on your most important goals, you can ask Thor to help you plan for your day, week or a specific meeting: You 8:15 AM Hey @Thor @Thor, give me a plan for today. You 8:15 AM Hey @Thor @Thor, give me a plan for today. Thor App 8:15 AM Here's a focused plan for today: **9:30** prep for the pricing sync, before lunch unblock ENG-1842 (Sam is waiting on your review), and **3:00** customer call with Acme. Want agendas for the rest of the week too? Thor Bot 8:15 AM Here's a focused plan for today: **9:30** prep for the pricing sync, before lunch unblock ENG-1842 (Sam is waiting on your review), and **3:00** customer call with Acme. Want agendas for the rest of the week too? you prompt β€Ί Use the Thor MCP to give me a plan for today. thor response 9:30 β€” prep pricing sync Before lunch β€” unblock ENG-1842 (Sam waiting on review) 3:00 β€” Acme customer call (export + SSO) Other prompts that work well: > [!NOTE] > > Hey `@Thor`, what important meetings do I have coming up this week? Generate a short agenda for each. > [!NOTE] > > Hey `@Thor`, for my call with Tom later today, what should I be ready for? ## Find a decision made in a meeting Have Thor do a deep scan of your recent meetings to find an important discussion point: You 11:48 AM Hey @Thor @Thor, I remember a while back in some meeting we discussed migrating the code to Rust β€” can you find that discussion and remind me what we decided? You 11:48 AM Hey @Thor @Thor, I remember a while back in some meeting we discussed migrating the code to Rust β€” can you find that discussion and remind me what we decided? Thor App 11:48 AM Found it β€” **Platform sync, Mar 12**. Decision: stay on the current stack for now; revisit Rust only if the parser hotspot still shows up after the Q2 perf work. Want me to turn the follow-ups into tasks? Thor Bot 11:48 AM Found it β€” **Platform sync, Mar 12**. Decision: stay on the current stack for now; revisit Rust only if the parser hotspot still shows up after the Q2 perf work. Want me to turn the follow-ups into tasks? you prompt β€Ί Use the Thor MCP to find the meeting where we discussed migrating the code to Rust, and summarize what we decided. thor response Platform sync, Mar 12 β€” stay on current stack; revisit Rust only if the parser hotspot remains after Q2 perf work. ## Find a past discussion Thor can also search across your Slack and Teams conversations to recover past discussions. When you link or forward a message, Thor loads the full thread (respecting private-channel access) and uses keyword-first matching with semantic fallback to find the right conversation: You 3:02 PM Hey @Thor @Thor, I remember some time ago we were discussing the new pricing tiers in some channel. Help me find it. You 3:02 PM Hey @Thor @Thor, I remember some time ago we were discussing the new pricing tiers in some channel. Help me find it. Thor App 3:02 PM Closest match is the thread in **#product** from Apr 3 β€” "Pricing tiers v2". Summary: three tiers, annual discount at 20%, grandfather existing Pro customers. Want the link? Thor Bot 3:02 PM Closest match is the thread in **#product** from Apr 3 β€” "Pricing tiers v2". Summary: three tiers, annual discount at 20%, grandfather existing Pro customers. Want the link? you prompt β€Ί Use the Thor MCP to find where we discussed the new pricing tiers. thor response \#product Β· Apr 3 β€” "Pricing tiers v2" Three tiers, 20% annual discount, grandfather existing Pro customers. # Reminders Source: https://docs.thor.ai/usecases/reminders Create a recurring reminder with Thor's internal data context, reasoning and summarization engine. # Use cases ## Create a complex reminder [YouTube video player](https://www.youtube.com/embed/NZcF6CoTcNQ) Thor has an internal CRON engine that can be used to create complex recurring reminders using all the internal data context Thor has about you and your team: You 4:02 PM Hey @Thor @Thor, every Friday at 4pm, compile a list of all tasks, meetings and discussions I completed during the week, remove any technical jargon, highlight any important customer-facing work and send it to my boss Sally. You 4:02 PM Hey @Thor @Thor, every Friday at 4pm, compile a list of all tasks, meetings and discussions I completed during the week, remove any technical jargon, highlight any important customer-facing work and send it to my boss Sally. Thor App 4:02 PM Scheduled β€” every Friday at 4:00pm in your timezone. I'll write it for a non-technical audience, call out customer-facing work, and DM Sally the summary. You can edit or pause this anytime from Automations. Thor Bot 4:02 PM Scheduled β€” every Friday at 4:00pm in your timezone. I'll write it for a non-technical audience, call out customer-facing work, and DM Sally the summary. You can edit or pause this anytime from Automations. you prompt β€Ί Use the Thor MCP to schedule a Friday 4pm reminder that compiles my week of work for Sally in non-technical language, highlighting customer-facing work. thor response Scheduled β€” every Friday 4:00pm Audience: non-technical Β· deliver to Sally Β· pause/edit via Automations ## Weekly Messages Thor can automatically send you a weekly recap at the end of Friday with a list of everything you accomplished, any outstanding action items & insights from the week. Additionally, Thor can send you a Monday kickoff message at the start of the week with a list of your priorities for the week. To enable this, click on "Manage Notifications" from the Thor "Home" tab and toggle "Weekly messages via DM" to on. ![weekly-messages](https://mintcdn.com/thor/ZicLt5N2ZynC2LYK/images/usecase-weekly-messages.png?fit=max\&auto=format\&n=ZicLt5N2ZynC2LYK\&q=85\&s=f2d2ba632996fee37434bd8b0a93eb67) ## Quick actions on reminders When a reminder includes a work item (an issue, PR or task), Thor renders inline quick action buttons directly in the message β€” so you can update status or take the next step without typing a single word. This updates the status of the work item immediately and keeps your systems of record in sync. Thor App Friday at 1:00 AM On Monday in the standup, you planned to update the Thor change log, create new feature videos, and refresh the docs for this week's recent changes. Let me know if you want help turning that into tracked issues or prioritizing the work. πŸ™ #46243 feat: migrate changelog from Headway to Plain Help CenterπŸ™ #2838 Thor v1.2 (March Public Launch) Thor Bot Friday at 1:00 AM On Monday in the standup, you planned to update the Thor change log, create new feature videos, and refresh the docs for this week's recent changes. Let me know if you want help turning that into tracked issues or prioritizing the work. πŸ™ #46243 feat: migrate changelog from Headway to Plain Help CenterπŸ™ #2838 Thor v1.2 (March Public Launch) you prompt β€Ί Use the Thor MCP to show my open reminder about the changelog and docs work, with the linked issues. thor response Reminder β€” changelog, feature videos, docs refresh \#46243 feat: migrate changelog from Headway to Plain Help Center \#2838 Thor v1.2 (March Public Launch) ## Manage automations from Slack [YouTube video player](https://www.youtube.com/embed/2QvtB0yrc-U) You can manage all of your Thor automations and reminders directly from the Thor Slack app's **Home** tab β€” no need to leave Slack: * **Browse** all of your active datetime triggers at a glance, with timezone-aware previews of exactly when each one will fire. * **Create** new automations and reminders, including fully custom prompts driven by Thor's CRON engine. * **Edit or delete** existing automations from an overflow menu. Open the Thor app in Slack, switch to the **Home** tab, and your automations will appear there. # Stand-ups Source: https://docs.thor.ai/usecases/standups Have Thor automatically generate your daily stand-up notes every morning. # Use cases ## Generate your daily stand-up notes Ever come to stand-up and forget what you worked on yesterday? Have Thor generate your daily stand-up notes every morning so you come prepared with updates: You 9:02 AM Hey @Thor @Thor, send me my stand-up notes for today. You 9:02 AM Hey @Thor @Thor, send me my stand-up notes for today. Thor App Today at 9:00 AM πŸ—“οΈ Standup Summary for Alex Rivera - Wed, July 29 Cancelled 🚫Atlas β€’ Drop the legacy webhook dual-write path β—¦ πŸ™ #2148 chore: remove dual-write for inbound webhooks PRs: 1 closed Completed βœ…Atlas β€’ Unblock SSO token refresh on mobile β—¦ πŸ™ #2201 fix: refresh tokens before background expiry β—¦ πŸ’¬ Thread in #atlas-eng + 1 other thread β€’ Ship the export CSV dry-run mode β—¦ πŸ™ #2187 feat: CSV export dry-run flag β—¦ πŸ“… Jul 28 - Atlas standup Meridian β€’ Resolve invoice pagination timeouts β—¦ πŸ™ #941 fix: paginate invoice export queries β€’ Investigate dashboard chart flicker β—¦ πŸ™ #955 fix: remount charts on filter change Other β€’ Reviewed onboarding copy for the help center launch β—¦ πŸ’¬ Thread in #docs Issues: 2 closed β€’ PRs: 1 authored, 4 closed, and 3 discussions β€’ Discussions: 2 action items Upcoming πŸ•’Meridian β€’ Fix null customer\_id on retry paths β—¦ πŸ™ #962 πŸ™ #968 β€’ Prep pricing sync follow-ups β—¦ πŸ“… Jul 29 - Pricing sync Thor Bot Today at 9:00 AM πŸ—“οΈ Standup Summary for Alex Rivera - Wed, July 29 Cancelled 🚫Atlas β€’ Drop the legacy webhook dual-write path β—¦ πŸ™ #2148 chore: remove dual-write for inbound webhooks PRs: 1 closed Completed βœ…Atlas β€’ Unblock SSO token refresh on mobile β—¦ πŸ™ #2201 fix: refresh tokens before background expiry β—¦ πŸ’¬ Thread in #atlas-eng + 1 other thread β€’ Ship the export CSV dry-run mode β—¦ πŸ™ #2187 feat: CSV export dry-run flag β—¦ πŸ“… Jul 28 - Atlas standup Meridian β€’ Resolve invoice pagination timeouts β—¦ πŸ™ #941 fix: paginate invoice export queries β€’ Investigate dashboard chart flicker β—¦ πŸ™ #955 fix: remount charts on filter change Other β€’ Reviewed onboarding copy for the help center launch β—¦ πŸ’¬ Thread in #docs Issues: 2 closed β€’ PRs: 1 authored, 4 closed, and 3 discussions β€’ Discussions: 2 action items Upcoming πŸ•’Meridian β€’ Fix null customer\_id on retry paths β—¦ πŸ™ #962 πŸ™ #968 β€’ Prep pricing sync follow-ups β—¦ πŸ“… Jul 29 - Pricing sync you prompt β€Ί Use the Thor MCP to get my standup for today. thor response πŸ—“οΈ Standup Summary for Alex Rivera - Wed, July 29 Cancelled 🚫 Atlas β€’ Drop the legacy webhook dual-write path (#2148) Completed βœ… Atlas β€’ Unblock SSO token refresh on mobile (#2201) β€’ Ship the export CSV dry-run mode (#2187) Meridian β€’ Resolve invoice pagination timeouts (#941) β€’ Investigate dashboard chart flicker (#955) Other β€’ Reviewed onboarding copy for the help center launch Upcoming πŸ•’ Meridian β€’ Fix null customer\_id on retry paths (#962, #968) β€’ Prep pricing sync follow-ups ## Daily briefings Skip the context switch to Slack. Ask your MCP client for today's standup and what needs your attention: you prompt β€Ί Use the Thor MCP to get my standup for today and call out what needs my attention. thor response Auth migration: PR #482 needs design review on logout redirect Billing: ENG-1849 waiting on Sam Attention: unblock #482 before the 3pm sync Connect Cursor or Claude from the [MCP tab on Quickstart](/quickstart). ## What's in your standup [YouTube video player](https://www.youtube.com/embed/SlpREWubZt8) Each standup is structured around the products and projects you've been working on, so it's easy to scan what's moving where: * **Grouped by product and project** β€” items are organized under the products and projects Thor has identified across your tools, rather than a flat list. * **Work items rendered inline** β€” the actual issues, PRs and tasks behind each update are embedded directly in the standup message, so you don't have to click out to get context. * **Show TLDR** β€” a button on every standup (individual and manager) collapses the full update into a short summary you can paste straight into your team's standup channel. * **Share** β€” forward your standup to a teammate or channel in one click, without re-typing or summarizing. ## Standup Reviews for Managers For managers who want to help their teams stay on track, Thor can now automatically send a list of each team member's standup summary to their manager. Managers can then add additional feedback and notes, and Thor will compile all this context into a single message sent to each individual team member the following morning. > [!WARNING] > > The feature is currently in closed beta. If you're interested in trying it out, please contact us at \[[support@thor.ai](mailto:support@thor.ai)]\(mailto:[support@thor.ai](mailto:support@thor.ai)). # Tasks Source: https://docs.thor.ai/usecases/tasks With a single command, Thor can summarize, assign, categorize and organize your tasks. # Pre-requisites To have Thor perform task management features you will need to connect at least one task management platform. Currently Thor supports **GitHub** and **Linear** issues. # Use cases ## Convert a thread into a task Thor can automatically summarize and extract any important action items from a long thread, and convert it into a task for you: Sam 2:14 PM Okay so to recap β€” we need to fix the flaky auth redirect on mobile, add a regression test, and ping design once it's up. Who can take this? Sam 2:14 PM Okay so to recap β€” we need to fix the flaky auth redirect on mobile, add a regression test, and ping design once it's up. Who can take this? You 2:15 PM Hey @Thor @Thor, can you create a task for the team based on this discussion? You 2:15 PM Hey @Thor @Thor, can you create a task for the team based on this discussion? Thor App 2:15 PM Created **Linear ENG-1842**: Fix flaky auth redirect on mobile. Description includes the regression test ask and the design follow-up from this thread. Want me to assign it to someone? Thor Bot 2:15 PM Created **Linear ENG-1842**: Fix flaky auth redirect on mobile. Description includes the regression test ask and the design follow-up from this thread. Want me to assign it to someone? you prompt β€Ί Use the Thor MCP to create a task from the #eng discussion about the flaky auth redirect on mobile. thor response Created Linear ENG-1842: Fix flaky auth redirect on mobile Includes regression-test ask + design follow-up from the thread. If you don't have a default repository configured, Thor will prompt you to choose one. ## Search for existing tasks Have Thor retrieve an existing task based on a freeform query: You 10:21 AM Hey @Thor @Thor, do we have any tasks logged for the authentication bug yet? You 10:21 AM Hey @Thor @Thor, do we have any tasks logged for the authentication bug yet? Thor App 10:21 AM Yes β€” **ENG-1842** ("Fix flaky auth redirect on mobile") was created earlier today from the #eng thread. Status: Todo. Want me to open it or assign it? Thor Bot 10:21 AM Yes β€” **ENG-1842** ("Fix flaky auth redirect on mobile") was created earlier today from the #eng thread. Status: Todo. Want me to open it or assign it? you prompt β€Ί Use the Thor MCP to find any tasks logged for the authentication bug. thor response ENG-1842 β€” Fix flaky auth redirect on mobile (Todo) Created earlier today from the #eng thread. ## Assign and categorize tasks Have Thor automatically assign and categorize your tasks: You 10:24 AM Hey @Thor @Thor, assign issue #123 to @John and tag it with any relevant labels. You 10:24 AM Hey @Thor @Thor, assign issue #123 to @John and tag it with any relevant labels. Thor App 10:24 AM Done β€” assigned #123 to John and added labels **bug**, **auth**, and **mobile**. Thor Bot 10:24 AM Done β€” assigned #123 to John and added labels **bug**, **auth**, and **mobile**. you prompt β€Ί Use the Thor MCP to assign issue #123 to John and apply relevant labels. thor response Assigned #123 β†’ John Labels: bug, auth, mobile ## Delegate to coding agents [YouTube video player](https://www.youtube.com/embed/ajQsvq4ZKEI) Have Thor assess if a task is suited for delegation to your favorite AI coding assistant. Currently supported coding agents are Cursor, Claude, Tembo and Charlie. You 11:05 AM Hey @Thor @Thor, is issue #123 a good candidate for a coding agent? If yes, assign it to Cursor. You 11:05 AM Hey @Thor @Thor, is issue #123 a good candidate for a coding agent? If yes, assign it to Cursor. Thor App 11:05 AM Yes β€” it's well-scoped, has clear acceptance criteria, and doesn't need product judgment. Assigned #123 to Cursor and attached the related thread context. Thor Bot 11:05 AM Yes β€” it's well-scoped, has clear acceptance criteria, and doesn't need product judgment. Assigned #123 to Cursor and attached the related thread context. you prompt β€Ί Use the Thor MCP to check if issue #123 is a good coding-agent candidate, and if so assign it to Cursor. thor response Yes β€” well-scoped, clear acceptance criteria. Assigned #123 β†’ Cursor (thread context attached). Connect Cursor or Claude from the [MCP tab on Quickstart](/quickstart) so your coding agent can pull issue context, related discussions, and prior decisions directly from Thor. ## Context for coding agents Someone decides something in a meeting. Someone else changes their mind in Slack on Friday. The ticket still says what it said three weeks ago. Nobody lied. The team just moved faster than its own notes. Then a coding agent reads that ticket and builds exactly what it says, including the parts that are no longer true. Thor keeps the record current and hands it to whoever picks up the work next, human or agent. When Thor has something worth adding, it injects a briefing into the GitHub or Linear issue body. That is the context pack, written onto the ticket so whoever opens the issue already has it. The block is folded so it does not clutter the description. A person sees one line, `Additional context (powered by Thor AI)`. An agent reading the issue sees the full context pack: parent work, related PRs, governing docs, meetings, and decisions. The last line of that block tells the agent how to call Thor if the bullets are not enough. > [!NOTE] > > Thor embeds that block into **GitHub issue** and **Linear issue** bodies. If you don't see *Additional context (powered by Thor AI)* on your tickets yet, email [support@thor.ai](mailto:support@thor.ai). Thor doesn't write the code. That's what Cursor, Claude Code, and the rest are for. Thor makes sure the agent doing the work has the right historical context. ## Update progress from your editor If you are heads-down in your editor and need to update Linear with your progress, your MCP client can post it back to Thor: you prompt β€Ί Use the Thor MCP to update Linear to reflect that I'm working on issue #123 and note where the latest blocker is. thor response Updated #123 β†’ In Progress Blocker noted: waiting on design review for logout redirect ## Task Subscriptions Thor can monitor tasks for important updates, comments and changes, then notify you via DM when this occurs: You 4:40 PM Hey @Thor @Thor, let me know when someone starts work on issue #145. You 4:40 PM Hey @Thor @Thor, let me know when someone starts work on issue #145. Thor App 4:40 PM Got it β€” I'll DM you when #145 moves out of Todo or gets an assignee. You can also ask me to watch for blocked or completed. Thor Bot 4:40 PM Got it β€” I'll DM you when #145 moves out of Todo or gets an assignee. You can also ask me to watch for blocked or completed. you prompt β€Ί Use the Thor MCP to notify me when someone starts work on issue #145. thor response Subscribed to #145 β€” will alert when it leaves Todo or gets an assignee. Other examples: > [!NOTE] > > Hey `@Thor`, notify me when github.com/microsoft/vscode/issues/145 is completed > [!NOTE] > > Hey `@Thor`, alert me if issue #42 gets blocked or closed # Busy Work Source: https://docs.thor.ai/why-thor/busy-work Coding agents removed the busy work of writing software. Thor removes the busy work of running a software team. > [!TIP] > > You shouldn't have to choose between doing the work and tracking the work. Thor handles the tracking. You focus on the work. # The work nobody wants to do Every team is held together by a quiet pile of busy work. Nobody enjoys it. Almost nobody is great at it. If it doesn't get done, things start to fall apart. You know the list: * Writing the issue *after* the Slack discussion ended. * Updating the issue's status when you actually start it. Or finish it. Or get blocked. * Writing meeting notes. Tagging the right people. Listing action items. * Following up the next day to see if those action items got done. * Updating the doc that became wrong as soon as the feature shipped. * Logging the decision that was *clearly made* in chat but written down nowhere. * Closing out the "good idea, but we're not doing it" so nobody re-pitches it in three months. This is the connective tissue of a healthy team. It's also exactly the work that gets skipped when people are busy, which is always. # You skipped hiring a PM. You didn't skip the PM work. A lot of fast-moving AI-first teams have made a deliberate call: no dedicated project manager, no dedicated product manager, no extra layer of process. Engineers ship. Founders decide. Things move. The problem is that the work a PM would have done didn't disappear. The issues still need to be written. Decisions still need to be tracked. Action items still need follow-up. Docs still need to stay current. That work just quietly landed on whoever was closest to it, usually the tech lead or the founder. The same people who were supposed to be heads-down building are now writing meeting notes, updating the roadmap, and chasing down owners. You inherited it. It's slowing you down. # What LLMs did for code, Thor does for the team Cursor and Claude Code didn't make engineers obsolete. They removed the parts of writing software that were tedious and repetitive, like boilerplate, unit tests, and doc drafts, so engineers could spend their time on the parts that actually need a brain. Thor does the same thing for everything *around* the code. It doesn't replace the judgment calls. It doesn't replace the meetings, the decisions, or the work itself. It removes the **paperwork around** the work β€” the tracking, logging, tagging, summarizing, reminding, and following up that has to happen for the team to stay coordinated, but that nobody signed up to do. # Thor doesn't replace your tools. It makes them work better. You already picked the tools your team likes. Linear, GitHub, Google Docs, Notion, Google Calendar, Zoom, Slack. Thor's job isn't to replace any of them β€” it's to make them more accurate, more current, and more useful. * **Linear and GitHub stay your source of truth for issues.** Thor makes sure issues exist, get updated, and reflect what's actually happening. * **Google Docs and Notion stay where knowledge lives.** Thor reads the pages you share and uses them as context when answering questions, drafting issues, and checking whether work aligns with your specs. * **Google Calendar, Meet, and Zoom stay where meetings happen.** Thor turns transcripts into action items in the systems you already use. * **Slack stays where your team talks.** Thor lives there too β€” no new app to check. Every action Thor takes lands in a system you already trust. Same tools you have today, with the tracking, history, and follow-up they were always supposed to have. # What Thor actually handles ## Not every change needs a task. The big ones do. AI has made some work so fast that logging it is overhead. Need a small fix or a one-off script? Hand it to Claude or Cursor, get a PR, ship it. The whole loop takes minutes; a Linear ticket would slow it down, not help it. But that's not most of what your team does. Bigger projects, long-running work, epics, anything that spans more than one person or more than a week: those still need a tracked home. Roadmaps need work items. Estimates need a record of what's actually been done. New hires need a trail to follow. And the *useful* tasks β€” the ones tied to real work in flight β€” are exactly the ones that get neglected. The discussion happened in Slack. The decision happened in a meeting. By the time someone gets back to Linear, half the context is gone. Thor closes that gap: * Turn a Slack thread into a properly written GitHub or Linear issue in one message. See [Tasks](/usecases/tasks). * Pull action items out of meeting transcripts and offer to convert them into tracked work. See [Meetings](/usecases/meetings). * Notice when work has started, stalled, or finished, and offer inline buttons to update status without leaving Slack. See [Quick actions](/usecases/reminders#quick-actions-on-reminders). When the tasks that matter actually reflect reality, your roadmaps, estimates, and reports start to mean something. ## Written context should actually get used Specs, PRDs, and decision docs only help when people read them β€” and when the work in flight actually reflects what's written. Thor indexes the Notion pages and Google Docs you share and folds them into the [data layer](/why-thor/data-layer) alongside your issues, meetings, and Slack threads. Ask whether recent tasks align with a spec, draft an issue from a requirements doc, or get a summary without copying pages into chat. See [Documents](/usecases/docs). The bar isn't "every doc is perfect." It's "the context your team already wrote is available when decisions get made." ## Conversations should leave a trace Every meeting and every long Slack thread either produces something concrete or leaves a question hanging. Both need to be captured, including the boring ones. After a meeting, Thor will: * DM each participant their action items and decisions. * Cross-reference anything that was *also* discussed in a previous meeting (so "we already decided this" stops happening). * Follow up the next day if action items haven't moved. Even the "good idea, but we're not doing it" decisions get logged, because future-you will thank present-you for writing it down. # What you get when this works When the busy work gets done consistently: * **Predictability gets better**, because what's in flight reflects what's actually happening. * **Onboarding gets faster**, because the trail of decisions actually exists. * **Less work falls through the cracks**, because action items have an owner and a follow-up. * **Your lead gets a real picture**, because reports aren't built on incomplete data. * **Your AI agents get smarter**, because they have a reliable history to draw from. When it doesn't, the team runs on tribal knowledge, status meetings, and the heroics of whichever person is best at remembering things. # An honest note Thor handles a lot, but it doesn't replace your judgment. Thor will draft an issue from a Slack thread, and you decide whether to ship it. Thor will read a spec and suggest how work aligns with it, and you decide what to change. Thor will surface action items from a meeting, and you call which ones matter. Think of Thor as a teammate who does the first 80% of the busy work for you. The last 20% β€” the part that needs your call β€” is still yours. # Data Layer Source: https://docs.thor.ai/why-thor/data-layer Thor doesn't just connect to your tools. It builds a live graph of how your team actually works. > [!TIP] > > Knowledge bases tell you what was written down. Thor tells you what your team is doing. # Why Thor isn't just another bot Most AI tools start with a connector and end with a prompt. You hook them up to GitHub, Slack, Linear, Notion, and your calendar, and every question turns into a frantic round-trip across five different APIs. Your agent rebuilds your company from scratch every single time. We built Thor differently. Underneath everything Thor does is a live graph of your team's work β€” what's in flight, who owns it, what's blocked, what changed, what was decided. It's not a knowledge base. It's not enterprise search. It's a working picture of how your team runs, kept up to date as you go. # What's in the graph (and what isn't) Knowledge bases store artifacts: docs, wiki pages, reports. Useful, but that's not where work actually happens. Most of the stuff that matters never becomes a clean artifact: * Someone gets blocked in a Slack thread at 4pm. * Scope changes mid-meeting because Sarah raised a concern. * Two engineers commit to reviewing each other's PRs by Friday. * A product call gets made in three messages and a thumbs-up. Thor catches all of that. It treats Slack threads, meetings, and tickets as places where **work changes** β€” not just text to search later. The graph connects: * **Work items** stitched together from Slack threads, meeting clips, Linear issues, GitHub PRs, and the documents that actually describe them. * **Documents** from Notion and Google Docs you explicitly share β€” specs, PRDs, runbooks, and decision records Thor can search and read when answering questions or drafting work. * **People** as owners, reviewers, blockers, and decision-makers. * **Projects and products** picked up from how your team talks about them, not from a perfectly maintained taxonomy nobody has time to keep up. * **What's happening** β€” blockers, commitments, handoffs, scope changes, decisions, stalled work. ## Your team's vocabulary, in one place ![team-glossary](https://mintcdn.com/thor/YYCrix9H3kEt1_oM/images/team-glossary.png?fit=max\&auto=format\&n=YYCrix9H3kEt1_oM\&q=85\&s=4b3418c9c99a3916d82dc4bdee96029c) Every org has its own language β€” product codenames, internal acronyms, customer names, process jargon. Thor centralizes that vocabulary in a **Team Glossary**: terms are mined from your issues, Slack, and meetings, then injected into prompts so standups, summaries, and agent replies use the words your team actually uses β€” not generic LLM guesses. Thor's not a mind reader. If your team only talks about a project in DMs Thor can't see, it'll miss it. But for the work that happens in shared channels, meetings, and the tools you've connected, Thor builds a surprisingly complete picture. # Why one graph beats five raw connectors You could connect your AI agent directly to GitHub MCP, Slack MCP, Linear MCP, Drive MCP, and a calendar MCP. Plenty of teams do. The problem isn't access. It's interpretation. A raw GitHub MCP can tell your agent that PR #482 is open. It can't tell your agent that the PR's been sitting because the owner has been waiting on design feedback for three days, the design discussion happened in a meeting last Tuesday, and the relevant Linear issue is actually #1041, not the one in the PR description. Thor knows. That's the difference between **tool access** and **team context**. Raw connectors hand your agent a pile of disconnected responses. Thor hands it a graph. # Always current. Always reconciled. The graph isn't a one-time export. Thor keeps it up to date as work moves across your tools. That matters more than it sounds. A blocker that got resolved yesterday shouldn't shape today's standup. A project whose scope shifted this morning shouldn't be understood through last week's stale ticket. And when the tools disagree (a GitHub PR looks unblocked but Slack says the owner is waiting on feedback), Thor reconciles. It surfaces the real state, not the optimistic one. # One graph. Humans and agents. The same graph that powers your morning Slack briefing also powers Thor's [MCP server](/quickstart). That means: * **You** can ask Thor in Slack, "what's blocking the auth migration?" and get a real answer, not a list of search results. * **Your coding agent** can ask Thor, "what should I know before working on issue #123?" and get the related Slack threads, prior decisions, ownership, and adjacent work in a single call. * **Your lead** can get a Friday recap that knows the difference between a project that shipped and one that quietly drifted. Same graph. Same source of truth. No more pasting Slack threads into prompts every time you start a new conversation. # Proactivity Source: https://docs.thor.ai/why-thor/proactivity Most AI waits for you to ask. Thor doesn't. > [!TIP] > > Reactive AI answers your questions. Proactive AI tells you which questions to ask. # AI shouldn't wait for a prompt You open ChatGPT. You type a question. You wait. You read. You close the tab. You open Cursor. You highlight some code. You write a prompt. You wait. You apply the diff. You spend an afternoon wiring up an n8n flow or a CRON job. You hope you anticipated the conditions that matter. You forget about it. Three weeks later it breaks silently and nobody notices. Every interaction starts with **you** deciding something is worth asking about. That's a problem, because the things that matter most are usually the ones you don't yet know to ask about. The blocker that just appeared in a thread you're not in. The teammate who quietly missed a commitment. The decision that got reversed in a meeting you skipped. The customer issue three different people mentioned in three different channels this week. You can't prompt your way to context you don't have. # Thor comes to you We built Thor on a different premise: the AI should pay attention so you don't have to. Instead of waiting in a chat window, Thor watches the actual flow of work β€” Slack threads, meetings, ticket activity, PRs, docs β€” and pings you when something matters. Not when *anything* happens. When something **you** would want to know about. That includes: * A meeting you were in just ended, and you've got three action items. * A teammate said they'd follow up on something yesterday and haven't. * A product change you're waiting just got blocked. * A decision you cared about was made in a thread you missed. * It's Friday at 4pm and you struggle to remember what the team actually got done this week. You don't program any of this. No triggers, no CRON expressions, no n8n graphs to maintain. You tell Thor in plain English what to keep an eye on, and Thor figures out when to come back to you. # A chief of staff for your work The mental model that fits best: a really good chief of staff. They sit in on every meeting. They keep tabs on every channel. They read every PR description. They notice when something stalls. They notice when a question went unanswered. They notice when a decision got made but nobody wrote it down. And, more importantly, they don't wait to be asked. They DM you and say "hey, I think you wanted to know about this." That's Thor. # Thor isn't perfect Sometimes Thor pings you about something you don't care about. Sometimes Thor misses something you wish it had caught. When that happens, tell Thor (in plain English) to back off on a topic, or to pay closer attention to one. The more you use Thor, the better it gets at picking the right moments. This is still early days, and some rough edges are expected. # Reactive vs. proactive, in practice Same task, two ways: **Reactive AI** waits for you to ask β€” and that only works if you (1) remember the meeting happened, (2) remember to ask, and (3) ask the right question. **Proactive Thor** comes to you: Thor App 8:04 AM Heads up: three pricing decisions were made in yesterday's leadership sync. Two need follow-up from your team. Want me to draft action items? Thor Bot 8:04 AM Heads up: three pricing decisions were made in yesterday's leadership sync. Two need follow-up from your team. Want me to draft action items? You 8:06 AM Yes β€” draft them and assign the ones that look like mine. You 8:06 AM Yes β€” draft them and assign the ones that look like mine. Thor App 8:06 AM Drafted two tasks from the sync and assigned the owner follow-ups to you. The third is waiting on Finance β€” I subscribed you to updates. Thor Bot 8:06 AM Drafted two tasks from the sync and assigned the owner follow-ups to you. The third is waiting on Finance β€” I subscribed you to updates. you prompt β€Ί Use the Thor MCP to draft action items from yesterday's leadership sync pricing decisions and assign the ones that look like mine. thor response Drafted 2 tasks Β· assigned your follow-ups Subscribed you to the Finance-owned item Same data. Different outcome. The reactive version requires you to know what you don't know. The proactive version assumes you don't, and helps anyway. # Things Thor does without being asked Out of the box, Thor will: * DM each meeting participant a recap of action items and decisions a few minutes after a meeting ends. See [Meetings](/usecases/meetings). * Send you a daily standup with what you worked on yesterday. See [Stand-ups](/usecases/standups). * Send a Friday recap and a Monday kickoff. See [Weekly Messages](/usecases/reminders#weekly-messages). * Tell you when a task you care about gets blocked, completed, or reassigned. See [Task Subscriptions](/usecases/tasks#task-subscriptions). * Follow up the next day if you haven't closed out an action item from a meeting. You can also tell Thor to watch for arbitrary things, with no scripting required: You 9:30 AM Hey @Thor @Thor, let me know if anyone mentions the auth migration this week. You 9:30 AM Hey @Thor @Thor, let me know if anyone mentions the auth migration this week. Thor App 9:30 AM On it β€” I'll ping you when the auth migration comes up in channels, threads, or meetings this week. Thor Bot 9:30 AM On it β€” I'll ping you when the auth migration comes up in channels, threads, or meetings this week. you prompt β€Ί Use the Thor MCP to watch for anyone mentioning the auth migration this week. thor response Watching channels, threads, and meetings for "auth migration" this week.