Wing 12, Claude Code, and MCP support

retag add tags

Hi,

I'm a long-time Wing user with an active support subscription, and I have a question about the direction taken with AI integration in Wing 12.

I noticed that the new agentic features are centered around Claude Code, while the previous multi-provider AI integrations are now considered legacy features.

I understand the practical reasons for focusing deeply on one coding agent rather than maintaining several different agent integrations. However, I personally don't use Claude anymore after having tested it extensively, so I'm wondering what this means for Wing going forward.

In particular:

Is the focus on Claude Code a pragmatic choice for Wing 12, or do you expect Claude Code to remain the only supported agent for the foreseeable future?
Since Wing exposes its code intelligence, debugger, testing, and VCS capabilities through MCP servers, are those MCP servers technically usable by other MCP-compatible clients/agents?
Do you have any plans to support other coding agents in the future, for example OpenAI Codex or Gemini CLI, while reusing the same Wing MCP infrastructure?

I'm mainly trying to understand whether the Claude Code dependency is intrinsic to Wing's new architecture, or primarily a product/integration decision at this stage.

Thanks! Bruno

kerouanton

asked 2026-08-17 05:44:09 +0000

edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

The shift in focus was from old style single-LLM-query AI to support for AI agents. You can call Claude's models from the old now-legacy AI integration in Wing (which can still be enabled in Wing 12 if wanted) but that's completely different than using Claude Code.

Agentic development is such a quantum leap that we shifted to that model, for now just with Claude Code but we'll certainly look at supporting other providers of AI agents in the future.

You should be able to point other AI agents to our MCP servers and probably even tell them to read the contents of the .claude directory Wing writes when you enable Claude Code for a Wing project. If the agent also has a TUI then you could run it from the OS Commands tool, which now has true Pseudo TTY support.

So it more or less might just work, but not the Tasks tool, which does currently assume Claude Code.

I can't predict time frames on any of this, but hopefully that gives you an idea of where we're headed.

4.3k

Wingware Support

answered 2026-08-17 19:50:16 +0000

edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer

Wing 12, Claude Code, and MCP support edit

Comments

1 Answer

Comments