Skip to main content

Vision & roadmap

The foundation — free, local, and always on​

devcoach today is a free, open-source MCP server: one lesson at a time, rate-limited, entirely local, nothing to open or maintain. That foundation stays. The local-first model is not a limitation to eventually remove — it's a deliberate design that keeps your data on your machine and coaching genuinely unobtrusive.

Not commercialized​

devcoach is free and open-source under AGPL-3.0, and it is not being commercialized. There is no paid tier, no subscription, and no plans to sell the core tool — the thing you install and run stays free for everyone, forever.

If anything is ever sold, it would be a separate, derivative product built alongside devcoach — never a paywall bolted onto the tool you already use. There is nothing to buy today, and the roadmap below is a set of ideas we're exploring, not products with price tags.

There is no paid path at all today — not even a commercial license. The only thing the AGPL rules out is embedding devcoach inside a closed-source product; if that is ever your case, ask by opening an issue and it will be considered case by case. See License & commercial use for the details — ordinary use, at home or at work, is always free.

Roadmap — ideas we're exploring​

These are directions we find interesting, written down to invite discussion — not a committed plan and not a price list:

  • Lesson sharing — shipped in 2.1.0. A lesson that landed for you can be handed to a teammate as copyable text, a server-less link or a .devcoach.md file, and imported from the dashboard, the CLI or the agent, where it joins the coaching log as a shared lesson (topic, level and feedback tracked as usual, pacing untouched). Sharing is always explicit — nothing leaves your machine unless you send it. Next on this thread: short links (a secret Gist behind the long link, revocable from the CLI), ephemeral one-use links (zero-knowledge — the key stays in the URL fragment, the server holds only ciphertext that self-destructs on first read), and curated collections of lessons per stack that a team or a community can maintain.
  • Gap-driven learning paths — devcoach already learns where you're weak (topics you score low on, concepts you keep marking ❌, patterns the notebook flags). Connecting those gaps to a structured progression — the next thing to learn, in order — is a natural extension of that.
  • Deeper course modules — when you've hit the same wall three times, a longer, sequenced deep dive on exactly that concept could go beyond what a single lesson card can carry, while staying local and private.
  • Per-developer knowledge profiles — each developer's knowledge map, calibrated to their actual stack and experience level.
  • Team-level visibility — which topics a team is collectively strong or weak on, where coverage is thin, and where skills are concentrated in one person — enough signal to plan onboarding and spot gaps before they become incidents.

The individual, local experience stays private by default; anything team-shaped would be an opt-in layer on top, never a change to how the solo tool works.

What never changes​

  • Local-first for individuals — your data stays on your machine, forever
  • Free for personal use — a single developer connecting devcoach to their agent will always be able to use it at no cost
  • Unobtrusive by default — one lesson at a time, rate-limited, nothing to open

Shape the roadmap​

Have a feature request, a use case the current tool doesn't cover, or thoughts on any of the ideas above? Open an issue on GitHub Issues — feature requests, feedback and questions all live there.