ruflo
Claude Code multi-agent orchestration layer. The legitimate patterns vs the documented-but-not-quite-working ones. Quick start, cheatsheet, hard-won lessons.
Open ruflo notes โ
Quick-starts, cheatsheets, gotchas, and lessons-learned for the tools, libraries, and platforms HARTLE.TECH uses across our projects. Written from experience โ not a re-publication of upstream docs.
Each tool section follows the same shape:
| URL | What's there |
|---|---|
/<tool>/ | Tool landing โ what is this thing + why we use it + key links |
/<tool>/docs/ | Public docs โ quick-start, cheatsheets, our hands-on findings |
/<tool>/wiki/ | Internal wiki โ tailnet-only candid notes (gotchas with internal context) |
If you can see /wiki/ links, you're on the HARTLE.TECH tailnet. Otherwise they 404 โ by design, enforced at the Caddy layer.
We use a lot of tools across NearTrace, Nosferato, DumpSock, Medusa, hartle.tech-terraform, and others. When we figure out the actually-working pattern for one, we want it written down once โ and findable next time.
Rule: what's here is our experience. The upstream tool's docs are authoritative for the tool itself; we link to them for canonical reference. Our value-add is the "we stumbled onto X in project Y; this is how we got around it" layer.