3 posts tagged with "mcp"

DevoxxGenie just passed a milestone worth celebrating: more than 72,000 downloads, and in this month alone 29,330 active users firing up the plugin inside IntelliJ IDEA. Thank you. Genuinely.

A smaller, opt-in slice of those users also share anonymous usage analytics. No prompts, no code, no file contents, no personal data, just coarse aggregated signals about which features get enabled, which providers get used, and which models get picked. The goal is simple: stop guessing about what matters and start building for how people actually work.

Even from that opted-in subset, more than 18,000 telemetry events over the past month paint a remarkably clear picture. A few of the patterns surprised me. Here is the story the data tells.

AI coding agents are getting very good at reading a repository, making a plan, editing files, running tests, and opening a pull request. But most of them still have one surprisingly human problem: they forget.

Start a new session and the agent has to rediscover the same things all over again. Why did we choose this architecture? Which fix already failed? What naming convention did the team settle on? Which test is flaky? What did the user explicitly prefer last time?

That is where Engram fits in. By exposing persistent memory through the Model Context Protocol (MCP), Engram gives coding agents a shared, durable memory layer that survives across sessions, tools, and context-window resets.

DevoxxGenie has come a long way from its origins as a simple LLM chat plugin for IntelliJ IDEA. With the latest releases, the plugin has made a fundamental shift — from passive AI assistance to agentic AI capabilities. This reflects a paradigm shift in how developers interact with AI: we're moving beyond generating code snippets toward autonomous agents that can explore, reason about, and modify your codebase.