Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
← All Cursor issues

This week in Cursor · Jun 29, 2026

Cursor AI June 29: Origin Agent-First Git Platform and 1.5-Trillion-Parameter Frontier Model Confirmed, Continue Acquisition, Code Custody Stakes Rise

Get the next issue in your inbox. Weekly · Free

unsubscribe anytime.

TLDR;

Following SpaceX's acquisition of Cursor at compile 2026 last week, this week confirmed the products behind the deal. Cursor Origin is a new agent-first git platform designed as a GitHub rival - your code is stored with Cursor, not Microsoft, and a SpaceX-trained model operates on it natively. Cursor also disclosed it trained its first frontier coding model from scratch on xAI's Colossus cluster: 1.5 trillion parameters across 100,000 GPUs. Separately, Cursor acquired Continue, the open-source GitHub Copilot alternative with a large VS Code and JetBrains user base, folding its community and tooling into the Cursor platform. These moves together position Cursor as a vertically integrated coding stack - IDE, git host, and proprietary model. For developers on Microsoft GitHub or using Continue as a standalone open-source tool, now is the time to assess code custody terms and make a deliberate platform choice.

Developer Tools & Community

Cursor Origin Launches: Agent-First GitHub Rival and 1.5-Trillion-Parameter Frontier Model Trained on xAI Colossus

  • Confirmed June 24, Cursor Origin is a new agent-first git platform rivaling GitHub - your code stays in Cursor's custody, not Microsoft's.
  • Simultaneously, Cursor disclosed it trained its first frontier coding model from scratch on xAI's Colossus cluster: 1.5 trillion parameters across 100,000 GPUs, with an initial variant trained on SpaceX's private codebase.
  • That SpaceX model now powers Origin's agent workflows, and Cursor frames code custody - who owns write access, storage, and training rights - as a first-class product differentiator.

Editor’s read: Cursor Origin is a real GitHub challenge, not marketing - but the code custody trade-off is the key question to resolve before migrating. Read Cursor's data terms carefully: who trains on your code, and what opt-outs exist.

Cursor AI Acquires Continue: Open-Source GitHub Copilot Alternative Joins Cursor Platform

  • Reported June 22 by The New Stack, Cursor has acquired Continue, the open-source GitHub Copilot alternative used by developers in VS Code and JetBrains.
  • Continue's developer community and tooling will be integrated into the Cursor platform, extending Cursor's reach beyond developers who already use the Cursor IDE.

Editor’s read: If you use Continue specifically because it is open-source and IDE-agnostic, note that its roadmap is now controlled by Cursor, a private company recently acquired by SpaceX. Evaluate whether that changes your dependency trust model.

Community & Independent Developers

Cursor Composer Agent Problem: Autonomous Tasks Creating Pull Requests Too Large or Opaque for Human Review

  • A June 28 essay by Jon Udell addresses the growing workflow breakdown where AI coding agents including Cursor's Composer generate PRs too large, complex, or opaque for meaningful human review, and proposes concrete team policies for defining PR size limits and oversight gates before autonomous agent commits.

Editor’s read: With Origin integrating agentic write access into git, the unreviewable PR risk compounds - define your review criteria before giving Cursor agents write access to Origin repos.

Action Items

Immediate

  • Read Cursor's data terms for Origin before migrating any repositories from GitHub - specifically: who has training rights on your code, and what opt-outs exist
  • If you use Continue standalone: evaluate whether Cursor's acquisition changes your open-source dependency assumptions
  • Use the June 28 pricing comparison to verify Cursor's current tier value against alternatives at your usage level

By July 6

  • Evaluate whether Cursor Origin's code custody model is preferable to GitHub for your team given the SpaceX ownership structure
  • If your team uses Continue in JetBrains or VS Code: plan whether to stay on the open-source fork or migrate to Cursor's integrated version
  • Define PR size and review criteria gates before allowing Cursor Composer agents to commit autonomously to any production-adjacent repo
  • Test Cursor's new SpaceX-trained frontier model on your most representative coding tasks if you get access - benchmark it against claude-opus-4-8 and GPT variants you currently use

All Resources

Every Monday morning

This week in Cursor

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.