Trust
What you actually get.
Four honest answers.
Klabauter looks at your repos — that's a matter of trust. A fair deal needs honest answers to the hard questions, not just the easy ones. Here are mine.
Why mac-only — and forever?
Klabauter sits deep in macOS APIs that simply don't exist elsewhere: SwiftUI MenuBarExtra with Liquid Glass, NaturalLanguage for the on-device embeddings behind finds, strict Swift 6 concurrency, UserNotifications for the morning greeting.
Going cross-platform would mean building three separate products — each one further away from the system. The result would be a kobold that's mediocre everywhere instead of excellent on one platform.
Your guarantee
Cross-platform is not on our roadmap, not parked in 'Future / aspirational', and not 'maybe in 5 years' — it's a deliberate non-goal. Mac-only by design. Forever.
Which data goes to AI — and to which one?
Honestly first: Klabauter is NOT 100% local. For triage and deep analyses the app sends project context to an AI endpoint: README, package manifest, and a git-log summary. No full codebases, no secrets — but more than "nothing".
Which endpoint that is, you decide: kimi acp (Moonshot) by default, alternatively any OpenAI-compatible endpoint or DeepSeek via jcode. The call goes straight from your Mac to the endpoint — there is no moinsen.dev server in between recording anything.
What stays local: all scores and reports (cache in .pumuckl right inside the repo), your finds including embeddings (on-device, Apple NaturalLanguage), and the portfolio knowledge. GitHub access runs through the gh CLI with your own login — Klabauter never sees a token.
Your guarantee
The AI endpoint is switchable at any time, no lock-in. There is no Klabauter cloud collecting your project data — we can't sell or lose what we never have.
Why isn't Klabauter open source?
In 2026, open-source maintainers are flooded with AI-generated pull requests — most well-intentioned, few well-crafted. Maintainer burnout from PR triage is the most common cause of small OSS projects dying.
Klabauter is built by a solo developer who funds the next features from the one-time price after beta. Going open source would mean spending 30% of the time on PR reviews instead of code — at the expense of what makes Klabauter better, i.e. at your expense. That said: the .pumuckl data format and the bundled Claude Code plugin are open to inspect — your analysis data belongs to you in readable form.
Your guarantee
The open-source question is publicly re-asked on a regular basis (in the GitHub repo). When market reality or maintainer capacity changes, the answer changes — and you'll hear it first.
What does "no telemetry" mean for an AI app?
Many apps write "no telemetry" on their landing and still ship data — crash reports, anonymous usage stats, remote feature flags, A/B tests. "No telemetry" is interpreted very generously in the industry.
At Klabauter, "no telemetry" is literal: the app connects to exactly two destinations — the AI endpoint you configured yourself, and the GitHub API (via the gh CLI, with your own login). There is no Klabauter account, no license-server check, no analytics endpoint, no Sentry. This landing page itself sets no cookies either.
What we specifically did not build
No Sentry, no crash reports (you can attach crash logs to a GitHub issue manually). No analytics, no "anonymous" usage stats. No remote feature flags — what you installed is what's in the binary. No A/B testing. This list is append-only — if anything ever joins it, it will be announced publicly in the GitHub repo before release.
Still have a question?
Missing an honest answer that should be here? Open an issue on the repo — I usually reply within 24-48h.
Ask on GitHub