Skip to main content

3 posts tagged with "ollama"

View All Tags

Watch Your LLM Think: Reasoning Now Visible in DevoxxGenie

· 3 min read
Stephan Janssen
Creator of DevoxxGenie

Reasoning models don't just answer. They think first. They talk themselves through the problem, weigh options, and correct course before committing to a reply. Until now, all of that happened invisibly: you saw the polished answer, but never the reasoning that produced it.

Starting with DevoxxGenie 1.8.12, you can watch it happen. Turn on Show Thinking and the model's chain of thought appears in its own dedicated 🧠 section, streaming live, right before the final answer.

What 18,000 Events Tell Us About How You Use DevoxxGenie

· 6 min read
Stephan Janssen
Creator of DevoxxGenie

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.

Why We Turned RAG Into a Tool

· 7 min read
Stephan Janssen
Creator of DevoxxGenie

For months, DevoxxGenie's RAG pipeline worked beautifully — as long as you stayed in chat mode. Index your project into ChromaDB, ask a question, and the most relevant code chunks would automatically appear in the prompt as a <SemanticContext> block. It was invisible, automatic, and effective.

Then we shipped Agent Mode, and RAG fell off a cliff.

Users would ask conceptual questions like "which slides discuss MCP?" or "where do we explain the indexing pipeline?" and the agent would ignore the rich semantic context we had just injected. Instead, it reached for search_files — a regex grep — and returned nonsense. The semantic context had become wallpaper: present, but unseen.