AI Engineering Trends

Jellyfish measures Autonomous Agent Activity as the percentage of pull requests that are autonomously created or generated by AI agents. A PR qualifies as agent-generated if it was opened by a user identity that is an agent, or if it contains commits where the committing user is an agent. This metric tracks the emerging frontier of AI adoption, where AI isn’t just assisting engineers, but independently shipping work.

Jellyfish measures Model Usage as the share of each tool’s active users who used a given model, reported separately for Claude Code, GitHub Copilot, and Cursor. It is calculated from the models invoked by each developer each week. Users can appear under multiple models. 

By analyzing the top three models by share of users each month, we measure how quickly engineering organizations absorb new model generations. As each new release ramps, its predecessor fades, so the top models can change from month to month.

Jellyfish measures open weight model usage as the fraction of engineers who selected an open-weight model (e.g. Kimi, GLM, DeepSeek, Qwen) in a given week, alongside which model families lead among the companies using them. It is calculated from per-event model selections, classified by model family.

As software organizations mature in their AI transformation, their AI budgets are growing correspondingly. Teams are employing a number of strategies to manage that spend, including leveraging open-weight models and routing usage through model routers and gateways. This behavior remains concentrated in the most AI-mature companies, with under 2% of companies employing open-weight models or routers regularly, and August held the post-surge highs: 0.7% of weekly engineers used an open-weight model (up from about 0.2% in March), with Kimi at 68% of open-model engineers.

Jellyfish measures agentic-merged PRs as the fraction of a company’s merged pull requests whose only review activity, whether comments or formal reviews, came from AI tools, with no human review input before merge. It is calculated per company over merged PRs opened by humans or AI agents. The data below shows the distribution across companies by percentile.

This metric captures the sharpest edge of AI adoption: work that ships with AI as the only reviewer. While the median company agentic-merges just 0.6% of its PRs, lead adopters of this workflow merge 9%+ of their PRs with no human review.

Jellyfish measures invocations of agent skills in Cursor and categorizes them by use-case using an LLM. The data above shows the distribution of skill categories invoked by engineers within Cursor in the past month. 

This captures the current state of AI development practices and the specific workflow steps engineers are augmenting within the AIDLC.

Jellyfish measures AI Spend as the cost of AI coding tool usage per developer per week, reported for Claude Code and Cursor. It is calculated by summing each developer’s reported usage costs each week, shown as a distribution across developers.

This metric turns token consumption into budget terms, and the distribution matters as much as the level: spend is highly concentrated, with the heaviest users consuming an order of magnitude more than the median developer. For leaders, it anchors the ROI question by showing what the organization actually pays per developer for the productivity signals measured alongside it.

Jellyfish measures Token Consumption as the total number of tokens consumed by a developer while using Claude Code and Cursor. It is calculated by summing all tokens as reported from Claude Code, and Cursor for each developer each week. This metric tracks usage of those tools and the potential budgetary implications of increased AI maturity.

Jellyfish measures Productivity by Token Consumption at the developer-week level. Each developer-week is ranked by its AI token consumption (Cursor + Claude Code) and grouped into 50 equal-sized bins, each 2 percentiles wide. Each point is one bin’s average tokens against its average merged PRs, and the line is a curve fitted to those points. 

This metric addresses the core ROI question of whether consumption converts into output. Throughput rises with token consumption, but not linearly: gains taper off at the high end. As with all comparisons in this report, the relationship is correlational rather than causal.

Jellyfish measures Access Percentage as the fraction of engineers at a company who have a license to an AI coding tool. As a baseline adoption metric, Access Percentage establishes the foundation for deeper analysis, including how frequently and deeply AI tools are integrated into developer workflows.

Jellyfish measures Weekly Active Users (WAU) percentage as the fraction of engineers at a company who actively use an AI coding tool in a given week. This metric captures the frequency of adoption, showing whether engineers are actually integrating AI tools into their regular workflows.

Jellyfish measures AI Code Percentage as the fraction of a company’s shipped code that is AI-assisted. It is calculated as the fraction of merged code additions that were AI-assisted, relative to all code additions in merged pull requests for each company. 

This metric moves beyond tool usage frequency to capture the actual depth of AI’s impact on codebases and coding work.