I’ve always loved Batman with his tools and widgets. I was sold when Knight Rider had his self driving car Kit and remote control watch to talk to it. Suddenly I was in front of this sci-fi technology with all these possibilities and it was last April. I started to create my toolset for agentic development and now I can create Power Platform solutions, Copilot Studio agents and even Android applications with couple prompts even when driving a car. I’m planning buying smart watch and creating there my own application, so I could talk to my production pipeline even from my watch.
It is much easier to create pro code with agentic means than Power Platform. I’ve had had much struggles when authenticating to different tools but amazingly I was always tried the right time when there was a way to do something. I started using Azure virtual server since our company did not allow installing Claude into my work windows laptop. And turned out to be the better solution, since now it does not have access to my laptop and personal files, it is running 24/7 in tmux window with Claude remote and I can access it with mobile when my laptop is turned off.
The future is here, so is the burn out
This all did not come for free. Before summer holidays I was with my AI-Claude-honeymoon and got depression symptoms. No wonder when I was doing work and developing my toolset all the time I was awake. I tried everything, even creating children’s cartoons with Higgsfield MCP attached to my Claude – The Quantum Whiskers. But I also learned quite much. Where I was good and where not. I’ve always been a programmer, this took me back towards pro code but the difference was, that I did not need to code, just guide the coding agent.
Forming my orchestration
I was using quite much only one agentic window in the beginning, just connecting trough VS Code SSH extension to my Ubuntu server in Azure. I thought that I need to run my laptop, so that I can connect Claude remote control. Then I discussed with my agent. It told me about tmux, I started using it. Then I saw someone’s post that Claude sessions can talk to each other. What sessions, I have only one. Then suddenly I had multiple and first they were operator and Robin and Batman. Quite soon I chose the name “The Musketeers” and formed these four core sessions that run the show with couple physical machines on the side.
Athos, Porthos and Aramis are running at the moment with Claude Opus 5.5 and high effort doing the basic tasks. D’Artagnan is running Fable 5.1 the highest language model for challenging planning. I have besides that old iMac from 2011 running now with Xubuntu doing the work that requires UI and is called Platon. Besides that I have Cardinal that is old Android phone doing the stuff where API cannot reach. When driving a car and wanted two way discussion, I created app called Kingdom of Heaven so I can really discuss with my agent. In this mode Athos is there for me and driving all work for other sessions. Normally my Musketeers asks me permission if they could use other sessions or start temporary ones. Scheduled tasks are run partly with headless sessions – I will write another blog for best practices about orchestrating Claude Code sessions and tasks.
Meet the Musketeers
Power Platform
This was not easy, since sometimes you need to use pac cli for governance operations, sometimes you need Azure cli login for other stuff, and then Copilot Studio plugin for agent development and Flow tools creating Power Automate flows. Luckily Claude will guide you and no matter how many times you ask it to write instructions when you find the best way to do it – it will skip the instructions because of some stupid reason. It is not autonomous and does not read the instructions even if the first line of the instructions is “read all the instructions”. You need to remind it, you need to guard it. And usually it is also good idea to logout from customer tenant after finishing the task for the day. I created safe control for that, it will run /clear for session and before that logs out automatically from customer environments if I’m idle more than 30 minutes.
Copilot Studio agents
Developing is still quite easy with Standard Harness, could not get working the GitHub Copilot Harness Claude experimental plugin but did not actually had much time to study it. New harness model agents are working much better and formatting the prompt is more important than twitching between topics which are not in the new model. I need to create the agent manually by portal and then clone the agent into my server. Then Claude Code has access to the yml files, can make edits and publish it back to the Copilot Studio. After that it can take latest changes and then run autonomously. I suggest creating Evaluation tests and do Test-Driven Agent Development to ensure that your agent is really doing what it needs to do.
Power Automate flows
This is the easiest, just allow Claude with your Azure login and I can create everything. Using pac cli it can check flow runs, start them. Create new flows. The only thing it could not do is put them into correct solution – or maybe I did not prompt enough. This is awesome, it really create high quality flows. I asked it to parametrize this huge solutions I created for customer for automating Power Platform environment creation and DLP connector requests, it did and I created DEV environment since the original solution was created directly into production because it uses SharePoint lists. I wanted that everyone in the tenant could use the Canvas App without Premium permission. Flow part was quite anonymous but Canvas App needed my help.
Power Apps
I think model-driven apps were easier to do, since it did not need my login. When creating Canvas Apps it was behind a struggle to get the co-authoring work. Luckily the first time it worked and then four next times took almost one hour struggle to get authentication work. Problem for me is that Claude Code is running in virtual server in Azure and the authentication port redirection to localhost url is not working, since my server does not have any windows open to internet. Finally we found solution where I need to write one line of JavaScript into console, so that I can click the invisible button in the page and do the login.
The gadgets were never the point
As a kid I watched Batman and Michael Knight with their gadgets. Now I have my own: four Musketeers, an old iMac called Platon, an Android phone called Cardinal and an app that lets me talk to all of them from the car. Since April I have gone from one agent window to a small orchestra. Pro code turned out to be easy for the agent. Power Platform is harder, because every tool needs its own login and the agent still skips its own instructions unless you remind it. So you guard it. The biggest lesson was not technical though. The toolset grew fastest when I worked every waking hour, and that is exactly when I got tired. Now I think the most important tool is not the watch I am planning. It is knowing when to close the laptop, even when the agents keep running without me.
And forgot the Claude app in my mobile 🙂