Context that travels_
Cursor's indexer is excellent inside Cursor. Maguyva is the hosted MCP map the same agent can query from other editors, CLIs, and CI.
> ls /var/log/decisions/*.md
Architecture decisions, MCP implementation notes, and the occasional rant about things that should not be this hard.
Latest dispatch
Start here if you want the freshest technical update before you drop into the archive.
Cursor's indexer is excellent inside Cursor. Maguyva is the hosted MCP map the same agent can query from other editors, CLIs, and CI.
Archive
Architecture, observability, MCP surface design, and the patterns that survived contact with production.
Ground the coding agent in a repo map before it writes. Let Greptile review the pull request after. A complementary pairing, not a swap.
How to give a coding agent a queryable map of a large repository from the cloud, without running a local indexer on your laptop.
AI coding agents invent file paths when they have no real map of the repo. Here is why it happens, and how grounding leads to fewer hallucinated edits.
We moved our code embeddings to voyage-4-large — currently top of the public RTEB code retrieval leaderboard. The honest version: the trade we make, what we actually index, and why we pay for premium embeddings.
We support code intelligence for ~280 languages. No human can hand-audit that. So we built a language recursive self-improvement loop — spot-check, LLM-as-judge, fix one thing, re-validate — and run it with a fleet of isolated agents until extraction is actually right, not just green.
A query like 'where is parseConfig defined' wants a different search than 'how does auth work'. Maguyva classifies the intent, weights four retrieval modalities accordingly, and fuses the results with weighted Reciprocal Rank Fusion.
We wired Claude Code and Codex into one Grafana stack with OpenTelemetry and Alloy, then used traces and logs to find and fix agent behavior issues at the source.
Git commits become structured changelog entries and architectural decision records, then feed back into AI agents as queryable institutional memory.
We screened 3,500 skill candidates and adopted 466. A systematic mining and ingestion loop for building a coherent AI agent skill library at scale.
Agent systems are opaque by default. Progressive disclosure gives operators layered CLI views from quick status checks to full agent internals and decision traces.
AI agents hallucinate confidently. Ground truths are versioned, scoped facts that anchor agent behavior to reality. Here is how we built and enforce them.
One orchestrator routes work to specialist AI agents, each with distinct skills and memory. How Orkestra coordinates 46 agents and 466 skills in production.
Every dispatch lands here first. New ones ship straight to the changelog, or subscribe via RSS to get notified the moment one drops.