We tracked Cursor for 30 days using AI. Here's every signal we caught.

Cursor hit $100M ARR faster than almost any developer tool in history. If you're building in the AI editor space — or adjacent to it — you need to know what they're actually building, not what their marketing page says.

We pointed Argus at Cursor's GitHub, job board, news coverage, website, and patent filings for 30 days. Here's exactly what we found, in the order we found it.

Week 1: The enterprise pivot is real

The first signal that fired was a GitHub commit pattern. Argus flagged a new branch in the cursor-so/cursor repo: enterprise-auth. Within 72 hours, 12 commits landed — SAML provider support, org-wide session management, and audit log endpoints. This wasn't a spike in activity. It was a sustained, deliberate build.

Two days later, two Enterprise Account Executive roles appeared on their jobs page — one in New York, one in London. The JDs asked for experience closing six-figure SaaS contracts. Cursor has never had an enterprise sales team. They do now.

Week 2: Pricing page changes overnight

On day 11, Argus flagged a change on cursor.so/pricing. A new "Teams" tier appeared — $40/seat/mo, with admin controls, usage dashboards, and centralized billing. This wasn't announced on Twitter. There was no blog post. The page just changed.

This is exactly the kind of signal that's invisible unless you're watching. By the time it shows up in a newsletter, your sales team has already missed the pricing intelligence window.

Week 3: A patent nobody noticed

On day 19, Argus pulled a USPTO patent application filed by Anysphere Inc. (Cursor's parent): "System and method for context-aware code completion using retrieval-augmented generation with repository-level embeddings." This is describing their codebase indexing approach — the thing that makes Cursor feel like it "understands" your whole repo, not just the open file.

They're protecting the core IP. That's a signal about where they think the moat is.

Week 4: The GitHub Copilot displacement signal

In the last week, Argus picked up a pattern in G2 reviews for GitHub Copilot — 22 reviews this month mentioned switching to Cursor as the reason for leaving. The phrasing was consistent enough to cluster: "switched to Cursor," "moved our team to Cursor," "Cursor is just better now."

This is displacement in progress. And it's measurable before any analyst publishes a report about it.

What this tells you

Cursor's 30-day signal profile is unusually coherent. Enterprise auth → enterprise sales hires → Teams pricing tier. That's not three separate decisions. That's one deliberate motion executed over 30 days.

If you're GitHub, you now know Copilot's displacement is accelerating at the team level, not just individual devs. If you're Zed or Windsurf, you know the window to differentiate on non-enterprise is narrowing fast.

"The best competitive intelligence isn't what your competitor says — it's what they're building before they say anything."

None of these signals were secret. They were all public — GitHub commits, job postings, patent applications, review sites. The problem is that collecting and connecting them manually would take a researcher days. Argus does it continuously, automatically, and flags what matters.