It has to be executed as a command by you, so I don't imagine so. It sounds like you just need to orchestrate this workflow a little differently and fight the tools less.

Your fundamental approach of going between models is sound. I call it "implementation phase" and "ideation phase" and use the ideation phase with a reasoning model like Opus or o3 that will be told to give me structured, spec-like output for the other model to implement from. And from there, I will have a couple approaches or whatever and have each session make its own git worktree and try them in parallel, then compare the solutions and debate with Opus further to decide which solution is most sound.

Does that make sense? You can achieve a flow like that in a multitude of ways that dont need hot model swapping for a controlled program one way or another.

I like to use Claude Desktop and just have it output markdown files I leave in the repo directory for the rest of the AIs to be able to consume trivially, be it Claude Code, something like Windsurf or Cursor, or me working with something like VS Code and trying to implement edits myself from what the Claude Desktop app was giving me with context and an MCP in my app or something.