xgo
XGo is a programming language that reads like plain English. But it's also incredibly powerful, it lets you leverage assets from C/C++, Go, Python, and JavaScript/TypeScript, creating a unified software engineering ecosystem. Our vision is to enable everyone to become a builder of the world.
Runssource: GitHubhomepageGoApache-2.0commit ad73bea11e63
Go, Apache-2.0 licensed. The project labels itself: ai native, data science, golang, goplus, low code, programming language, scientific computing and stem.
xgo runs. An Argusic agent installed it in 11 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
XGo binary v0.0.0 builds, runs XGo programs, and all 18 Go test packages pass with 0 failures on Go 1.27.1 linux/amd64.
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 100 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.
- No Go compiler pre-installed in container1 minute
- xgo test ./... fails on XGo sources (builtin/doc.xgo type errors, cmd/chore/* undefined symbols)
- Install time
- 11 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... -count=1 exited 0 with 18 ok packages (ast, ast/fromgo, ast/togo, cl, cl/internal/gop-in-go/foo, cl/internal/typesutil, demo/unit-test, doc, dql/html, env, format/formatutil, parser, printer, token, token/internal/tokenutil, tool, tpl/parser, tpl/scanner, tpl/token, x/build, x/format, x/jsonrpc2/jsonrpc2test, x/typesutil, x/xgoprojs). /work/repo/bin/xgo version returned 'xgo v0.0.0-20260919013125-ad73bea11e63 linux/amd64'. xgo run fib.xgo printed 'fib(10) = 55'. xgo run hello.xgo printed 'Hello from XGo!'.
- Model tokens used
- 88,953
- Exact commit tested
- ad73bea11e63
- 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.
Link /work/repo/bin/xgo to /home/runner/gopath/bin/gop successfully. Link /work/repo/bin/xgo to /home/runner/gopath/bin/xgo successfully. End linking. XGo tools installed successfully! NEXT STEP: We just installed XGo into the directory: /home/runner/gopath/bin To setup a better XGo development environment, we recommend you add the above install directory into your PATH environment variable. Everything works end-to-end. Here's the summary: tokens used 88,953 Everything works end-to-end. Here's the summary:
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.
- Installed in 11 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
ai-nativedata-sciencegolanggopluslow-codeprogramming-languagescientific-computingstemstem-educationxgo
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xgo)Questions
- Does xgo run?
- Yes. xgo runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test xgo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ad73bea11e63. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test xgo?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xgo take to install?
- 11 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 xgo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xgo?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for xgo?
- 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.