Repository navigation
.NET community integration: CAJAL local chat plugin (implemented externally) #13948
Description
An implemented native .NET community plugin is now hosted outside Semantic Kernel core: https://github.com/Agnuxo1/CAJAL/tree/main/integrations/semantic-kernel .
It exposes ask_local and health through the current KernelFunction / Kernel.InvokeAsync API, using Semantic Kernel Core 1.80.1 and the installable CAJAL local chat server. It supports loopback endpoints, cancellation and fail-closed response handling.
Validation: actual SDK discovery/invocation, negative HTTP/response/cancellation/scope checks, and an actual loopback HTTP request through CAJAL's Flask app, with mocked inference. Build 0 warnings/errors. CI: https://github.com/Agnuxo1/CAJAL/actions/runs/37344653790 . Implementation merged in Agnuxo1/CAJAL#3 . Documentation-only proposal: #13942.
Scope correction to the original proposal: the supported installable package is a local chat CLI/API. The old proposed ScientificWriter, Citation and PeerReview plugins are not implemented by this extension, and generated text is not verified research. No fixed memory requirement or research-quality claim is made. No Semantic Kernel core modification is requested.
Activity
[-]📝 Integration Proposal: CAJAL — Local Scientific Paper Plugin[/-][+].Net: 📝 Integration Proposal: CAJAL — Local Scientific Paper Plugin[/+]github-actions commentedon Sep 30, 2026
This issue is stale because it has been open for 90 days with no activity.
[-].Net: 📝 Integration Proposal: CAJAL — Local Scientific Paper Plugin[/-][+].NET community integration: CAJAL local chat plugin (implemented externally)[/+]Agnuxo1 commentedon Oct 5, 2026
Concrete update: the external .NET community plugin is implemented and merged in Agnuxo1/CAJAL#3, with both CI jobs passing. It uses the current native-plugin API for local chat and health, and includes real SDK plus loopback server-contract tests (model inference mocked). I corrected the original issue scope and refreshed the existing documentation PR #13942 to describe that actual functionality. No Semantic Kernel core changes or verified-paper/citation claims. A subsequent review identified redirect hardening; that follow-up is being addressed in the implementation before calling the integration finished.