Skip to content
Multi-IDE Support for Unity cover

Side projects / Multi-IDE Support for Unity

Multi-IDE Support for Unity

I turned a Unity 6.6 upgrade blocker into an open-source tool for restoring an AI-native IDE workflow.

2026
UnityC#IDE IntegrationCursorWindsurfKiro

Overview

When I upgraded my projects to Unity 6.6, I lost an important part of my workflow: opening, editing, and debugging code from the AI-native IDEs I already used. I did not want to choose between upgrading the engine and keeping a workflow that helps me iterate faster, so I turned that blocker into a maintained open-source tool.

The result brings Cursor, Windsurf, Kiro, and Antigravity IDE back into Unity’s editor workflow while keeping projects ready to work with. It started as a problem I needed to solve for myself, but is designed to remove the same friction for other developers.

From an upgrade limitation to reusable tooling

This is the kind of problem I enjoy solving: a platform upgrade changes an established workflow, a key tool no longer fits, and the solution must coexist with the existing ecosystem without making teams rebuild their projects.

I worked from an existing Unity integration to restore support for modern editors, preserve C# project generation, and maintain compatibility with the current engine. The challenge was not simply launching an external application: it was retaining a dependable developer experience around Unity, solution files, and IntelliSense.

My contribution

  • Identified a real pipeline regression during a Unity 6.6 migration and turned it into a published solution.
  • Extended and maintain a C# tooling codebase that connects Unity with external development tools.
  • Solved compatibility concerns around IDE discovery, editor selection, and the project generation required for IntelliSense.
  • Turned a personal solution into an installable, maintainable package for the Unity community.

What it demonstrates

Beyond Unity itself, this project reflects how I work: I understand a developer’s end-to-end workflow, find where it breaks, enter an existing codebase with intent, and ship a solution others can adopt. It is developer tooling, software maintenance, and developer experience applied to a real need.

Stack

  • Unity 6.6, C#, and Unity’s package system
  • IDE integration, .sln / .csproj generation, and IntelliSense
  • Cursor, Windsurf, Kiro, and Antigravity IDE