A Workspace installs a plugin once, but that single installation is reused by
several product objects: every processor for a Runner, every knowledge base for
a KnowledgeEngine / Parser / Retriever, and many conversations or page requests
for the other component kinds. The platform storage key carries no processor or
knowledge-base dimension, so a plugin must fold that identity into its own keys.
- certified-plugins: add "one installation, many usages" with the isolation
dimensions per component kind, and "when an installation is revoked"
documenting BasePlugin.on_installation_revoked, its trigger set, the absent
invocation context and the no-op/failure semantics.
- component pages (runner, knowledge-engine, knowledge-retriever, parser, tool,
command, event-listener, page): add a short component-specific section with
that component's own rules and a link to the contract page.
- Align the background-work rule with the SDK contract: the SDK does not track
ownership of detached work, so a plugin must keep its own binding-keyed
registry and stop it in the revocation hook.
All three locales carry the same sections.
Rewrite plugin/certified-plugins in all three locales around the
questions a plugin developer actually asks, and make it the single home
for certification: what it is, why it exists, when it is needed, what
changes after approval, and what the contract requires.
- Decision framing restored, including a needs/does-not-need table and
the explicit statement that most plugins do not need certification.
- Full manifest example, accepted values for both declaration fields and
the SDK version that recognises them.
- Constraints kept and tightened: stateless rules, allowed/forbidden
table, anti-patterns with correct/incorrect snippets, Runner notes,
self-check list.
- Submission flow moved onto this page so it no longer depends on the
publishing page.
- Operator content that duplicates the Core architecture document
removed (Cloud admission matrix, OSS issuer keys, certificate fields,
internal review tiers).
publish/market is now publishing-only with a one-line pointer, and its
misplaced plugin_submission screenshot moves back under the upload
section where it belongs. dev/basic-info replaces the commented-out
manifest fields with a link to the contract page.
ja had been missing whole sections (36 lines); all three locales now
share the same section structure.
* docs: update wiki for RAG engine plugin architecture
Replace KnowledgeRetriever component docs with RAGEngine across all
three languages (zh/en/ja). Key changes:
- Add new rag-engine.mdx component docs covering RAGEngine base class,
creation_schema/retrieval_schema, capability declarations, lifecycle
hooks, host RAG APIs, and complete code examples
- Update knowledge base usage docs to reflect unified KB model (remove
internal/external distinction, add RAG engine selection flow)
- Update component list (add.mdx) and plugin intro to reference RAGEngine
- Add RAG API section to plugin common APIs (invoke_embedding,
vector_upsert/search/delete, get_rag_file_stream)
- Update docs.json navigation to point to rag-engine pages
Companion to LangBot PR #1995 and SDK PR #34.
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* fix: sync with sdk
* docs: update vector API docs with metadata filters, search_type, and documents support
- Replace Warning tags about unimplemented filters with Info tags documenting
canonical filter format (Chroma-style where syntax) and supported operators
- Document search_type/query_text params for full-text and hybrid search
- Document documents param for vector_upsert
- Update RetrievalContext.filters description from reserved to active
- Add filter usage examples (en/zh/ja)
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* docs: enhance RAG Engine documentation across multiple languages
- Expanded the description of the RAG Engine component to include bridging capabilities with advanced knowledge base services like Dify, RAGFlow, and FastGPT.
- Clarified the `DOC_INGESTION` capability description, specifying conditions under which the declaration can be omitted.
- Updated documentation in English, Japanese, and Chinese to ensure consistency and clarity.
* docs: add instructions for show_if conditional rendering
* docs: add Parser component documentation (zh/en/ja)
Add Parser as a new component type in plugin docs. Parser extracts
structured text from binary files (PDF, Word, etc.) before RAG engine
ingestion. Includes manifest format, parse method API, data models
(ParseContext/ParseResult/TextSection), RAGEngine integration via
parsed_content, and cross-plugin invoke_parser API.
Also add DOC_PARSING capability to RAG engine docs and parsed_content
field to IngestionContext.
Companion to SDK PR langbot-app/langbot-plugin-sdk#37 and
LangBot PR langbot-app/LangBot#2000.
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* docs: rename RAGEngine components to KnowledgeEngine
* refactor: change rag engine to knowledge engine
---------
Co-authored-by: Claude Opus 4.6 <[email protected]>
Co-authored-by: Junyan Qin <[email protected]>
* 重构文档结构：移除 docs 目录，调整文件组织结构
* Reorder "插件 SDK API" section in docs.json
* Refactor and clarify various documentation sections
* Refine warnings and info boxes across multiple docs
* Refactor and simplify Japanese documentation content
* Update package.json to include mintlify as a dependency and add pnpm-lock.yaml for dependency management
* Update blog link and add description in docs.json
---------
Co-authored-by: Junyan Chin <[email protected]>
