# FEATURES - [Focus](https://help.swarmia.com/features/focus.md) - [Focus summary](https://help.swarmia.com/features/focus/focus-summary.md): The focus summary allows you to easily explore what your teams and organization are spending the most effort (FTEs) on. - [Investment balance](https://help.swarmia.com/features/focus/balance-engineering-investments.md): Analyze team focus, improve time allocation and boost focus on top priorities - [Activity and effort-based models](https://help.swarmia.com/features/focus/balance-engineering-investments/activity-and-effort-based-models.md): Swarmia supports two different models to measure the work: activity-based and effort-based - [Categorization](https://help.swarmia.com/features/focus/balance-engineering-investments/categorizing-work.md): Configure custom categories and and improve the categorization rate. - [Initiatives](https://help.swarmia.com/features/focus/deliver-strategic-initiatives.md): Set up your initiatives to enable visibility beyond team-level work. - [Forecasting initiatives](https://help.swarmia.com/features/focus/deliver-strategic-initiatives/forecasting-initiatives.md): Estimate how long initiatives will take. - [Work log](https://help.swarmia.com/features/focus/analyzing-the-activity-patterns-on-work-log.md): Work log visualizes the various activities of your team. Knowing which work patterns to avoid and which to aim for helps teams improve their health and development speed. - [Sprints](https://help.swarmia.com/features/focus/sprints.md): Swarmia tracks the issues linked to your sprints and helps you visualize scope increase and carryover. - [Metrics](https://help.swarmia.com/features/metrics.md) - [Code metrics](https://help.swarmia.com/features/metrics/code-metrics.md) - [PR cycle time](https://help.swarmia.com/features/metrics/pull-request-cycle-time.md): Pull request cycle time (or PR cycle time) is the total time a pull request spends in all stages of the development pipeline. - [Time to review](https://help.swarmia.com/features/metrics/pull-request-cycle-time/time-to-review.md): Learn how Swarmia calculates pull request review metrics, including time to first review and review time. - [What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?](https://help.swarmia.com/features/metrics/pull-request-cycle-time/whats-the-difference-between-change-lead-time-and-pull-request-cycle-time-metrics-in-swarmia.md) - [DORA metrics](https://help.swarmia.com/features/metrics/track-dora-metrics.md): Analyze deployment frequency and quality across your entire organization in Swarmia. - [Automatic change failure detection](https://help.swarmia.com/features/metrics/track-dora-metrics/automatic-change-failure-detection.md): Automatically detect DORA change failures from application version rollback, pull request reverts, and advanced hotfix filters. - [How Swarmia links PRs to deployments](https://help.swarmia.com/features/metrics/track-dora-metrics/how-swarmia-links-prs-to-deployments.md): Linked PRs are used to calculate change lead time and time to deploy. The are also used to determine who owns the deployment. - [Issue metrics](https://help.swarmia.com/features/metrics/issue-cycle-time.md): Issue metrics help you understand how your engineering teams are delivering work — how fast issues move through your process, how much work is in progress, and how throughput changes over time. - [CI visibility](https://help.swarmia.com/features/metrics/get-visibility-into-your-ci-pipeline.md): Swarmia provides you with the most important CI metrics for tracking your CI health - [Explore](https://help.swarmia.com/features/metrics/explore.md) - [AI tools](https://help.swarmia.com/features/ai-tools.md): Combine developer experience surveys, adoption metrics, and usage patterns to understand how AI coding tools play into your software organization’s productivity. - [AI adoption](https://help.swarmia.com/features/ai-tools/ai-adoption.md): Track GitHub Copilot, Cursor, and Claude Code licenses and adoption across your teams over time - [GitHub Copilot activity](https://help.swarmia.com/features/ai-tools/github-copilot-activity.md): See detailed GitHub Copilot activity patterns across teams, features, models, editors, and programming languages - [Cursor activity](https://help.swarmia.com/features/ai-tools/cursor-activity.md): See detailed Cursor activity patterns across teams and modes - [Claude Code activity](https://help.swarmia.com/features/ai-tools/claude-code-activity.md): See detailed Claude Code activity patterns across teams and modes - [AI impact](https://help.swarmia.com/features/ai-tools/ai-impact.md): See how pull requests assisted by different AI coding tools — or no AI tools — perform across metrics like throughput, cycle time, batch size, and review time. - [Cloud agents](https://help.swarmia.com/features/ai-tools/cloud-agents.md): Gain visibility into the pull requests created by AI agents running in the cloud. See how they perform across metrics like throughput, merge percentage, and batch size. - [AI tool detection & filters](https://help.swarmia.com/features/ai-tools/ai-tool-detection-and-filters.md): Swarmia automatically detects pull requests assisted by GitHub Copilot, Cursor, or Claude Code - [PR inbox](https://help.swarmia.com/features/managing-pull-requests-in-progress-with-the-pull-request-view.md): See all open pull requests and where they are going in a team context. - [Working agreements](https://help.swarmia.com/features/working-agreements.md): Working agreements help teams continuously improve with clear goals and consistent execution - [Surveys](https://help.swarmia.com/features/run-developer-experience-surveys.md): See what truly affects developer experience and productivity by viewing relevant survey results alongside your system data. - [Creating a survey](https://help.swarmia.com/features/run-developer-experience-surveys/creating-a-survey.md): Improve developer experience by collecting insights directly from your engineers at scale. Identify patterns and turn them into actions. - [Managing surveys](https://help.swarmia.com/features/run-developer-experience-surveys/managing-surveys.md): You can create, preview, duplicate, close, and delete surveys. - [Viewing and sharing survey results](https://help.swarmia.com/features/run-developer-experience-surveys/viewing-and-sharing-survey-results.md): After a survey ends, you can review the results, publish them to your teams, or export them - [How we show your survey responses](https://help.swarmia.com/features/run-developer-experience-surveys/how-we-show-your-survey-responses.md): Responses are reported by team. You can choose whether to show your name in comments. - [Survey communication guide and templates](https://help.swarmia.com/features/run-developer-experience-surveys/survey-communication-guide-and-templates.md): You can use this messaging sequence and templates to communicate your developer experience survey to your teams. - [Software capitalization](https://help.swarmia.com/features/capitalize-software-development-costs.md): Use developer activity data from Swarmia to generate capitalization reports and blend with cost data. - [Timesheets](https://help.swarmia.com/features/capitalize-software-development-costs/timesheets.md): Timesheets help your organization record, approve, and export hours at the daily and individual level without manual tracking during work. - [Swarmia AI](https://help.swarmia.com/features/swarmia-ai.md) - [Developer overview](https://help.swarmia.com/features/coach-software-developers.md): Visualize engineering work with Developer Overview - [Notes](https://help.swarmia.com/features/notes.md): You can attach freeform context information to work items like pull requests and issues with notes. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.swarmia.com/features.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.