rust · go · local models · tiny language models · 3 min read

Building a team of Mini Mes with ACP

Build a team of local Mini Me agents talking over ACP: a coordinator that routes your Go and Rust questions to two documentation specialists.

K
k33gOct 15, 2026 · 3 min
Building a team of Mini Mes with ACP

A Mini Me agent (mm) supports the ACP protocol (see the previous post: Mini Me and the ACP protocol (Agent Client Protocol)), which means a Mini Me agent can send a message to another Mini Me agent using this protocol. I added the helpers needed to make communication between agents simpler.

So today, we're going to build ourselves a team of "coding helpers" to get interactive documentation for Go and Rust. You know, a bot to answer questions like:

  • How does pattern matching work in Rust?
  • How do I add a method to a struct in Go?
  • How do I create a library in Rust?
  • Etc. ...

Building the team

We'll ask our questions to a coordinator, which hands them off to the right specialist with the built-in ask_agent tool of Mini Me (mm):

AgentFileModelRole
🧭 coordinatoragent.yamlQwen3.5 0.8B (hf.co/unsloth/Qwen3.5-0.8B-GGUF:latest, 737.5 MB)picks go or rust, sends the question along with the conversation
🐹 goagent.go.yamlMellum2 12B A2.5B (hf.co/JetBrains/Mellum2-12B-A2.5B-Instruct-GGUF-Q4_K_M:Q4_K_M, 8.1 GB)documents Go
🦀 rustagent.rust.yamlthe same Mellum2 model, so it's loaded only oncedocuments Rust

For this post, the "specialists" document, they don't build: they explain and show snippets, and only write a complete program if you ask for it. They have no tools, so they never touch your files. No skills, no hooks either (hooks are a feature coming in Mini Me v0.5.0, post on its way once the release is out).

Configuring the coordinator agent

In the coordinator agent's configuration file agent.yaml, you need to define its "ACP identity":

yaml
acp:
  name: coding-helpers
  title: 🧭 Coding helpers (Go, Rust)

This lets the ACP client display information if needed.

And then, define the agents that will make up its team:

yaml
mmConfigs:
  go:
    path: agent.go.yaml
    description: >-
      Go specialist. Explains Go concepts and how to do something in Go,
      with short examples, like documentation. For any question about Go.
    yolo: true

  rust:
    path: agent.rust.yaml
    description: >-
      Rust specialist. Explains Rust concepts and how to do something in
      Rust, with short examples, like documentation. For any question about Rust.
    yolo: true

The mmConfigs section will help our coordinator choose between the 2 agents.

The full code is over here: agent.yaml

Configuring the specialists

Each agent will also have its own "ACP identity":

In the go agent's configuration (agent.go.yaml):

yaml
acp:
  name: go
  title: 🐹 Go specialist

Full code: agent.go.yaml

In the rust agent's configuration (agent.rust.yaml):

yaml
acp:
  name: rust
  title: 🦀 Rust specialist

Full code: agent.rust.yaml

Let's use our new team in the Mini Me TUI

Just run this command in the folder where the agents' configuration files live:

bash
mm --tui

We start the coordinator:

mini me
mini me

We ask it to call on the Go specialist:

mini me
mini me

Then the Rust specialist:

mini me
mini me

You can also call one of the agents directly with a "slash" command: /ask_<agent-name>.

mini me
mini me

And of course, if your editor supports ACP, it's even more comfortable to do it from the editor, here in VSCode with the Patchbay extension:

mini me vscode
mini me vscode

Or with Zed Editor:

mini me zed
mini me zed

And there you go! Also, don't forget that using several agents with the same model lets you spread the context size across several agents, by splitting it up by topic for example.

K

Written by

k33g

Keep reading

Mini Me and the ACP protocol (Agent Client Protocol)

Plug Mini Me into Zed and VSCode through the Agent Client Protocol, directly or running inside a Docker sbx sandbox, with a ready-made translator agent.

Oct 11, 2026
Mini Me and the ACP protocol (Agent Client Protocol)

Hello Mini Me: an agent born while preparing a talk for Devoxx

Meet Mini Me, a coding agent born from a Devoxx talk on the agent loop, built for small local models with guardrails against loops and hallucinations.

Oct 3, 2026
Hello Mini Me: an agent born while preparing a talk for Devoxx

Mini Me release v0.3.0

What is new in Mini Me v0.3.0, the Devoxx Belgium release: approval mode, agents calling agents, request traces, JSON answers, AGENTS.md and an sbx kit.

Oct 10, 2026
Mini Me release v0.3.0

Responses

0 Comments

No comments yet. Be the first to comment!

Related reading

From other blogs

A mini code agent with Docker Agent - Part 9: a team of agents to spread the context out

k33g_org's Blog