okf-mcp: the observation registry is shared by every conversation of one server process

Open
#260 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Read src/OKF4net.Mcp and the samples/second-brain limitation note, then check whether the MCP transport exposes a session id. The issue needs a design decision among per-session registries, documenting the limitation, or accepting the behavior; done means one option is agreed before any code change.

Written by the indexing model from the issue text.

Description

.NET question

Area

src/OKF4net.Mcp — observation registry scope.

Question

OkfMcpToolset.Build builds one OkfBundleTools per server process, so its ObservationRegistry (§5.4) is shared by every conversation of the client: in Claude Desktop, a concept read in one chat authorises a write in another until the process restarts. The gate's intent is "this session saw that version".

Options: per-MCP-session registries (if the transport exposes a session id), documenting it as a limitation (done in samples/second-brain), or accepting it. Design decision needed before any change.

Found while building the #160 sample.

Dominant language
C#
Stars
4
Forks
1
Avg merge
1d 4h
Merged PRs (30d)
32

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jchable/okf4net

All issues in jchable/okf4net

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.