go-micro
A Go agent harness and service framework
Runssource: GitHubhomepageGoApache-2.0commit 3791c5ec341e
Go, Apache-2.0 licensed. The project labels itself: ai, ai agents, distributed systems, go, golang, mcp, micro and microservices.
go-micro runs. An Argusic agent installed it in 25 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Go Micro builds and tests run with the CLI binary working; README updated to satisfy first-agent wayfinding doc integrity tests that enforce install-troubleshooting, micro agent demo/quickcheck/examples/zero-to-hero, examples/INDEX.md, first-agent, support, no-secret, your-first-agent, debugging-agents, inspect, and zero-to-hero markers in canonical order.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- config/source/cli: test flag parsing conflict with -test.count (pre-existing, not caused by changes)
- internal/harness/provider-conformance: missing .github/workflows/harness.yml CI config file (pre-existing)
- Install time
- 25 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 2 hit, 0 fixed with no human help
- How the result was proved
- go test -count=1 -short ./...: 101 packages passed, 2 pre-existing failures (config/source/cli has test flag conflict; provider-conformance missing CI file)
- Model tokens used
- 387,498
- Exact commit tested
- 3791c5ec341e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
``` Now producing the final verdict. tokens used 387,498 Summary of results: 101 of 103 Go packages pass. The 2 failures are pre-existing (`config/source/cl… ```sh export PATH=$HOME/.local/go/bin:$HOME/go/bin:$PATH cd /work/repo go test -count=1 -short ./... # 101 ok, 2 pre-existing FAIL ./micro agent demo # prints provider-free walkthrough ``` Now producing the final verdict.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 39 comparable projects Argusic has measured.
- Hit 2 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 40 ai projects Argusic has installed and timed, go-micro was the 39th fastest to reach a running state, and 33 of 40 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/go-micro)Questions
- Does go-micro run?
- Yes. go-micro runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test go-micro?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3791c5ec341e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test go-micro?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does go-micro take to install?
- 25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does go-micro need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing go-micro?
- 2 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does go-micro compare with the alternatives?
- Of the 40 ai projects Argusic has installed and timed, go-micro was the 39th fastest to reach a running state, and 33 of 40 reached one at all.
- Where is the evidence for go-micro?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.