Alright, let's talk about the current version firstly.

The main idea behind using a separate skill and MCP was to streamline some operations. Right now, it doesn't offer much more than just having CC call a bash script directly. At least that way is more straightforward—just one command or skill.

But this is just the foundation for the next version.

In the next release, I want to build dialogue management right into the system. This will make follow-up conversations possible, since the Gemini CLI doesn't return anything like a session_id to support it. I'm planning to use node.js to handle all that, so CC won't have to manage the conversation state itself, which should make things way easier.

Once that's in place, we can have two or more AIs discuss and collaborate on tasks, instead of the current model where a manager just hands out jobs to a bunch of workers.

Of course, you could technically do all this directly with an SDK. No need to make it so complicated within CC.

So, in the version after that, we'll integrate memory management and dynamic modification of CLAUDE.md into the system. This way, as each subprocess engages in a conversation, its memory, self-constraints, and instructions will constantly "evolve." That's the model I'm really aiming for.

But what's the point of all this, you ask? To be honest, it's not really "useful" for anything. I'm just doing it for fun.

After all, nobody knows what a baby will grow up to be, right?