This release keeps developer identity private during AI analysis. It also gives self-managed customers a CIS Level 2 report for every image.
Highlights
Developer identity stays private in AI analysis
Navigara now replaces developer names and email addresses with placeholders before it sends text to the AI model. The model never sees who wrote the code. Navigara puts the real names back in the results, so summaries and insights look the same to you.CIS Level 2 reports for every image
Each release now includes a CIS Level 2 compliance report for each of the three self-managed images. Every image must reach a minimum score before we sign and publish it. You can share the reports with your security and audit teams.Smaller frontend image
The frontend image now uses a minimal base image that contains only the runtime it needs. The image is smaller and has fewer system packages to maintain. We strengthened the security of the platform.Also in this release
- AI agent sessions now link to work items through the commits they create or name, so more sessions appear with their pull requests.
- Large organizations see faster processing after a sync of an issue tracker or source control.
- The checks, billing, and connections pages now show a clear message when data cannot load, and keep updating after a retry.
Important changes
Upgrade notes
This release makes it easier to start measuring AI adoption. A new setup flow installs the Navigara CLI with one command.
Highlights
New AI adoption setup
After sign-up, a new setup flow guides you to your first AI adoption data. One command installs the Navigara CLI on your computer. Self-managed deployments get commands that point to their own address.Team rollout with one command
Administrators can roll out the Navigara CLI to a whole team with one command from their device management tool. The command sets up every user on the computer who uses Claude Code or Codex.Also in this release
- The dashboard now shows the AI adoption cards.
- Navigara now syncs pull requests of very large repositories in smaller parts, and runs more syncs at the same time.
This release connects more AI coding sessions to the work they belong to. Work Activity now shows a fuller picture of each work item. Imported Codex history now counts in your AI usage.
Highlights
Sessions join the work they mention
An AI coding session that mentions a pull request, an issue, or a branch now joins the work item of that pull request, issue, or branch. When stronger evidence appears later, such as a commit, Navigara moves the session to the correct work item.Codex sub-agents join their parent session
Codex can start sub-agents to do part of a task. Navigara now links each sub-agent to the session that started it. Its pull requests, branches, and commits join the work item of the parent session. Sub-agents do not add to your session count.Imported Codex history in AI usage
Navigara now keeps the Codex usage history that you import for each Developer. Imported history counts up to the day that live Codex data for that Developer starts. From that day, Navigara uses only the live data, so no usage counts twice.Also in this release
- The issue tracker row in Connections now shows “Status unknown” and a retry icon when Navigara cannot load the sync status. Sync stays off until the status loads.
- We strengthened the security of the platform.
Upgrade notes
This release makes Work Activity available to every organization. It also links more AI agent sessions to the pull requests and issues they worked on.
Highlights
Work Activity
Work Activity is now available to every organization. It groups agent sessions, pull requests, and commits into one work item. Open it from the sidebar or from My Performance. A short introduction shows the first time you open the page.Agent sessions link to more tools
Navigara now links AI agent sessions to pull requests and issues through any MCP server, not only Linear and GitHub. This includes Jira, GitLab, and Azure DevOps. More command-line tools and Git commands also create links. Navigara links a session only when the reference is clear, so unrelated work stays separate.Also in this release
- The onboarding page now shows one install command for the Navigara CLI. The installer starts the setup wizard for you.
- The welcome form now asks what you searched for when you found Navigara through Google Search. The answer is optional.
This release puts AI adoption at the center of Navigara. You get named adoption levels, a new dashboard, and clear charts that compare AI spend with delivered work. New connections bring in data from Cursor, YouTrack and Asana Goals.
Highlights
Redesigned dashboard
The dashboard now has four full-width panels: AI adoption, Performance, Objective alignment and AI usage. The AI adoption panel shows each active Developer as one dot at their score, with the Organization average as a line. The AI usage panel shows daily usage and agent hours, split into attended and unattended time.AI adoption levels
Navigara now places each person on one of five AI adoption levels: Curious, Regular, Fluent, Delegator and Orchestrator. A level comes from the person’s AI use over the last 90 days, and Navigara updates it every day. The AI Adoption page shows:- adoption level against delivered work (ETV) for each person or Team
- which people or Teams moved between levels during the range
- AI spend by model
- a “What changed” view that explains each change of the adoption trend
New connections
- Cursor: Navigara now reads the Cursor Enterprise OpenTelemetry export. Cursor usage shows in AI spend, AI usage and AI adoption, next to Claude Code and Codex. Settings → Connections has a Cursor setup wizard.
- YouTrack Cloud: you can now connect with OAuth. The permanent token stays available.
- YouTrack Server: you can now connect a self-hosted YouTrack Server, version 2025.3 or newer.
- Asana Goals: Navigara now reads Asana Goals as objectives.
Also in this release
- You can now exclude a Developer, for example a bot, from all dashboards and reports. Use the Exclude from metrics switch in the Edit dialog. Billing does not change.
- A new Organization setting, Collect prompt text, controls if Navigara keeps the text of AI tool prompts. It is on by default. Find it in Settings → General.
- AI cost, tokens and sessions now show about two minutes after the data arrives.
- Commits now align to GitHub issues that their pull request names in its title, description or branch. Linear sub-issues without a project align through the project of their parent Issue.
- The time picker has a new design. It shows a live preview while you type, warns when a range has no data, and has its own bucket size menu. Each device remembers your last range. The default range is now the last 12 weeks.
- The sidebar has a simpler layout. Settings now opens from the gear at the bottom. “AI budget” is now “AI spend”.
- Sign-in and sign-up are now one page.
- A page with no data yet shows a preview with sample data and one next step.
- AI tool usage history now shows on the AI pages while the import continues.
- Many pages now load faster.
Important changes
Upgrade notes
This release brings objectives to GitHub Issues. It also makes the Delegation score on the AI Adoption page show how often people steer their AI agents.
Highlights
Objectives from GitHub Issues
GitHub Issues now gives you objectives. Navigara reads the sub-issue tree to find the level of each issue. An issue with sub-issues and no parent is an objective. An issue with a parent and sub-issues is a sub-objective. Commits and pull requests align to these objectives.Map GitHub issue types and labels to levels
In the issue tracker setup, you can now map your own GitHub issue types and labels to a level. For example, map an “epic” label to objective. A mapped issue type or label has priority over the position in the sub-issue tree. Issue types and labels that you do not map keep the level from the tree.Steering in the Delegation score
Delegation on the AI Adoption page now has two parts. The first part is agent minutes per prompt. The second part is the share of agent runs that nobody steered. A steer is a prompt during a running agent turn, or a rejected tool call. The Delegation tooltip shows both parts.Important changes
Fixes
- After you disconnect a provider, the Connections page now also updates the list of issue trackers.
Highlights
GitHub Issues
You can now use GitHub Issues as an issue tracker. Turn it on from an existing GitHub connection on the Connections page. Navigara links issues to pull requests with the links that GitHub keeps. A commit that names an issue with its repository, for exampleacme/api#12, links to that issue.Nested teams as a tree
AI budget and Teams now show nested teams as a tree. A parent team includes the people of all its sub-teams. A breadcrumb shows the level and takes you back up.Spend by repository
The AI budget page has a new Spend by repository panel. It shows the AI spend for each repository that the AI tool reported. It follows the page filters and the time range.Also in this release
- The tracker row on the Connections page shows the number of issues that stopped updating because their mapping needs attention.
- YouTrack syncs only the issues that changed between full syncs.
- The Bitbucket token option is now Personal API Token, with a link to the setup guide.
- The session list counts prompts for Codex sessions.
Important changes
Upgrade notes
Highlights
Unassigned in AI budget
On AI budget, you can now filter to the Unassigned team, role, or seniority. Click it to see the developers in it. Charts show the current, incomplete period with hatching.Also in this release
- The dashboard hides Objective alignment until you connect an issue tracker, and hides AI budget until Navigara receives AI tool usage.
- The Team page in Settings has a new design.
- Navigara now records Codex conversations as agent sessions.
Highlights
AI budget
The Tool spend page is now AI budget. One Group by and Split by bar sets the view for the whole page. You can group by team, role, seniority, tool, or model. You can show spend, per active day. Click a value to filter, and share the view with its link.AI spend for teams
The teams list has a new AI spend column. You can sort teams by performance, $/ETV, or AI spend. The teams export includes AI spend.Also in this release
- You can sort developers by AI spend.
Important changes
This release has changes for the Navigara cloud service only. It has no changes for self-managed deployments.
Highlights
Performance breakdown on commits
The commit page now has a Performance breakdown panel. It shows the exact ETV that the adjustments added or removed, and the total change.Agent credit on the developer page
The page of an agent shows the ETV it kept, the ETV it produced, and the ETV credited to people. A new panel lists each person and the rules that credited them.Also in this release
- Self-managed deployments now capture AI tool usage events by default.
Highlights
Agents and attribution rules
You can now mark a developer as an Agent. Add attribution rules to credit the ETV of an agent’s commits to the people it works for. An agent is never a billable seat. Owners and admins manage agents in the Edit developer dialog.Also in this release
- The developers list shows total AI spend under $/ETV.
Highlights
Agent time on the developers list
The developers list now shows agent time and lets you sort by it. The Agent autonomy tile leads with total agent hours.Also in this release
- You can sort developers by $/ETV.
- Issue tracker connections have a Recompute sync mode in Settings → General → Advanced.
- We strengthened the security of the platform.
Highlights
See the commits behind an objective
On the Objective alignment chart, click an objective to see its commits.Clearer repository status
A project with no code, for example a wiki, now shows as empty. When Navigara cannot reach a repository, the list shows the reason.Also in this release
- Azure DevOps connections support both the
visualstudio.comanddev.azure.comaddresses.
Highlights
Developers that need attention
A new Needs attention tab lists developers with no linked provider account or no commit email.Return to your page after you sign in again
When your session ends, you return to the same page after you sign in again.Fixes
- Developer account matching now works for GitLab, Bitbucket, and Azure DevOps.
This release has changes for the Navigara cloud service only. It has no changes for self-managed deployments.
Highlights
Automatic duplicate repository merging
Navigara now detects when two connections point to the same project, for example after a rename, and merges them into one repository. This removes duplicate pull requests and commits from your totals.Revocable sessions and a stronger password policy
You can now see your active sessions and sign other devices out on demand. A new password must be at least 15 characters and not one of the most common passwords. Existing passwords keep working until you change them.Also in this release
- Repository lists now show accurate last activity, and sort by it.
Important changes
Fixes
- Repositories that stayed in a scanning state for a long time now finish processing.
- Adding a discovered repository now starts its analysis instead of doing nothing.
- Retrying analysis for a repository that could not be reached now works correctly.
- Repository branch lists show the actual default branch instead of guessing one.
- GitLab merge request authors and reviewers are now matched to existing developers automatically.
- Pull requests are now included in reports even when their author is added after the pull request.
- Team membership changes now show immediately after you update effective dates.
- Tracker connection status is now accurate. It no longer gets stuck on “Syncing”, and only shows success after the sync completes.
Highlights
Redesigned commit detail page
The commit detail page is easier to scan. Its title now shows the commit subject and short hash. One region now carries every status message for a commit, and the short hash sits next to a button that copies the full hash.See the commits behind an alignment band
On the team alignment chart, click a band to see the commits behind it. The commits open already scoped to that team, alignment state, and time range.Important changes
Fixes
- Pull request syncing now continues past a pull request that no longer exists at the source.
- Organization owners and admins can now start a data recompute themselves, from Settings → General → Advanced.
- API keys can now create repositories through the HTTP API.
Fixes
- Pull request syncing is now faster for Azure DevOps organizations.
- Report scope filters that are too complex now show a clear error immediately.
- The dashboard alignment card no longer appears for organizations that have not set up objectives.
Highlights
Individual developer privacy
Organization owners and admins can turn on individual developer privacy from Manage Organization. When it is on, Navigara hides a developer’s private performance and AI spend data across the platform. Team and organization data stay visible.Redesigned team history editing
Editing a developer’s team history now uses one continuous timeline across all teams, including periods with no team. You review a summary of your changes before you save them.Objectives now show your full delivery picture
The Objective alignment chart on the dashboard and Objectives page now includes work that is not yet linked to an objective, so a team sees its whole delivery history from day one. A new backlog card breaks down open work by flow, class, and how long it has waited.Also in this release
- The developer list now shows a Roadmap alignment column, matching the Team list.
- Manage Developers now suggests likely duplicate developer identities for you to review and merge.
- Redesigned review sheets show pull request cycle time and review coverage on the developer page.
- The Own pull requests tile on the developer page now shows the open pull request count.
- Charts now label the unit on every axis.
- Team settings, including name, description, parent team, and deletion, now live in one place on the Manage Team page.
- Developer management moved under Settings, alongside Manage Organization.
Important changes
Fixes
- Trackpad back and forward swipe gestures now work correctly during navigation.
- Metrics now update correctly after you delete a team.
Highlights
Repository discovery that keeps itself current
Discovery runs in the background, so a search across a large provider account no longer holds the page open. Navigara refreshes the discovered list once a day, and a Re-sync button refreshes it whenever you ask. A repository that is deleted at the provider leaves the list on the next sync.Review cycle diagnostics
Review timing now reads human review and automated review as two separate measures. A monthly Review coverage view plots every merged pull request by merge time and cycle duration, with the bubble sized by reviewed ETV, and you can step through the months. A team view separates the timing of a person’s own pull requests from the value they reviewed for others.Worked toward objectives
A Worked toward panel on a developer’s page lists the objectives their work reached in the selected period. Rows rank by ETV, highest first, and each row shows status, target date, work mix, and that objective’s share of the person’s total. Each row opens the objective.Your performance page, by role
The My performance page shows the view your role allows. Where your account matches no git identity, the page explains why the figures are empty and what to do next, instead of reading as no work.Also in this release
- The Pull requests tiles on a developer’s page group by subject, and show reviewed ETV beside authored value.
- Two surfaces that read “Key-aligned” and “Unaligned” now read Aligned and Untracked, matching every other surface. The bands themselves are unchanged.
Important changes
Fixes
- An issue tracker sync that ends before it finishes now reports that on the connection, so you can start it again.
Highlights
Show the alignment breakdown from Objectives
The Objectives page gains a Show breakdown footer. It opens the alignment table for the period you selected, without leaving the page.One tooltip, and a legend that works
A work category now carries one tooltip rather than several stacked on each other, and the legend shows and hides each series.Important changes
Highlights
Three context checks you configure
Navigara audits the context of a work item as three checks, one for each tier: objective, sub-objective, and issue. Each check carries its own checklist of scored questions and its own free-text instructions, so you decide what a well-described work item means for your organization. A question you do not require leaves the score entirely, and you can turn it back on at any time. All three checks are off by default. Turn them on from Manage checks.Roadmap alignment leads the detail strip
Team, developer, and repository pages now lead with roadmap alignment. The strip reads the same three bands, from the same calculation, as the dashboard card.My performance on one page
The My performance page presents everything on one page, laid out like a developer’s detail page. The two surfaces now read the same way.Also in this release
- The commits list gains an alignment filter, so you can read only aligned, tracked, or untracked work.
- Period summaries use the same work categories as the charts.
Highlights
Work evidence on the commits list
The commits list carries two new columns: Alignment and Pull request / Review. Each column states what Navigara knows, and says so plainly when it knows nothing: “Not available” without an issue tracker, “Unanalyzed” before analysis, “Unknown” when a repository has no connected provider. A missing signal never reads as a negative verdict. Every chart drill-in now lands on this one list, the applied filter shows as a pill you can clear, and the web address is shareable.One place to manage teams, repositories, and developers
Each managed entity now has its own Manage page on one shared layout. Teams keep their structure tree, repositories keep their table, and developers get a new page that holds role, team, dates, and alias emails in one table and one edit dialog. Settings → Aliases now leads there. Search, filters, and page states read the same on every list, and the breadcrumb in the app bar is the one way back.Team structure, rolled up
The team page shows the hierarchy and its member counts, and a parent count includes everyone below it. A team page holds move, new sub-team, add members, the sub-teams, and repository-overlap suggestions for developers who are on no team. The roster is a timeline: one row per person, one bar per period, so a departure and a second period on the team are both visible. You can place many developers on one team in a single action.Objectives lead the dashboard
The dashboard now opens on Objectives (where the work went), followed by the executive summary and the performance trend. The objectives table starts collapsed with a count and a live sort caption, and one control opens it. The teams widget gives its slot to an organization-wide Tool spend card, so AI spend is on the dashboard for the first time.Also in this release
- Reviewed work now names the person whose commit was reviewed. You can group and filter reviewed work by that person.
Important changes
Fixes
- Repository discovery now finishes for an organization with many repositories, however long the search takes.
- Repository discovery always reaches a final state, so Check again stays available.
- A tracker credential that the provider refuses is now withdrawn, and the connection asks you to connect again.
- Adding an alias email now names the developer who already holds that address.
- Setting an issue type to ignored now takes its items out of objective alignment, and lets you run analysis again.
- A repository that cannot finish its analysis now reports that, instead of staying on Scanning.
- An organization with a non-Latin name now gets a usable web address.
Highlights
Commit evidence in the API
The commits endpoint now returns the evidence behind every row: objective alignment, the pull request the commit landed through, whether that pull request was reviewed, and the issues the commit references. An absent value stays absent, so a repository with no connected provider reads as unknown rather than as work with no pull request.One interface on every screen size
Pagination, dialogs, sheets, segmented controls, and dense tables now fit a phone and a tablet. Muted text now meets the WCAG AA contrast level, so it is easier to read. Every page sets its own browser title, every icon-only button carries an accessible name, and the sidebar marks the current page. A page that is still loading no longer shows an empty result, and an empty state now says what to do next.Important changes
Fixes
- When a Git host or an issue tracker host resolves to a private address, the message now names the setting to change.
Highlights
Link a login email to a commit email
A person often signs in with one address and commits with another. You can now add an alias email for a developer by picking an organization member from a searchable list, in Settings → Aliases. Navigara then counts both addresses as one person.Drill into the pull request numbers
The Pull requests panel shows four numbers: pull requests merged, average cycle time, review coverage, and AI spend. Each card now opens the work behind the number. A weekly grid places one bubble per commit, with a searchable list below it. Bubble size is the value of the change, and color is objective alignment.Important changes
Fixes
- Changing the hierarchy mapping of an issue tracker now starts a fresh sync, so the new levels take effect.
- A new API key now works as soon as you create it.
Highlights
One layout for every list page
Developers, Repositories, Teams, Commits, and Checks now share the same anatomy. A title with one action sits on top. A control band holds search, filters, refresh, the column switch, CSV export, and row density. A panel holds the chart and the table. Every numeric cell has a tooltip that defines the metric it shows.One layout for every detail page
Developer, repository, team, and day pages now use the same panels, the same metric strips, and the same loading behavior. Each cell in a metric strip is a tab that switches the chart below it. The repository page adds an average-per-period performance view and a deviation view. Pull request activity gets its own panel with sparklines and axis labels.Important changes
Fixes
- The Jira setup now includes the step that maps issue types to your work hierarchy.
- Pull request sync now completes for Bitbucket repositories that hold no pull requests.
- Self-hosted deployments sync pull requests when the analysis service runs an earlier version.
- Summaries now complete on self-hosted deployments that use a slower language model.
Highlights
Start free, with no credit card
You can now create an organization and analyze up to 1,000 commits in 14 days with no credit card. You add a card when you upgrade. The signup pages state both limits.Five work categories
Navigara now classifies work into features, maintenance, tests, documentation, and fixes. Tests and documentation are first-class categories, so test work no longer counts as features and documentation no longer counts as fixes. Every chart, report, and summary uses the same five categories.Important changes
Fixes
- Work mix cards now show one figure: the share of features.
- You can now create a password account from an invitation link.
- The password sign-in option now follows the setting of your deployment.
Highlights
Sandbox repositories
You can now mark a repository as a sandbox: an experiment, a playground, a hackathon, or a proof of concept. Navigara keeps the work on the repository page and leaves it out of organization and team totals. A chart that names the repository still includes it. The setting is in the repository edit dialog. No repository is a sandbox until you mark it.Provider traffic through your proxy
Navigara now honors the standardHTTP_PROXY, HTTPS_PROXY, and NO_PROXY settings for issue tracker and Git provider traffic. A self-managed deployment behind a corporate egress proxy can reach a cloud issue tracker through the proxy, and an internal Git server directly.Verify what you install
Every published container image now carries a signature, a software bill of materials, and build provenance. Each release publishes the exact image digests, and the deployment guide pins them. You can confirm that you install the same bytes Navigara released.Fixes
- Pull request sync now follows a redirect that stays on your own server, so a renamed or moved repository keeps syncing.
- An issue tracker sync now completes when one item is larger than the size limit.
Highlights
A separate view for managing repositories
The Repositories page now shows analytics only: repository, tags, developers, and performance. A new Manage view holds administration, with five lists: available to add, all, active, disabled, and needs attention. You select rows across pages and act on them together. Adding a repository is a view over the same list, so onboarding and daily management stay the same.Add every selected repository in one step
Navigara now adds a whole selection in one request. Each repository succeeds on its own, and the dialog names any repository it could not add.Full descriptions from your issue tracker
Navigara now reads the full description body of a project and an initiative, not the short summary. For Linear this is the project and initiative content. For Asana this is the project brief. A longer description gives the alignment analysis much more to read.Also in this release
- A team lead now sees a clear message on a page their role does not open, instead of a redirect to the dashboard.
Important changes
Fixes
- Pull request sync now uses the base address you set for a self-managed GitHub or GitLab server.
- Repository health now reflects whether Navigara can reach the repository.
Highlights
Asana matching by task ID
Navigara now reads the ID custom field on your Asana projects. It matches a commit to an Asana task by that readable ID, such asABC-1234. This is the ID your team already writes in commit messages. After you upgrade, run a full re-sync on the Asana connection. Existing tasks then pick up their IDs and align to your objectives.Accept an invitation and sign in on one page
An invitation link now opens the standard sign-in page, with the invitation in context. You accept it with your identity provider: Microsoft, Google, GitHub, or GitLab. The account, the organization membership, and the invitation complete together in one step. Links you already sent keep working.Also in this release
- Sign-in treats an email address the same, whichever letter case you type.
Important changes
Highlights
AI spend for every team and developer
The Teams list and the Developers list gain an AI spend / ETV column. It shows the cost of AI usage for each unit of delivered value, with the total spend below it. A row with no recorded AI usage shows a dash rather than a zero, so an empty figure never reads as free work. Where AI usage cannot be matched to a person, a note under the table states how much spend sits outside the rows.Roadmap alignment on the Teams page
Each team now shows the share of its delivered value that goes to the roadmap. The column uses the same calculation and the same label as the Roadmap alignment card on the dashboard, so both surfaces report the same number. A team with output but nothing on the roadmap shows0%. A team with no output shows a dash.Also in this release
- Self-hosted installations now show a specific message when a license key is absent or cannot be verified, with wording an operator can act on.
Important changes
Fixes
- Sign-in redirects now follow the address you opened, which keeps them correct behind a reverse proxy.
- The root address takes you straight to your dashboard.
Highlights
Map your Asana hierarchy to objectives
The connection wizard now offers Asana a mapping table. You choose which Asana level becomes an Objective, which becomes a Sub-objective, and which is ignored. Organizations that use Asana projects rather than portfolios can now set projects as their objectives and see alignment work end to end. After you save the mapping, run a full re-sync on the Asana connection so existing work picks up the new levels.Comparison periods you can read
The AI Efficiency gauge compares against the same quarter last year when that quarter carries priced AI spend, and against the previous quarter when it does not. Every change now names the period it measured against, instead of always reading as a year-on-year figure.Chart detail that fits the date range
The time picker now caps how fine a bucket you can pick for a long date range, so a chart stays readable. A bucket that is too fine for the selected range is disabled and explains why. Typed input and shared links coarsen the bucket automatically instead of rendering hundreds of bars.Also in this release
- Performance charts name the OSS Index on the plot, shade the area beyond it, and show each bar’s share of it in the tooltip.
- Charts label weeks with their calendar week number.
Important changes
Highlights
Project detail shows where the work comes from
A project inside an objective now shows how much work flows into it, split by issue and by developer. The objective view above it gains the same per-project breakdown. Both views keep the split, share, and delivered value figures you already see on the objectives overview.Board-ready quarterly reports
The quarterly report now states where its numbers come from. A footer shows when the report was generated, the date the data runs through, the applied scope, and the benchmark cohort with its effective date. New print and share actions turn the report into a PDF, with every chart data table included. AI efficiency gains a gauge against last year’s cost per unit of delivered value.Full control of root access on self-hosted installations
Self-hosted operators can now setDISABLE_NAVIGARA_SUPPORT_ACCESS=true to make their own administrator key the only key that can sign in as root. Navigara refuses to start if the setting is enabled without an administrator key, so an installation cannot lock itself out. License verification is unaffected.Important changes
Fixes
- Pages and lists show a loading indicator until their data arrives, instead of a zero or empty state.
- A list emptied by a filter now says that no results match, and keeps the filter controls in place.
Highlights
Team-scoped access for team leads
The team lead role now scopes every view to the teams a person leads. Commits, metrics, objectives, developers, team members, and checks all follow the same scope. Organization-wide objectives stay visible to everyone, so leads keep the full picture of what the organization aims at.Decision-ready executive briefings
Weekly and monthly briefings now have distinct jobs. The weekly briefing covers operations. The monthly briefing covers strategy. Both lead with delivered value, then show the work mix, backlog movement, and how risk changed since the last period. Briefings separate delivery risk from backlog debt, so aging low-priority work no longer reads as a delivery problem. AI spend appears as total cost and as cost per unit of delivered value.Redesigned quarterly report
The quarterly report has a new executive summary. Performance reads against a stable benchmark scale with a target marker, so the gauge means the same thing every quarter. One color palette covers performance, AI, alignment, maintenance, and fixes across every chart. Each change states the period it compares against, and the quarter selector, labels, and links behave consistently.Checks in Beta, with per-organization settings
Checks is now available in production as a Beta feature. A new Checks page in Settings lets you turn each check on or off and tune its thresholds, such as how long a pull request may stay open or wait for review. The occurrence list supports search and paging, and triage follows a familiar filter, group, and resolve pattern.Manage your subscription yourself
Billing settings now include a button that opens a secure payment portal. There you can update your card, view invoices, and cancel. At each renewal, Navigara counts the developers billable for the coming period and bills that count, with no mid-period adjustments. If a payment does not go through, you keep a grace period to recover, and the portal stays reachable throughout.Also in this release
- The accepted company context now appears in Settings, and each briefing records the context version it used.
- The dashboard and the Objectives page share one Objective alignment chart, with stacked bands and a percentage view.
Important changes
Fixes
- The processing status dashboard counts scheduled re-checks separately from work that is still pending.
Highlights
Jira connections with scoped API tokens
You can now connect Jira Cloud with a scoped Atlassian API token. Navigara detects which token type you supply and uses the matching Atlassian endpoint for validation and sync. Classic tokens keep working as before.AI spend is generally available
The AI spend view is now generally available, and its Beta label is gone. Every organization can use it to compare weekly cost against weekly performance.Also in this release
- Empty states tell you whether there is no data yet or whether your filters returned nothing.
- A section that cannot load its data shows an inline message with a retry action.
Fixes
- Charts include benchmark lines when they scale the vertical axis, so the benchmark stays visible.
- Refreshing the Discovered repositories list updates it in one step.
Highlights
Live AI efficiency in quarterly reports
The AI efficiency card in the quarterly report now shows a live figure for spend per unit of output. It clearly shows when there is no AI usage yet, when usage exists but has no cost attached, and when spend exists but no output was delivered.Redesigned executive summary
The dashboard executive summary card has a refreshed look. It includes a clearer loading state, a draft label for briefings covering a period still in progress, and a one-click way to generate a briefing on demand.Also in this release
- In-app setup is now available to everyone, guiding new organizations through connecting their tools.
- The “How is performance evolving” dashboard card was redesigned with clickable views.
- Navigara now measures tool calls per message to give a clearer picture of AI tool usage.
Important changes
Highlights
Self-serve signup and free trials
New organizations can now sign up and start using Navigara on their own, without waiting for manual activation. The setup flow guides you through connecting your code and task management. Each step advances automatically as it completes. If your plan includes a free trial, an in-app banner shows how many days remain, and a reminder email arrives before the trial ends.Executive briefings and on-demand reports
The dashboard now opens with an executive briefing. It leads with your objectives, then shows aligned and untracked work, costs, and notable team activity. Each repository, developer, and team has a redesigned Reports section in the same briefing style, with a period navigator to browse every completed period. You can generate any report on demand with a single click. Briefings also refresh automatically after you connect a task management tool, so new objectives appear right away.Also in this release
- A new usage view shows your plan and how much of your commit-analysis limit you have used, with a trial countdown and a page that lists exactly which developers count toward billing.
- The Checks page now uses one consistent layout and links each finding to its source commit, pull request, or issue.
- Chart legends are now interactive: select an item to show or hide that series.
- Developer aliases let you group several email addresses under one developer profile.
Important changes
Fixes
- The Add Repository dialog now closes automatically after you add repositories, and lists newly discovered repositories as they are found.
- Developer detail pages now list only repositories with activity.
- Objective charts now include periods that have no activity.
- You can now connect Asana and load your workspaces during setup.
Highlights
Redesigned AI spend insights
The AI spend view now matches weekly cost against weekly performance across developers, teams, tools, and models. You can see cost and value side by side. Developers get a dedicated detail view. Rows are fully clickable, and tools share a consistent legend across charts.Light theme for sign-in and onboarding
Sign-in and onboarding now use a clean light theme that matches the rest of the app. Text is clearer, buttons are consistent, and contrast is improved.Switch between quarters in the quarterly report
The quarterly report now includes a quarter selector. You can review recent quarters instead of only the latest one. Every section, including baselines, weekly charts, teams, and objectives, updates to match your selection.Also in this release
- The Key metrics board on the dashboard has a refreshed layout, with progress-colored trend bars and clearer period totals.
- AI spend records now include a cache-aware cost estimate for supported AI coding tools, for a more complete spend picture.
Important changes
Fixes
- You can now edit the host path and token name on an existing token-based connection, instead of only rotating the token.
- The processing status dashboard now refreshes automatically after you retry or dismiss an item.
Highlights
Refreshed dashboard
The dashboard now opens on the last 12 months by default. Team rows show alignment and AI spend alongside performance. Objectives render as shaded area charts, and the top 20% share callout shows what percentage of total performance it represents.Asana task linking by ID
Navigara now recognizes Asana’s human-readable task IDs (for exampleIDP-4355) in commit messages. Commits and Asana tasks line up automatically, not just from the underlying task link.Safer connection setup
The connections page only shows sign-in options that are fully set up on your account. You always land on a working setup step.Important changes
Fixes
- Jira: objective and sub-objective changes now update the alignment status of all related commits, including ones several levels down.
- Jira: on-premises Jira connections now keep separate identities, so two on-premises instances are never mixed together.
- Reported AI tool usage and spend from on-premises analysis is now calculated consistently over time.
Highlights
Connect Asana and Linear
Navigara now connects directly to Asana and Linear with a one-click sign-in flow. For Asana, you can choose which workspace or workspaces to sync, so multi-workspace teams get exactly the projects and tasks they need.Flexible email delivery
Organizations running Navigara on their own infrastructure can now send password reset, invitation, and welcome emails through any standard email provider, using a simple configuration.Important changes
Fixes
- Organization owners, admins, members, and viewers can now access the Connections page from Settings.
Highlights
Dashboard summary and teams
The dashboard summary now shows performance, objective alignment, and AI augmentation as trend lines. Each trend line has a trend chip comparing the start and end of the period. The Developers section is now a Teams section. It shows your top and bottom teams by performance, with a link to each team’s page.Performance chart views for teams and developers
Team and developer pages now have clickable summary cards. Use them to switch the chart between alignment mix, work mix, average member performance, and AI augmentation. AI spend now shows as spend per unit of value delivered, with total spend shown alongside it.Team hierarchy
Sub-teams and parent teams are back on team pages. A breadcrumb shows each team’s place in the hierarchy. A picker lets you assign sub-teams when creating or editing a team.Also in this release
- The Developers list filters are simpler: search by name or email, filter by team, or by probation status.
- Developer detail pages now show the same clickable performance charts available on team pages.
Fixes
- The team edit page now opens.
- The “Top 20% Sum” trend line on the dashboard timeline chart now renders alongside its legend and summary value.
- Chart Y-axes on developer and team pages now scale closer to the actual data, removing excess empty space above the highest value.
Highlights
Find and re-enable disabled repositories
Repositories you disabled from analysis previously disappeared with no way to bring them back. A new Disabled tab next to your repository list shows every disabled repository and lets you re-enable it with one click.A guided setup wizard for task tracking connections
Connecting Jira, Linear, or another task tracker now walks you through picking which projects to sync. It also shows how issue types map to objectives, sub-objectives, and issues. The same wizard supports every provider. Reopening it later shows your saved settings instead of resetting them.Multiple connections per AI tool
You can add more than one connection for the same AI assistant. For example, you can set up separate connections for different backends or departments. Each connection gets its own setup view and can be removed independently.Also in this release
- Team and developer pages now show extra performance and alignment detail cards.
- The commits page highlights pull-request metrics, including merged count, average cycle time, and review coverage, and makes AI-assisted commits easier to spot.
- The AI spend page is reorganized around cost, with a per-developer breakdown, pagination for large teams, and a drill-down view for individual developers.
- The settings page now shows when each API token was last used.
- Reports has graduated from beta and is now generally available.
- The toolbar shows a live indicator while your organization’s data is being processed.
- You can compare a period against its previous period directly in custom metric queries, and build custom calculated measures from existing ones.
Important changes
Fixes
- Navigara now shows a maintenance page instead of signing you out when it briefly cannot reach the server.
- Developer reports now support the quarterly view.
- The commits page keeps your repository filter selected when you also filter by developer.
- The developers page keeps your filters and page position when you change the time range.
- Switching organizations now loads all your organizations the first time you select “Show more”.
Fixes
- Pull request metrics in reports now stay up to date and scoped correctly after team or hierarchy changes.
Highlights
More accurate average-per-developer metric
The average-per-developer figure now sums each week’s average within a period. Larger periods, like a month or quarter, stay proportional to their weeks. A developer who joins partway through a longer period no longer skews the average for everyone else.Consistent numbers across dashboard and reports
The dashboard summary and KPI cards now use the same average-per-developer calculation as quarterly reports. The numbers match everywhere you see them.Important changes
Fixes
- The quarterly report now loads when no team roles are configured, showing a clear message instead of staying on a loading state.
Highlights
AI tool usage and spend, per developer
Navigara now ingests usage telemetry from AI coding tools. It attributes tokens and spend to the developer who generated them. You can track AI adoption and cost person by person, not just organization-wide.Refreshed dashboard overview
The dashboard overview now shows Performance, AI Augmented, and Alignment side by side.Also in this release
- The Repositories page replaces automatic polling with a manual Refresh button, so you control when the list updates.
- Adding a developer to a new team now warns you first if they already belong to another team, since the move ends their current membership.
- Directory sync (SCIM) now supports value-path filtering for Microsoft Entra ID provisioning.
- Metric-backed list views support entity search filters and pagination for faster browsing on large organizations.
Important changes
Fixes
- Editing a repository that was previously stopped now resumes its analysis automatically.
- Developer lists and filters now show the correct team for each developer.
- Team membership lists no longer show duplicate or outdated entries for developers who changed teams.
Fixes
- Team pages now open when the team name includes spaces or accented characters.
- Team membership history no longer shows duplicate entries when someone rejoins the same team on the same day.
- Signing up now returns a clear “already registered” message when the email address is already in use, even when multiple sign-up attempts happen at the same time.
Highlights
Redesigned time picker
The date range picker now uses simple period chips (day, week, month, quarter, year) with quick presets like “Last 12 weeks” or “Last 8 quarters”. A new “complete periods only” toggle lets you exclude the current, still-in-progress period from your view so you are always comparing full periods. The default view is now the last 12 complete weeks.Team membership history
Team detail pages now include a membership history panel showing every developer who has ever been on the team, past and current. Filter by name or email, and open a developer’s role directly from the list.Executive summary gauges
Reports and dashboards now show Performance, Objective alignment, and AI efficiency as clear gauge cards, each with a year-over-year trend indicator. Reports also gained an outcomes section highlighting the quarter’s top objectives with supporting evidence, and a quality and governance summary covering pull request throughput, review coverage, and cycle time.Also in this release
- You can now pause analysis for an individual repository from its settings, without removing the repository.
Important changes
Fixes
- Connecting a tracker or issue integration now shows a clear message when a connection is temporarily rate limited.
- Adding or editing a team member now shows a clear error message if the request cannot be completed.
Highlights
Bulk add team members
You can now add several developers to a team in one step. Search and multi-select developers, or paste a list of email addresses. Preview each person’s current team assignment. Set a shared start date, with a per-row override when needed.Also in this release
- Team pages stay in sync everywhere. Changes made from the Developers page are immediately reflected on the Teams page.
- API key errors are now shown clearly on the Tokens page, with a retry option.
Important changes
Highlights
Clearer issue tracker sync status
The connected issue tracker card now shows “Last synced” as a relative time, with the exact time available on hover. A new Force sync button lets you trigger an immediate refresh instead of waiting for the next scheduled sync.Fixes
- The Add repository button on the Repositories page now appears reliably on every page load.
Highlights
Team membership history
Team pages now show a full history of which team each developer belonged to and when. You can add, edit, or delete historical or active membership periods. Changing a developer’s team now asks for the transition date instead of assuming today.Global command search
Press Cmd/Ctrl+K anywhere to search objectives, teams, developers, repositories, and commits. You can also jump straight to a page.Also in this release
- Organizations can rename themselves from general settings.
- CapEx datapack exports include richer issue metadata and links.
- Organizations can set a default analysis start date, used when a repository does not specify one.
Important changes
Fixes
- The file changes table respects your selected metrics view consistently.
- The commits page keeps the correct total count while paging through results.
- Search fields handle special characters correctly when filtering results.
- Directory sync (SCIM) is more reliable when mapping and syncing user attributes. Revoking a sync token can be repeated safely.
Highlights
Team hierarchy
Teams can now be organized into a tree, with parent teams and sub-teams. Create sub-teams when you create a team, or move a team under a new parent. The teams list shows the full structure with a clear indented view. Metrics for a parent team now include all of its sub-teams, so a leader can see their whole organization at a glance.CapEx report export
The CapEx report now has an Export CSV button. It downloads one row per developer per month for the selected date range, with hours and CapEx percentage. The file opens directly in Excel or Google Sheets.SCIM connection management
Organization admins can now create, list, and revoke SCIM tokens from Settings. This supports identity-provider provisioning.Important changes
Fixes
- Historical summaries now load their status and totals reliably.
- Repository and benchmark pages refresh automatically after you delete, stop, or reset an analysis, so the list reflects the latest state.
- Accepting a team invitation now keeps an active organization selected.
- Analysis results are preserved more reliably if processing is interrupted partway through.
Fixes
- Team management shows clear confirmation and error messages when you create a team, update a team, add members, or remove members.
Highlights
Team visibility on the developer page
The developer detail page now shows a Team card. You can see which team a developer belongs to without switching pages. Organization owners and admins can assign a team directly from this card when one is not set yet.Also in this release
- Sync status for Linear now distinguishes an organization that has never connected Linear from one that connected but has not synced yet.
Important changes
Fixes
- Deleting a team now asks for confirmation before removing it, to help prevent accidental deletions.
- Benchmark reports now show grouped and aggregated results.
Highlights
Repository connection health
Navigara now detects when a repository connection loses access, for example because of expired credentials or an unreachable repository. Affected repositories show a clear status. You can retry the connection with one click to restore analysis.Also in this release
- Team performance metrics automatically refresh when a developer joins or leaves a team.
- Role filters on the Developers and Reports pages now include every matching developer, even for large teams.
Important changes
Fixes
- Objective pages now consistently show performance charts and breakdowns.
- Performance reports show refreshed data with corrected work-classification percentages.
Highlights
Smoother sign-in and organization switching
Signing in with email or a single sign-on provider now takes you straight to your dashboard with the right organization selected. Switching organizations is instant.New AI provider option
Organizations can now connect Navigara to Claude and GPT models through Azure AI Foundry, in addition to the existing provider options.Also in this release
- Access controls now limit repository tag changes, developer identity changes, and developer merges to organization admins.
Fixes
- Commit history analysis now respects each repository’s configured start date. Large, long-running repositories analyze faster and stay within the intended time window.
- Updating a Git access token now automatically refreshes repository discovery. Deleting a token now warns you when active repositories depend on it.
Highlights
Renamed performance unit to Engineering Throughput Value (ETV)
The quarterly performance report now presents your score as Engineering Throughput Value (ETV). This aligns naming across the quarterly report and the performance whitepaper. The report also adds an Activity measure showing how actively engaged your team was each quarter, with clear color bands and a worked example.Refreshed and expanded performance whitepaper
The cross-organization performance whitepaper now shows independent scales per organization. Smaller teams are no longer flattened by larger ones. The whitepaper also adds a cohort breakdown table and a full appendix listing every repository analyzed.Also in this release
- Team, seniority, and role selections on the Developers page stay applied immediately after you make them.
Highlights
Cleaner repository and team pages
Repository and team detail pages now show cleaner, more relevant information. Outdated panels have been removed.Consistent developer counts
Developer counts now match everywhere they appear on a repository page.Important changes
Fixes
- Commit history catches up automatically after an analysis run is interrupted, so no commits are left unprocessed.
Highlights
License expiration banner
Self-hosted organizations now see a banner in the sidebar as their license approaches expiration. It shows a clear countdown, and a follow-up notice during the grace period after expiration. Cloud organizations are not affected.Fixes
- Analysis of very large repositories continues from where it left off if interrupted.
Highlights
Regenerate summaries for your whole organization
You can now regenerate developer summaries for your entire organization from Settings. Previously you could only do this one repository at a time.Fixes
- The discovered repositories page now loads faster and shows accurate result counts while paging through results.
- Pull request data now loads for public repositories outside your connected GitHub organization.
- Newly created teams now appear immediately in every team selector on the page, without needing a refresh.
Highlights
Stronger account security
Navigara now requires stronger passwords when you sign up, reset your password, or accept an invitation. A checklist shows in real time whether your password meets the requirements as you type. Password reset requests are rate-limited, and email addresses are validated before an account is created.Also in this release
- Repository selection during setup supports pagination and filtering by provider.
Fixes
- Page numbers on the commits list stay accurate when navigating between pages.
- The probation period notice disappears automatically once the probation period ends.
Fixes
- Signing in now takes you to your dashboard, even if you also have a personal organization from onboarding.
- Objectives you do not have permission to view now show a clear message instead of a not found page.
Highlights
Faster search across selectors
Repository, developer, and user pickers now search on the server as you type. Selectors open instantly and results update as you search.Sortable, paginated file changes
The file changes table on commit and developer pages supports sorting by complexity, engagement, and performance. Pagination handles commits that touch many files. You can also expand a commit’s file changes directly from the developer page.Streamlined sign-in
Login, invitation, and onboarding pages now show only the sign-in options your organization has configured. Icons and loading states are consistent across all three.Also in this release
- Repository analysis skips example folders, dependency manifests, and changelog files, focusing on your actual source code.
Important changes
Fixes
- Re-inviting someone with an already-pending invitation refreshes their invitation rather than showing an error.
- The edit repository dialog keeps your changes in place while data refreshes in the background.
- Creating a team with a name that is already in use shows a clear error message.
Highlights
Bitbucket Server and Data Center support
Organizations using a self-hosted Bitbucket Server or Data Center instance can now connect it the same way as Bitbucket Cloud. This includes pull request history, comments, and approvals.Licensing for self-hosted deployments
Self-hosted deployments now include a license key system. Administrators can see trial and license status directly in the product.CapEx reports
A new Reports section in the sidebar includes a CapEx report page with chart visualization. This gives finance and engineering leaders a clearer view of capitalized development effort.Also in this release
- Invite links can now be copied directly from the invite dialog and from the pending invitations table.
- Commit lists can now be filtered by developer.
- Connection setup now suggests the correct address format for host fields.
- Accepting a team invitation now supports all available sign-in providers.
Highlights
Manage membership across every organization
Platform administrators can now manage membership across every organization. They can assign the owner or admin role and remove any member. Organization-level admins keep their existing, more limited permissions.Fixes
- The growth metric now displays its color clearly in all cases.
Highlights
Role picker with role-filtered metrics
You can switch between roles, for example engineer or manager, from a global picker. Every page, including dashboards, summaries, and reports, filters its metrics to match the selected role. This makes it easier to see the numbers that matter for a specific perspective.Repository settings and metrics exclusion
Each repository now has a settings panel where you can exclude it from organization-wide metrics. When you turn on exclusion, Navigara recalculates all affected metrics in the background so dashboards and reports stay consistent.Deeper root-cause tracing for fixes
Navigara traces fixes back to the commit that originally introduced the issue being fixed. This works even when the fix and the original change touch different files or functions. It gives more accurate context on developer summaries and commit history.Also in this release
- Added a quarter option to the time-bucket selector, presented as a dropdown.
- Repositories are shown with their owner and repository name instead of a raw URL.
- Added Navigara tools for AI assistants, through MCP, to list repositories and objectives, fetch summaries, and query metrics directly.
Important changes
Fixes
- Invitations can no longer be sent twice to the same address for an organization.
- Settings pages show a clear error and revert your change if a save does not go through.
- The developers list includes all available time-bucket sizes.
Highlights
AI-augmented badge on commits
The commits list and commit detail page now show a badge on commits identified as AI-augmented. This applies when AI detection is enabled for your organization.Architecture overview
The Features page is now Architecture. It has a filter bar for searching by name, category, and team, and a clearer table layout.Also in this release
- Repositories now rank by total performance, so the sort order matches what is shown on the page.
- Search when adding a repository now matches names anywhere, not only at the start, and shows how many results are available.
Fixes
- Editing a repository’s analysis start date to an earlier date now updates its metrics and summaries to match.
- The date picker in Add Repository shows the correct month.
- Search in Add Repository waits briefly before searching, and no longer overwrites your results while a sync is in progress.
- Sync and connection errors in Add Repository are shown so you know what to do next.
Highlights
Azure DevOps support
You can now connect Azure DevOps repositories to Navigara. Sign in with a personal access token or Microsoft Entra ID. Pull requests, reviewers, and approvals sync the same way they do for GitHub and GitLab.Flexible architecture analysis
You can now choose which repositories architecture analysis covers: all of them, or a specific selection. Coverage also improved, so more of your codebase is captured under the right feature area.Also in this release
- Signing in with Google now works reliably when your organization uses a custom frontend address.
- Work attribution across shared directories and files touched by multiple features is now more accurate, reducing miscategorized activity.
Important changes
Fixes
- Browser tabs left open across a deployment now reload automatically instead of showing repeated errors.
- The developer breadcrumb now appears when navigating from a developer’s page to one of their commits.
Fixes
- Repository pages now show all developers who have contributed, including developers first seen on another repository.
- The developer list on a repository page now matches the performance totals shown above it, and uses the same table experience as the team page, including team, seniority, and role filters and column visibility controls.
Fixes
- Improved scheduling so analysis keeps processing smoothly, and other work like summaries and metrics keeps moving during heavy load.
Highlights
Sign in with Microsoft
You can now sign in to Navigara with your Microsoft account. This includes work, school, and personal accounts.Feature contributions chart
The Features page now includes a chart. It shows developer contributions to each feature over time.Also in this release
- The organization switcher now supports search and pagination. This makes it faster to find and switch between organizations.
- The Features page now shows which features depend on each feature. This replaces the previous interface list.
Fixes
- Repository list pagination now uses the correct total count. Page numbers and navigation are accurate.
- The organization role picker now shows each member’s actual role.
Highlights
Custom AI model connections
Navigara now supports OpenAI-compatible AI model endpoints, in addition to the default provider. This lets you connect the model that fits your setup.Role filter on the average performance chart
You can now filter the average member performance chart by role. This makes it easier to compare like with like.Smarter developer matching
Navigara now recognizes when the same developer commits using different email addresses. It keeps them as one developer profile, so activity and performance stay in one place.Also in this release
- The Features area moved after Objectives in the sidebar for a more logical flow.
Important changes
Fixes
- Root cause detection in commit analysis points to the originating commit more consistently.
- Organizations with matching names automatically get a unique address.
- Setup waits for your provider installation to finish before moving to the next onboarding step.
Highlights
Objective detail pages
Every objective now has its own detail page. It shows a stacked area chart of grow, maintenance, and waste effort over time, plus breakdowns by developer and by project. Objectives with no recorded work yet show a clear “work hasn’t started” state instead of an empty chart. You can also open the linked Linear issue directly from the page.Features list
Organizations that turn on architecture analysis in settings now get a Features page. It lists detected architectural features, with expandable details for each feature’s dependencies and entry points.Also in this release
- The objectives chart now has an Absolute / Percent toggle, so you can view effort as raw amounts or as a share of the total.
- Admins can now invite multiple people by email at once from the organization panel.
- Team average performance charts gained a comparison mode toggle.
Fixes
- Accepting an organization invitation now only auto-completes when the logged-in account matches the invited email.
- Accepting an invitation now always switches your active session to the invited organization.
- The team average performance graph animation now displays correctly.
Highlights
Bitbucket Cloud support
You can now connect Bitbucket Cloud repositories alongside GitHub and GitLab. Navigara discovers your Bitbucket repositories, analyzes commits, and tracks pull requests the same way it does for other providers.See how work connects to your objectives
Commits can now be linked to the Issue, sub-objective, and objective they belong to. This is based on your issue tracker hierarchy. It works whether you connected your repositories or your issue tracker first.Redesigned objectives page
The objectives page has a cleaner chart and a performance column with an at-a-glance score. Objectives are now ordered by target date. Hovering a row highlights it on the chart and vice versa. You can filter to objectives active in your selected time range.Also in this release
- Organizations can turn AI-detection columns on or off for their Developers, Repositories, and Teams tables.
- Repository settings now include a “Check for new commits” option to catch up any commits that were missed.
Fixes
- Moving a repository’s analysis start date to an earlier date now analyzes the commits in the newly covered range.
- Reanalyzing a repository after a temporary processing issue no longer skips previously skipped commits.
- The app no longer shows a stale-session error after a period of inactivity.
Highlights
AI-augmented commit detection
Navigara now automatically identifies commits created with the help of AI coding tools. It uses signals like co-author information, commit patterns, and branch names. You will see an “AI %” badge next to performance scores on the developers, repositories, and teams pages, so you can track how much of your team’s work is AI-assisted.Flexible work-category reporting
You can now choose how work is grouped across dashboards, charts, and reports. Pick the classic Grow / Maintenance / Waste view, or a simplified Grow / KTLO view that combines maintenance and waste into one category. Switch anytime from Settings.Reorganized objectives
Objectives can now be folded to show or hide their child projects. This makes it easier to scan a long list of objectives and drill into the ones you care about. Objective detail pages also show more accurate child status counts.Also in this release
- Clicking a developer’s icon now takes you straight to their developer profile.
- The developers page gained filters for role, team, and seniority.
- Developer avatars now use their connected GitHub profile picture where available.
Important changes
Fixes
- The role selector on the team performance graph now works.
- Selected time range and bucket size are preserved when navigating between developer and team detail views.
- Requests that hit a temporary rate limit now retry automatically.
- Objectives show accurate child status counts and improved contrast for status themes.
- Repository links in the commits view now take you to the correct repository page.
Highlights
Objectives from your issue tracker
Navigara can now automatically create and update objectives from your issue tracker’s initiatives. Objectives are matched using the initiative hierarchy. Branch names serve as a fallback when an issue reference is not available, so more of your delivery work is captured without manual setup.More deployment flexibility for self-hosted teams
Organizations running Navigara on their own infrastructure can now run analysis independently from the rest of the platform. They can connect it over a dedicated network endpoint and turn on a dedicated analysis setting per organization. This gives self-hosted teams more control over how and where analysis runs.Move from self-hosted to cloud
Teams running Navigara on their own infrastructure can now migrate their data to the Navigara cloud using a new migration tool.Fixes
- Repository sync now reliably detects updated pull requests.
- Dashboard sections recover gracefully if an error occurs, without affecting the rest of the page.
- Analysis is more stable for repositories that contain non-standard text encoding.
Fixes
- The performance deviation percentage on developer and repository charts now uses the same benchmark baseline as the chart line, so the percentage and the chart always agree.
- Open tabs refresh automatically after a new deployment, so you can keep taking actions without interruption.
Highlights
Guided onboarding
New organizations now go through a guided setup. Tell us about your organization, connect your code source, choose the repositories to analyze, and watch Navigara analyze them in real time. You can navigate between steps using the page URL, and your progress is saved if you refresh.Sign in and connect with GitLab
You can now sign in to Navigara with GitLab, alongside Google and GitHub. Organizations can also connect GitLab during onboarding or from Settings to discover and analyze repositories across their GitLab groups.Linear workspace integration
Connect your Linear workspace from Settings to bring initiatives, projects, and issues into Navigara. Commits are automatically linked to the Linear issues they reference, and objectives are created and kept in sync from your Linear initiatives.Also in this release
- Repository analysis now includes pull requests and merge requests from GitHub and GitLab, linked to the commits that merged them.
- The developers and objectives pages now support keyboard navigation and are easier to use with screen readers.
Fixes
- Pagination controls across list pages now render correctly in both light and dark mode.
- Newly connected repositories now start with the correct default branch.
Fixes
- Invitation links now show the right sign-in or sign-up form based on whether you already have an account.
- Analysis automatically recovers if a connection is interrupted partway through, without losing progress.
Highlights
MCP server for AI assistants
Navigara now offers an MCP (Model Context Protocol) server. AI assistants such as Claude Desktop and Cursor can connect directly using your API key. Assistants can list your teams and pull AI-generated commit summaries and performance scores for a team without leaving the chat.Important changes
Fixes
- Invitation links now open for people who have not signed in yet.
- Team pages now show the Repositories section and the Developer Performance chart.
- The analysis status no longer shows an error badge for a run that a newer, successful run has already replaced.
- Analysis now skips auto-generated helper files from framework tooling, keeping developer metrics focused on real work.
Fixes
- Excluding or including a commit now updates repository metrics right away. Excluded work no longer appears in graphs and reports.
- Repository analysis details, such as author and cost information, are preserved when a later analysis attempt does not complete.
Fixes
- Daily repository syncs now process only new commits since the last analysis, so your data stays up to date faster.
- Large repositories now have more time to complete analysis, improving reliability for repositories with a high volume of history.
Highlights
API tokens for programmatic access
You can now create and manage Navigara API tokens directly from Settings. Generate a token, copy its key once at creation time, and revoke it later when it is no longer needed.Developer avatars
Developers and teams now show profile pictures pulled from GitHub or GitLab. Clean initials appear as a fallback when no picture is available.Also in this release
- Commits can now be sorted by performance on the commits page.
- The performance chart legend shows a tooltip explaining each series.
- The admin panel shows analysis connection status, so operators can see health at a glance.
- The time picker better recognizes preset ranges and remembers your selection across page refreshes.
- You can now filter developers by when they joined and by probation status.
Fixes
- Commits appear in the report sheet view.
- Trend calculations in the dashboard summary section are accurate.
- Minified files are skipped during commit analysis, avoiding noise in results.
- The zero-day index only applies to developers, as intended.
- Session handling has been made more resilient, reducing unexpected sign-outs.
Fixes
- You can now add a personal access token for a GitHub Enterprise instance. If adding the token fails, you now see a clear message instead of the dialog closing silently.
Highlights
GitHub Enterprise support for tokens
Navigara now validates access tokens against GitHub Enterprise instances, not just github.com. If your organization runs its own GitHub Enterprise deployment, you can add and use tokens for it directly.Also in this release
- The Add token dialog now shows a clear, specific message when a token cannot be validated.
Important changes
Highlights
Simplified connections settings
The Tokens page is now part of Connections. Each provider (GitHub, GitLab, Bitbucket) shows as a collapsible card with its token count and an expandable token list. You manage every connection from one place.Repositories contribution on team detail
Team detail pages now include a repositories contribution section. It shows which repositories a team’s developers are actively contributing to.Also in this release
- Filters show a clearer selected state and support multiple active filters at once.
- Your selected time range and bucket size are preserved as you navigate between pages.
- Git tokens let you specify the provider explicitly, improving support for self-hosted GitHub Enterprise, GitLab, and Bitbucket instances.
Important changes
Fixes
- Team charts load team members directly, so team performance data displays reliably.
Highlights
Teams
You can now group developers into Teams and view their combined performance over time. Each team gets its own detail page with a performance chart, member search, and an AI-generated summary of the team’s work. You can create, edit, and configure teams from Organization Settings.Developer detail redesign
The developer detail page now shows a repository-by-repository breakdown of performance. This makes it easier to see where a developer’s work is happening. Charts across the product now share one consistent tooltip style, so you can compare grow, maintenance, and waste values at a glance.Also in this release
- Organization Settings includes a new option to refresh your data on demand.
Fixes
- The developers table on the dashboard updates when you change the time range.
- The performance graph on the team detail page displays reliably.
Highlights
Redesigned dashboard, repository, and developer views
The dashboard, repository detail page, and repositories list page have a new look and feel, with clearer layouts. The repositories list also has a new performance chart. Developer list tables on the dashboard are redesigned for easier scanning, and graph line tooltips are now clearer and easier to read.Fixes
- Developer avatar initials now display when a name contains non-letter characters.
- Commit history for developers now includes all of their associated email addresses.
Highlights
Faster navigation to developer detail
Click a point on a developer’s line graph, or a time period on the developer detail page, to jump straight to the matching report. You can also sort commits inside the report pop-up window.Fixes
- Developers who commit using GitHub’s private “noreply” email address are now matched to their existing account.
- Repository sync with a GitLab on-premises server now completes when the server URL is entered without a protocol prefix.
Fixes
- The retry failed button in the work queue now retries only the failed items. You can recover from errors without rescanning everything else.
Highlights
Connect repositories with a GitHub App
You can now connect your GitHub organization using a GitHub App instead of managing personal access tokens. This also improves developer matching by recognizing multiple email addresses, including no-reply and alias addresses, for the same developer.Redesigned developer list
The developers list has a refreshed look. It includes a new performance graph, clearer table columns, simplified filters, and a new pagination control with a page size selector.Also in this release
- You can now edit a developer’s joining date, set a probation period, and filter the developer list by probation status.
- The performance graph and its deviation stat card have a cleaner, easier-to-read design.
Important changes
Fixes
- Cloning private repositories connected through a GitHub App now works reliably.
- Charts display dates consistently regardless of your time zone.
- Week numbers on charts that start on Sunday now display correctly.
- Repository data access is now scoped to the correct organization.
Fixes
- The repository benchmark selector no longer shows an option for a day with no activity.
- Performance summaries generate only for fully completed periods. This gives you more consistent results.
Highlights
Zero-day index view
Charts now offer a Zero-day index visualization mode alongside the Organization average. It shows upper and lower bands around the benchmark average, so you can see how performance spreads over time. The legend and tooltip show performance, average, and spread.Custom benchmarks in charts
You can now select a custom benchmark from the chart dropdown menu, in addition to Organization average and Zero-day index. The average performance deviation card updates its name to match your selected benchmark.Also in this release
- The Zero-day index option is now available directly from the repositories dropdown menu.
Fixes
- Repository sync now completes reliably, even when some items previously required a retry.
Highlights
Faster commit history for large repositories
Pages that list commits and developer activity now load significantly faster for organizations with large histories. This holds even with tens of thousands of commits.Important changes
Fixes
- Large result sets on the commits list now keep filtering and pagination consistent across pages.
Fixes
- Commit detail pages now load reliably in repositories with a large commit history.
- When you merge or split a developer’s email addresses, their commit history, contribution graph, and metrics update automatically to match.
Fixes
- The developer page now updates after you type a custom date into the time filter.
Fixes
- The navigation sidebar now collapses and expands smoothly, and the toolbar stays aligned with it.
Highlights
Exclude commits from metrics
You can now exclude individual commits from performance metrics, with a reason you choose. Excluded commits are marked on the commit page and are left out of all metrics calculations.Important changes
Fixes
- Repositories pages linked directly with a time range in the URL now load and filter correctly.
- Repositories hosted on GitLab Enterprise now detect the default branch reliably, even when it is not included in the initial project listing.
Fixes
- Summary reports now filter correctly by schedule type, scope, and period.
- The file list dropdown in commit details now responds correctly when you select an item.
Highlights
Team member management
Organization owners and admins can change a member’s role, remove a member, or cancel a pending invitation. Each action has a confirmation step to prevent accidental changes. The owner role is shown as a fixed badge. You can no longer remove yourself or change your own role by accident.Also in this release
- The developers table shows email addresses in a tooltip when you hover over a developer’s name, keeping the table itself cleaner.
Important changes
Fixes
- Repositories with no commits in the selected period show a clear “No commits” status.
- Clicking the dependency arrow in the file changes table keeps your session active.
- Period summaries update in place and show when they were last generated.
Highlights
Configurable periodic summaries
Navigara now generates periodic summaries automatically. You get a regular, up-to-date view of developer and repository performance without asking for one.Redesigned performance graphs
Repository and developer performance graphs now let you switch between relative and absolute views. You can compare against the organization average from a dropdown menu.Visibility into skipped files and commits
Analysis now shows which files and commits were filtered out, for example lockfiles or generated code. A clear explanation shows what is included in your metrics.Also in this release
- A quick-access arrow on the repository developers list takes you straight to each developer’s page.
Important changes
Fixes
- The developers page loads for organizations with more than 1,000 developers.
- You can assign a developer to a team in organizations with more than 1,000 developers.
- Seniority level displays for developers.
- Benchmark charts aggregate data based on the selected time bucket.
Highlights
Custom benchmarks
You can now save groups of developers or repositories to compare against. Choose average, median, or another percentile for how the group is aggregated, so comparisons match the way your team works.Fixes
- Newly connected repositories now show complete commit metrics from the start of analysis.
Highlights
Flexible time aggregation for commit activity
The Commits view now lets you group commit activity by day, week, or month. Zoom in for recent detail or zoom out for a longer trend.Probation tracking for developers
You can now record a developer’s joining date and end of probation date. This makes it easier to track ramp-up periods alongside performance history.Also in this release
- Developer day detail pages now show the developer’s name in the breadcrumb.
- The global time picker now accepts month ranges that span into the next year, for example “Dec 2025 - Jan 2026”.
Fixes
- Repository pages keep open dropdown menus open while a repository analysis is in progress.
- Performance and dashboard charts show date labels clearly, without overlapping text.
- Selecting a seniority level on the developer filters no longer clears the selected team, and vice versa.
Highlights
Clearer, more factual period summaries
Period summaries describe what happened in plain, factual language. Commit and pull request references in a summary are clickable links, and key terms are highlighted for faster scanning.Redesigned time picker
The time picker supports typing values directly and selecting custom ranges, with a fixed default time. This makes it faster to pick the exact period you want to view.Also in this release
- API tokens on the tokens settings page show their expiration date, with clear badges for tokens that are expired or expiring soon.
Fixes
- The invitation login page displays correctly.
- Bucket size selection in team and project charts applies correctly.
- Token expiration dates from GitHub are parsed correctly regardless of timezone format.
Highlights
PHP analysis
Navigara now analyzes PHP repositories with the same depth as other supported languages. This includes accurate symbol detection and reference finding across your PHP codebase.Also in this release
- List pages across Navigara (developers, teams, projects, repositories) now consistently apply your selected time range.
Important changes
Fixes
- Metrics now stay consistent when the same commit affects multiple repositories.
- The time period selector now works after refreshing the page.
Navigara is now available.
Highlights
AI-powered performance summaries
Navigara generates AI-powered summaries for Repositories and Developers. Each summary highlights key strengths, concerns, and recommendations based on recent activity. You can regenerate a summary at any time as new work comes in.Teams and projects
You can group Developers into Teams and Repositories into Projects. Each Team and Project gets its own detail view with a performance graph and a table of its members. This lets you track work at the level that matters to you.Commit knowledge graph
Commit detail pages include an interactive graph. It shows how a commit’s changes connect to the rest of your codebase. This makes it easier to understand the scope and impact of a change at a glance.Also in this release
- A global time picker lets you choose custom date ranges and bucket sizes across dashboards.
- Members can switch between Organizations they belong to directly from the sidebar.
- Dashboards, Repositories, and Developer pages have clearer performance charts and benchmark visualizations.
- Organization owners can invite members, manage Repository tokens, and reset passwords.
- Repositories can be tagged and automatically grouped by Project.
Fixes
- Time range selections carry through to Team, Project, and Developer detail pages.
- The Repository detail page shows the combined score for each developer.
- Charts show only bars that reflect data for the selected range.
- Developer emails are matched consistently regardless of capitalization, so contributions group correctly.