After trying out Claude Code and OpenCode it is time you test GitHub Copilot CLI. I was a bit skeptical, since this is already old stuff and I had couple licenses to this. But GitHub Copilot suprised me very well 🙂

I started mapping if need Copilot Studio skill or can use the ones installed into Claude Code already.

Mapping if skills are already installed
Mapping if skills are already installed

GitHub Copilot turned out to be very helpful and smart after all. I don’t know why I had doubts.

Pointing out the correct folder to find the skills
Pointing out the correct folder to find the skills

Then I created again empty Agent in Copilot Studio – with this I can control the what I get down to virtual machine and in which agent the changes affects to.

Empty Copilot Studio agent
Empty Copilot Studio agent

Cloning the Copilot Studio agent with VS Code to virtual machine
Cloning the Copilot Studio agent with VS Code to virtual machine

Once again cloning opened a VS Code again and need to open new terminal and start GitHub Copilot again – this happened both with Claude Code and OpenCode since it is Copilot Studio extension feature of VS Code, not the CLI itself. But later on doing this to other agents this feature did not appear anymore.

Prompt GitHub Copilot

Then I was prompting the GitHub Copilot with the same prompt as Claude Code and OpenCode. I got stuck when trying to merge the yml files for the cloned files. Needed to try again.

Getting stuck when trying to merge yml files, maybe missed something while multitasking
Getting stuck when trying to merge yml files, maybe missed something while multitasking

I was worried since GitHub Copilot was taking quite much time.

Waiting GitHub Copilot to finish the processing
Waiting GitHub Copilot to finish the processing

I felt like some eternal loop where GitHub Copilot is asking again and again permission to different directories or commands but I cannot see any file implementations for agent. Finally there was some changes in files and I see progress after 30 minutes of processing. But this is the slowest, after that Claude Code and OpenCode did everything like in 5 minutes.

Finally I got to upload output to Copilot Studio!

GitHub Copilot indicating some changes in the files
GitHub Copilot indicating some changes in the files

There was two errors in the yml files, upload did not work. The same as with other models, I just give the error messages to GitHub Copilot and wait it to fix the stuff and then try to upload again.

Fixing errors with agentic development
Fixing errors with agentic development

This gives quite trustworthy answer but it is totally wrong – maybe it understood wrong city. I think it might be in Lemu instead of Lemuntie.

Answering totally gibberish in Copilot Studio when trying the pushed agent in UI
Answering totally gibberish in Copilot Studio when trying the pushed agent in UI

I know that the task was too hard for agentic development since it needs Copilot Studio tools that can read external data source trough API. You cannot instruct Copilot Studio agent to do it and I think there is not skill for CUA. But this got some information from somewhere which was not so generic like other models told me.

Better answer from GitHub Copilot created Copilot Studio agent
Better answer from GitHub Copilot created Copilot Studio agent

And after all when I look the answer it is still far more better than Claude Code or OpenCode, since this looks like it somehow understands the route and searches the pages instead of just giving general answer. It gets the line and bus stops numbers.