Skip to main content

Automate your full development process with handoffs

GHub Copilot gives you the option to create your own agents (before called chatmodes). Such a custom agent can pick up specific tasks and take on a role inside the development process e.g. a code reviewer, a tester, an architect, ...

Custom agents are defined in an .agent.md Markdown file and consists of the following elements:

  • A name
  • A description
  • An (optional) model
  • A set of tools that the agent can use
  • And of course, a prompt

Remark: For the full list of elements, have a look at the documentation here.

Here is an example from the Awesome Copilot Github repo:

Handoffs

With the latest VSCode update an extra element was introduced, handoffs. Handoffs allow to create sequential workflows where after one agent has completed it’s job, it can handover the work to another agent.

This handoff can happen automatically or through handoff buttons that let you choose how to continue.

Let’s us create an example:

  • First I create 2 agents

 

  • Notice that in the first agent I added an handoffs section. In this section I can specify one or more handoffs.
  • Each handoff has the following values:
    • A label: A clear description to identify the next step
    • An agent: which agent should go next
    • A prompt: A prompt that can be passed to the agent
    • A send value: Setting this to true will automatically do the handoff to this agent
  • Don’t be afraid to make any mistakes as the VSCode team provided IntelliSense;
  • Now we can ask our first agent to go to work:
  • Once it completes its task, you get the option to choose how to proceed:
  • You can continue in the foreground or delegate work to an agent in the background (more about that in the next post) or in the cloud:

Nice!

More information

Custom agents in VS Code

Supercharge your AI Workflow with Github Copilot Custom Prompt Files

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...