✦   community

built open.
used openly.

The code is on GitHub. Agents review it. Humans use it. Here's how to participate.

how it works

the QA contributor model

Agents write reviews and merge code. Humans have a different and equally load-bearing role: they use milady in real conditions and report what breaks.

No formal QA team. No scripted test scenarios. Real usage, real bugs, real reports. The feedback loop runs from issue to fix to release in hours — not weeks — because the pipeline is automated end-to-end.

If you run milady, you're already participating. File an issue when something breaks. That's the contribution.

approximate cycle time

bug filedT+0
issue acknowledgedT+1h
fix PR openedT+4h
agent reviewT+4.5h
auto-mergeT+5h
releaseT+6h

depends on complexity and current queue

contributing

how to help

file a bug report

Find something broken? Open an issue on GitHub. Include your OS, milady version, and steps to reproduce. Logs help.

open an issue ↗

test a release candidate

Pre-releases are tagged on GitHub. Install them, use milady normally, report regressions. This is the human QA role in the pipeline.

see releases ↗

submit a pull request

Fork, change, open a PR. An agent reviews it — you get feedback from an AI reviewer, not a human. Usually faster.

contributing guide ↗

build a plugin

The plugin API is typed TypeScript. Publish as an npm package with the milady-plugin prefix and it's discoverable by the community.

plugin docs ↗

bug reports

what to include

The agent that triages issues extracts structured information from your report. Give it signal and the fix comes faster.

milady versionmilady --version → 2.0.10
OS and architecturemacOS 14.5 ARM64
LLM providerClaude / Ollama / etc.
steps to reproducenumbered, specific
expected behaviorwhat should have happened
actual behaviorwhat actually happened
logs if applicable~/.milady/logs/milady.log
get-logs.sh
# version
milady --version

# logs
cat ~/.milady/logs/milady.log | tail -100

# full diagnostic bundle
milady diagnostics > milady-diag.txt

Logs contain no personal data — only runtime events, errors, and timing. Safe to share.

find us

links