gh-dev-loop-test
An experiment: can a Muse agent run a real GitHub development workflow
end-to-end? This repo is the lab notebook. Everything here — scaffold,
commits, pushes, toolchain installs — was done by Merlin (Muse agent) on
2026-09-13, driven from a phone.
Verdict: the dev loop works — writing code, testing, pushing is all
smooth. The friction is GitHub auth (device codes, missing token scopes),
and the sandbox hard-blocks anything needing containers. Receipts below.
The machine
- Linux x86_64, kernel 7.0.0-26-generic (Ubuntu 24.04)
- 2 vCPU (AMD EPYC 9D25), 7.7 GB RAM, 7.5 GB disk
- Preinstalled: git 2.43.0, gh 2.100.0 (unauthenticated), gcc/g++ 13.3.0,
make, cmake, sqlite3, python3 3.12, node 24
Small but sufficient: full test suites for six languages run in seconds.
How to develop with it
git clone https://github.com/mxschmitt/gh-dev-loop-test.git
cd gh-dev-loop-test
git checkout -b <branch>
# edit, then:
python3 -m pytest python/ # or: node --test node/
cargo test --manifest-path rust/Cargo.toml
cd go && go test ./...
git add -A && git commit -m "..." && git push -u origin <branch>
gh pr create --fill # needs gh auth (see below)
How to install languages (how I did it)
No sudo, no package manager — user-space installs, minutes each:
# Rust
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs -o /tmp/rustup.sh
sh /tmp/rustup.sh -y --profile minimal
export PATH="$HOME/.cargo/bin:$PATH"
# Go
V=$(curl -s https://go.dev/VERSION?m=text)
curl -sL https://go.dev/dl/${V}.linux-amd64.tar.gz -o /tmp/go.tar.gz
mkdir -p ~/sdk && tar -C ~/sdk -xzf /tmp/go.tar.gz
export PATH="$HOME/sdk/go/bin:$PATH"
Result: rustc/cargo 1.98.1, go 1.27.1, both fully working.
Experiments
| # |
Experiment |
Result |
| 1 |
Clone / branch / edit / commit locally |
✅ trivial |
| 2 |
gh auth login (device flow) |
✅ worked, but code copy on mobile is painful |
| 3 |
gh repo create + push |
✅ repo live |
| 4 |
Push .github/workflows/ci.yml |
❌ rejected — OAuth token lacks workflow scope |
| 5 |
gh auth refresh -s workflow |
❌ needed a 2nd device-code round-trip; grant didn't stick |
| 6 |
Language inventory (python/node/perl/c/c++/sqlite) |
✅ all run, see table below |
| 7 |
Install Rust + Go on demand |
✅ minutes, no sudo, tests pass |
| 8 |
Keep CI workflow local-only |
⚠️ workaround for #4 — it's untracked, not forgotten |
| 9 |
Install k3s, run hello-world pod |
⚠️ half — k3s v1.36.4 API server runs, pod object created, but it stays Pending forever: zero cgroup controllers are delegated in this container, so the kubelet can't start and no nodes exist. Grok Bot's box delegates cgroups, so its kubelet ran (it only needed snapshotter/network tweaks). |
Language smoke tests (greet("merlin") → hello, merlin!):
| Language |
Version |
Status |
| Python |
3.12.3 |
✅ |
| Node.js |
24.20.0 |
✅ |
| Perl |
5.38.2 |
✅ |
| C / C++ |
gcc 13.3.0 |
✅ |
| Rust |
1.98.1 (installed in #7) |
✅ cargo test passes |
| Go |
1.27.1 (installed in #7) |
✅ go test passes |
| SQLite |
3.45.1 |
✅ |
| Ruby / PHP / Java |
— |
➖ not installed, not tried |
Receipts
Actual terminal output behind the claims above.
Push rejected without the workflow scope (experiment 4):
! [remote rejected] master -> master (refusing to allow an OAuth App to
create or update workflow `.github/workflows/ci.yml` without `workflow` scope)
error: failed to push some refs to 'https://github.com/mxschmitt/gh-dev-loop-test.git'
Token scopes after two device-code round-trips (experiment 5) — still
no workflow:
- Token scopes: 'gist', 'read:org', 'repo'
Zero cgroup controllers delegated (experiment 9) — can't be enabled
from inside:
$ cat /sys/fs/cgroup/cgroup.controllers
(empty)
$ echo '+cpu +memory +pids' > /sys/fs/cgroup/cgroup.subtree_control
write EXIT:1
k3s: API server runs, kubelet can't, pod pends forever (experiment 9):
$ k3s server
level=fatal msg="Error: failed to find cpu cgroup (v2)"
$ k3s kubectl version
Client Version: v1.36.4+k3s1
Server Version: v1.36.4+k3s1
$ k3s kubectl get pod hello-world
NAME READY STATUS RESTARTS AGE
hello-world 0/1 Pending 0 8s
The CI workflow that couldn't be pushed (experiments 4 & 8):
ci.yml
name: ci
on: [push, pull_request]
jobs:
python:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with: { python-version: "3.12" }
- run: cd python && python -m pytest test_greet.py
node:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: "24" }
- run: cd node && node --test greet.test.js
rust:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: cd rust && cargo test
go:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with: { go-version: "1.21" }
- run: cd go && go test ./...
Learnings for the future
- The machine is the easy part. Toolchains install in minutes without
sudo; the dev loop (edit → test → commit → push) works fine.
- Auth is the hard part.
gh ships logged out, the device flow is
phone-hostile (copy a code, switch apps, paste), and the default token
scopes silently exclude workflow — so CI files can't be pushed.
- Scope upgrades are a trap.
gh auth refresh -s workflow demands
another full device-code round-trip, and in our run the grant didn't
stick. Budget for this or use a PAT with the right scopes up front.
- Keep
.github/ out of git add -A until the scope is sorted, or
every push gets rejected. (We learned this twice.)
- What's missing for a nice Muse↔GitHub workflow: a one-click GitHub
connector (like Gmail/Notion/X have), pre-authed
gh, and a way to
watch PR/CI status without polling.
- Know your sandbox — it's the real differentiator. This container is
delegated zero cgroup controllers (
/sys/fs/cgroup/cgroup.controllers
is empty; enabling them is denied). k3s installs and its API server
runs, but the kubelet can never start — no nodes, pods stay Pending,
and no docker/containerd either. Grok Bot ran the same task on a box
that delegates cgroups: its kubelet started, needing only
snapshotter: native and flannel-backend: host-gw tweaks. Same agent
capability, different sandbox privileges. The model isn't the moat;
the sandbox is.