Choosing Your AI Assistant: Universal Support

Connecting Tools You Already Use

Estimated reading: 0 minutes 7 views

If you’re already using an AI assistant for coding, you can connect it to GameCatalyst without changing your workflow.

For VS Code users:

If you use GitHub Copilot, Cline, or Roo Code in VS Code, you’re already familiar with AI-assisted coding. GameCatalyst extends that experience into Unity. You can:

Keep using VS Code for script editing
Use your AI assistant to create Unity objects and scenes
See changes appear in Unity in real time
Switch between code editing and Unity work seamlessly

For JetBrains users:

If you use Rider (Unity’s recommended IDE), JetBrains AI integrates directly. You can:

Write C# code with AI assistance in Rider
Use GameCatalyst commands to test code in Unity immediately
Debug with Rider while AI manages Unity scene setup

For Claude Desktop users:

Claude Desktop is a standalone application. You can:

Use Claude for general coding questions and architecture advice

Use GameCatalyst commands to implement solutions directly in Unity

Keep Claude open alongside Unity for continuous assistance

For ChatGPT users:

ChatGPT runs in your browser. You can:

Use ChatGPT’s web interface for brainstorming and planning
Enable Developer Mode and connect to GameCatalyst via Web Relay
Execute commands in Unity without leaving your browser

The key insight:

GameCatalyst doesn’t replace your existing AI workflow. It enhances it by giving your AI assistant the ability to actually do things in Unity instead of just suggesting them.

You keep using the tools you know. GameCatalyst just makes them more powerful.

For command-line users:

If you use Claude Code (Anthropic’s CLI tool), Gemini CLI (Google’s command-line AI), or Amazon Q Developer, GameCatalyst works through STDIO just like desktop clients. The Client Conductor Configurator generates the correct command or configuration for each tool. Claude Code uses a simple CLI command to add GameCatalyst as an MCP server. Gemini CLI and Amazon Q Developer use their respective configuration files.

Seamless transitions:

You can switch between writing code in your IDE and asking your AI to make changes in Unity without any context switching penalty. Your AI client stays connected to GameCatalyst in the background. When you need something done in Unity, just ask. When you want to write code manually, just open your editor. The two workflows coexist naturally.