Supported Agent Frameworks

ContextNest ships connector packages for eight agent frameworks. Every package is an outbound, retrieval-only client that reads approved context from a hosted Community Nest over its public REST API — it just exposes that retrieval through whatever idiom the target framework uses (a knowledge source, a tool, a toolset, a retriever, a workflow node). This page lists each package, its status, and how it pulls context. For the shared connector design and licensing, see Connectors.

Framework support matrix

All eight read from the nest's public REST API. None bundles the ContextNest engine, and none writes back to the nest — retrieval only.

Status legend

• ✅ Supported — connector is available and functional.
• 🔶 Partial — connector exists but has an outstanding validation gap. For Dify, the tool plugin still needs live .difypkg validation before it can be marked fully supported.

Installation

Install names and pinned versions are not yet confirmed for this draft. Each connector is distributed for its framework's native package ecosystem (for example, a Python package for LlamaIndex, LangChain, CrewAI, Google ADK, and OpenAI Agents SDK; a JavaScript/TypeScript package for the Vercel AI SDK; a community node for n8n; and a plugin package for Dify). Confirm the exact identifiers against the Connectors repository before publishing.

Prerequisites

Each connector reads from a published, readable nest. Before wiring up a framework, publish and expose the nest — see Publishing a Nest. Only approved snapshots are returned, per Governance & Stewardship.

Sources

• PromptOwl/Promptowl-ContextNest-Connectors commits (July 2026): 4c15be9, 0e68f7c, 8004a69, 7c709e4, b623b54, 27c64e7.