Kontext - an AI agent memory and RAG plugin for KurrentDB#5567
Draft
Kontext - an AI agent memory and RAG plugin for KurrentDB#5567
Conversation
Contributor
Review Summary by QodoAdd KurrentDB.Plugins.Kontext — embedded agent memory plugin with MCP support
WalkthroughsDescription• Adds KurrentDB.Plugins.Kontext embedded agent memory plugin with MCP HTTP endpoint • Implements IKontextClient using internal ISystemClient for reads/writes/subscriptions • Provides KontextStreamAccessChecker for post-filtering search results against stream ACLs • Includes 21 passing tests covering client operations, MCP endpoint, and end-to-end workflows Diagramflowchart LR
Agent["Agent (Claude Code)"]
MCP["MCP HTTP Endpoint<br/>/mcp/kontext"]
Auth["Auth Middleware"]
Plugin["KontextPlugin"]
Client["KontextClient"]
SystemClient["ISystemClient"]
AccessChecker["KontextStreamAccessChecker"]
SQLite["SQLite Database<br/>FTS5 + Vector"]
Agent -->|"JSON-RPC over POST"| MCP
MCP --> Auth
Auth --> Plugin
Plugin --> Client
Plugin --> AccessChecker
Client --> SystemClient
AccessChecker --> SystemClient
Plugin --> SQLite
File Changes1. src/KurrentDB.Plugins.Kontext/KontextPlugin.cs
|
Contributor
Code Review by Qodo
1. ToolkitTestEnvironment.Initialize() missing assembly
|
shaan1337
changed the title
shaan1337
changed the title
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
Comment on lines
+10
to
+16
| [Before(Assembly)] | ||
| public static ValueTask BeforeAssembly(AssemblyHookContext context) => | ||
| ToolkitTestEnvironment.Initialize(); | ||
|
|
||
| [After(Assembly)] | ||
| public static ValueTask AfterAssembly(AssemblyHookContext context) => | ||
| ToolkitTestEnvironment.Reset(); |
Contributor
There was a problem hiding this comment.
1. toolkittestenvironment.initialize() missing assembly 📘 Rule violation ⛯ Reliability
The new test wire-up does not pass context.Assembly to ToolkitTestEnvironment.Initialize/Reset, which breaks the required standardized per-assembly test environment lifecycle. This can cause unreliable test setup/cleanup when multiple test assemblies run under the shared toolkit.
Agent Prompt
## Issue description
`TestEnvironmentWireUp` does not call `ToolkitTestEnvironment.Initialize(context.Assembly)` / `Reset(context.Assembly)` as required.
## Issue Context
The repository test infrastructure relies on assembly-scoped initialization/reset to avoid cross-test-project interference.
## Fix Focus Areas
- src/KurrentDB.Plugins.Kontext.Tests/TestEnvironmentWireUp.cs[10-16]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Comment on lines
+19
to
+22
| <ProjectReference Include="..\KurrentDB.Common\KurrentDB.Common.csproj" /> | ||
| <ProjectReference Include="..\KurrentDB.Core\KurrentDB.Core.csproj" /> | ||
| <ProjectReference Include="..\..\libs\Kurrent.Kontext\src\Kurrent.Kontext\Kurrent.Kontext.csproj" /> | ||
| </ItemGroup> |
Contributor
There was a problem hiding this comment.
2. Ci misses submodules 🐞 Bug ⛯ Reliability
CI uses actions/checkout without enabling submodule checkout, but the solution now includes libs/Kurrent.Kontext as a git submodule and directly ProjectReferences its csproj, causing restore/build failures in CI and for developers without git submodule update --init.
Agent Prompt
### Issue description
The repo now depends on a git submodule (`libs/Kurrent.Kontext`) at build time via `ProjectReference`, but CI workflows check out the repository without fetching submodules. This causes missing project files during restore/build.
### Issue Context
Workflows using `actions/checkout@v4` must set `submodules: recursive` (or at least `true`) for submodules to be present.
### Fix Focus Areas
- .github/workflows/common.yml[21-73]
- .github/workflows/build-reusable.yml[17-97]
- .github/workflows/build-container-reusable.yml[11-97]
### Suggested change
Update each `actions/checkout@v4` step to include:
```yaml
with:
submodules: recursive
```
If you intentionally do not want submodules in some jobs, then remove the `ProjectReference` dependency and consume `Kurrent.Kontext` as a NuGet package or vendored source instead.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
shaan1337
force-pushed
the
shaan1337/kontext
branch
2 times, most recently
from
de5de25 to
d4cc993
Compare
shaan1337
changed the title
shaan1337
force-pushed
the
shaan1337/kontext
branch
15 times, most recently
from
1a27b64 to
6c6deef
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
shaan1337
force-pushed
the
shaan1337/kontext
branch
from
6c6deef to
7a74efc
Compare
Contributor
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the Kontext plugin — an embedded agent memory and RAG system for KurrentDB that gives AI agents durable, searchable memory backed by KurrentDB events.
Kontext supports any AI agent that can connect to an MCP server over HTTP (Claude Code, Cursor, Windsurf, Copilot, etc.). Importing data into Kontext requires the agent to be able to run
curlor any equivalent HTTP client tool.Configuration
Data stored under
{index}/kontext/. Memory stream is$kontext-memory.Docker image (preview)
Connecting Claude Code
Add
.mcp.jsonto your project root:{ "mcpServers": { "kontext": { "type": "http", "url": "http://localhost:2113/mcp/kontext", "headers": { "Authorization": "Basic YWRtaW46Y2hhbmdlaXQ=" } } } }Try it out
RAG — ask Claude about events in an existing database:
Data Import — load a dataset and explore it:
Agent Memory — insights are retained across sessions:
How it works
The plugin subscribes to
$alland indexes every event using hybrid text + vector search. Agents connect via MCP over HTTP and can search events, retain synthesized facts, and recall them in future sessions.All configuration options
Use cases
Customer Support — Load ticket logs, ask an AI agent to find patterns and root causes.
Incident Investigation — Import production logs, let agents correlate events across services.
Sales Intelligence — Import CRM data, ask agents to spot trends and opportunities.
Compliance Auditing — Import transaction records, let agents flag anomalies.
Product Analytics — Import user activity events, ask agents to surface insights.
Knowledge Base — Import documentation, let agents answer questions grounded in your docs.