Documentation

Configure Ollama, OpenAI, or other embedding providers

Run Ogham on Neon, self-hosted PostgreSQL, or any Postgres with pgvector

JetBrains AI Assistant added MCP client support in 2026.1. That brings every IDE in the JetBrains family – IntelliJ IDEA, PyCharm, GoLand, WebStorm, Rider, RubyMine, RustRover, Android Studio – into the same memory loop as Claude Code, Cursor, and the rest. Five minutes of setup; your assistant remembers across IDEs and across projects.

Prerequisites #

• A JetBrains IDE on 2026.1 or newer with AI Assistant enabled.
• Ogham installed and reachable from your shell (ogham --version should work). If you haven’t run ogham init yet, start with the setup wizard.

Configure the MCP server #

JetBrains AI Assistant has a UI for this, no manual JSON file editing required.

Set up Ogham persistent memory inside Kiro

Common issues and fixes

Three things Ogham deliberately doesn’t do.

Where the name comes from and what the Irish terms in the codebase mean

Microsoft Agent Framework GA’d 1.0 in Q1 2026 as the merged successor to Semantic Kernel and AutoGen. It ships in Python and .NET with pluggable memory: built-in backends include Foundry Agent Service Memory, Mem0, Redis, and Neo4j. It also speaks MCP natively, which means Ogham can plug in today with zero glue code.

This page covers Shape A: registering Ogham as an MCP tool. The agent decides when to call it – store, search, compile, walk the graph – the same way it would call any other tool. No subclassing, no provider class.

What is SCION? #

SCION is Google Cloud’s multi-agent orchestration testbed. It runs LLM agents (Gemini CLI, Claude Code, OpenCode, Codex) in isolated Docker or Kubernetes containers, each with their own identity, credentials, and workspace.

The problem: agents in SCION are isolated by design. Agent A doesn’t know what Agent B learned. Every agent starts from a blank slate, and when it stops, its knowledge stays locked in its container.