PathFox Product Intelligence

PathFox is PathPro's built-in AI assistant that understands your project's context — its tasks, features, submissions, and community activity. Rather than a generic chatbot, PathFox is trained on what's happening in your project right now, giving you actionable product intelligence on demand.

What is PathFox?

PathFox is an AI-powered product intelligence assistant that lives inside every PathPro project. Unlike general-purpose AI tools, PathFox has deep awareness of your specific project data — your roadmap tasks, feature requests, community submissions, voting patterns, comments, and analytics. This means every answer it provides is grounded in the real state of your project, not generic advice.

Each project gets its own independent PathFox context. If you manage multiple projects in PathPro, PathFox in Project A knows nothing about Project B. This isolation ensures that responses are always relevant and that sensitive information stays compartmentalized across projects.

PathFox is available to project admins and team members. Community members do not have access to the AI assistant, keeping your internal analysis private from your public audience.

Starting a Chat Session

To open PathFox, click the floating chat bubble in the bottom-right corner of any project page. The chat panel slides open, and you can immediately start typing your question or request. PathFox maintains conversation history within your current session, so you can ask follow-up questions without repeating context.

The chat interface supports natural language — you don't need special commands or syntax. Ask questions like "What are the most requested features this month?" or "Are there any duplicate submissions about dark mode?" and PathFox will analyze your project data to respond.

PathFox is context-aware based on the page you're currently viewing. If you open PathFox while on the Feature Voting page, it automatically scopes its analysis to voting data. If you open it on the Submissions page, it focuses on community feedback. You can always ask about anything regardless of the page, but the default context helps PathFox give you the most relevant answers first.

PathFox AI What are the top requested features? Based on 247 votes across 34 features: 1 Dark Mode 142 votes 2 API Access 98 votes 3 Mobile App 67 votes Would you like a detailed breakdown of any of these features? Ask PathFox...
PathFox chat interface open on a project page

Demand Scoring

One of PathFox's most powerful capabilities is demand scoring. When you ask PathFox to evaluate demand for a feature or topic, it analyzes multiple data sources across your project: vote counts on feature requests, the frequency of related submissions, comment sentiment, and how recently activity occurred. It then produces a demand score that helps you prioritize what to build next.

Demand scores are presented on a relative scale within your project. A high demand score means that a particular feature or theme has significantly more community interest compared to other items. PathFox also explains why a score is high or low, citing the specific data points that influenced the ranking — for example, "Dark mode has 47 votes, 12 related submissions in the last 30 days, and overwhelmingly positive comment sentiment."

You can ask PathFox to rank all features by demand, compare demand between two specific features, or identify emerging demand trends that haven't yet accumulated high vote counts but show accelerating interest patterns.

Demand Score Analysis Feature: Dark Mode Support 87 /100 Demand Score Community Votes 142 Related Submissions 8 Comment Mentions 23 Trend Rising Analysis based on data from the last 90 days
PathFox demand score analysis for a feature request

Duplicate Detection

As your project grows, community members will inevitably submit feedback that overlaps with existing feature requests or previous submissions. PathFox uses semantic analysis to detect duplicates — not just exact text matches, but submissions that describe the same underlying need in different words.

Ask PathFox "Are there any duplicate submissions?" and it will scan your recent submissions, group related ones together, and present clusters of duplicates with confidence scores. For each cluster, PathFox identifies the original submission and suggests which duplicates could be merged or closed with a reference to the original.

You can also ask PathFox to check a specific submission against existing content: "Is this submission a duplicate of anything?" This is especially useful during triage, when you're reviewing new feedback and want to quickly determine if the topic has already been captured.

Sentiment Analysis

Understanding how your community feels goes beyond counting votes. PathFox performs sentiment analysis across comments, submissions, and discussion threads to give you a qualitative picture of community mood. It categorizes sentiment as positive, neutral, negative, or mixed, and provides specific examples to support its assessment.

Sentiment analysis is particularly useful for identifying frustration before it escalates. If a particular feature request is attracting increasingly negative comments, PathFox can flag this trend and suggest that the team respond with a status update or timeline estimate. Conversely, if a recent release note is generating enthusiastic responses, PathFox highlights that as a signal of what's resonating with your audience.

You can ask for sentiment on a specific topic ("How do people feel about our mobile app performance?"), across a time period ("What's the overall sentiment this month?"), or for a comparative view ("Is sentiment better or worse than last month?").

Use Case Shout-Out
PathFox doesn't just answer questions — it adapts to where you are. Ask about demand on the Feature Voting page and it analyzes voting patterns. Ask the same on Submissions and it groups community themes.

Context-Aware Analysis

PathFox adapts its analytical capabilities based on which page you're currently viewing. While you can always ask any question from any page, the default context determines which data sources PathFox prioritizes and which specialized analysis tools it brings to bear. This means you get the most relevant insights without having to specify exactly what data you want PathFox to look at.

Submissions Context

When you open PathFox from the Community Submissions page, it automatically focuses on incoming community feedback. In this context, PathFox excels at theme grouping — clustering related submissions into categories so you can see the big picture of what your community is asking for. It also performs duplicate detection to flag redundant submissions, hostility flagging to identify abusive or unconstructive feedback that may need moderation, and summarization to condense long submission threads into actionable takeaways.

A common workflow is to open PathFox on the Submissions page at the start of each week and ask "Summarize this week's submissions." PathFox will group them by theme, highlight any duplicates, flag anything requiring moderation, and give you a prioritized list of the most impactful feedback.

Feature Voting Context

On the Feature Voting page, PathFox shifts its focus to voting patterns and demand analysis. It can rank features by demand score, identify voting trends over time, detect features that are gaining momentum, and highlight capabilities that your community considers table-stakes versus nice-to-haves. This context is ideal for sprint planning sessions where you need data-driven input on what to build next.

Roadmap Context

When accessed from the Roadmap page, PathFox focuses on task and milestone analysis. You can ask it to search for specific tasks, analyze progress across task groups, identify bottlenecks in your current sprint, or compare estimated versus actual completion rates. PathFox can also cross-reference your roadmap with community demand, helping you answer the question "Are we building what our users actually want?"

Analytics Context

From the Analytics Dashboard, PathFox provides growth analysis, priority recommendations based on data trends, and a comprehensive sentiment overview. It can interpret your analytics charts in natural language — for example, "Your community growth rate increased 23% this month, driven primarily by organic traffic to your feature voting page." This context is especially useful for preparing stakeholder reports or board updates.

AI-Generated Summaries

Beyond the chat interface, PathFox powers automatic summaries throughout PathPro. When viewing a feature request with extensive community discussion, PathFox generates a concise summary at the top of the page that captures the key points, common requests, and overall sentiment. This saves you from reading through dozens of individual comments to understand the community's position.

Task summaries work similarly — for tasks with long comment threads or complex subtask hierarchies, PathFox provides a natural-language overview of the current state: what's been completed, what's blocking progress, and what the team is discussing. These summaries update automatically as new activity occurs.

You can also ask PathFox to generate summaries on demand for any collection of items. For example, "Summarize all features tagged as high priority" or "Give me a summary of submissions from enterprise customers this quarter."

Use Case Shout-Out
One team used PathFox to detect that 30% of their submissions were duplicates — saving hours of manual triage every week.

Token Usage and Limits

PathFox uses AI tokens to process your questions and analyze project data. Each message you send and each response PathFox generates consumes tokens. Your token allocation depends on your PathPro plan — higher-tier plans include more tokens per month, and unused tokens do not roll over.

You can monitor your current token usage from the project settings page under the AI section. PathPro displays your total allocation, how many tokens you've used this billing cycle, and an estimate of how many questions that remaining balance can support. If you're approaching your limit, PathPro will notify you so you can adjust your usage or upgrade your plan.

Token consumption varies based on the complexity of your question and the amount of project data PathFox needs to analyze. Simple questions like "How many open tasks do we have?" use fewer tokens than complex analyses like "Rank all features by demand and explain the top five." To optimize token usage, be specific in your questions — the more targeted your request, the less data PathFox needs to process.