Add RuleFoundry
Use a direct package where available. An official marketplace install link appears here only after that listing is accepted and verified.
Direct plugin packages are available for supported test and CLI paths. All four marketplace submissions are awaiting review; official install links will appear here only after the listings are accepted and verified.
Use reviewed business logic to plan features, write code, and generate tests without reconstructing the rules from tickets.
Submitted - awaiting Cursor review
Carry the same business logic into Claude and Claude Code for implementation, analysis, and documentation.
Submitted - awaiting Anthropic review
Use permitted RuleFoundry knowledge to create plans, specifications, documents, and other useful work in ChatGPT.
Submitted - in OpenAI review
Use completed RuleFoundry artifacts as source material in Copilot CLI and supported IDE workflows.
Submitted - awaiting marketplace review
The connection uses RuleFoundry sign-in and OAuth authorization. It does not get a back door to your account or database.
Use a direct package where available. An official marketplace install link appears here only after that listing is accepted and verified.
RuleFoundry opens a secure sign-in and consent flow. Review the requested access before approving it.
Your assistant can find only permitted workspaces and the Extractions you own or are assigned to.
Use completed artifacts as grounded context, or create a new Extraction request after confirming its topic, description, and participant. Unfinished work returns its status and RuleFoundry app link; the actual session stays in RuleFoundry.
Marketplace and direct-install connections can list permitted workspaces and owned or assigned Extractions, read completed artifacts, return RuleFoundry app links, or create an Extraction after you confirm its topic, description, and participant - yourself or another person. For an external participant, RuleFoundry automatically sends the same invitation email as the app; email is not a separate plugin action. Creating the request does not begin the Extraction. The connection cannot begin usage, conduct, resume, complete, modify, resend, or delete an Extraction or artifact. Every actual Extraction session still happens in the RuleFoundry app; code or documents the assistant creates remain downstream work in that assistant.
The context is more than a transcript summary: a completed artifact comes from an active, FDE-style Extraction that probed ambiguity, exceptions, and inconsistencies. A connected assistant can then turn that grounded logic into the work you request.
Give a connected assistant the reviewed rules before it designs the feature, changes a data model, writes code, or generates tests.
Turn the captured logic into specifications, SOPs, runbooks, onboarding material, decision guides, or customer-facing explanations.
Build requirements, acceptance scenarios, implementation plans, review checklists, and follow-up questions from the same source knowledge.
The plugin communicates reusable business logic, not a fixed document type. Your assistant can transform it into the downstream deliverable you ask for.
PERMISSION MODEL
Marketplace and direct-install connections receive scoped, revocable, least-privilege access. Every read and every Extraction creation is checked against the same workspace and Extraction permissions used by the web app.
Start with one free Extraction and use a direct package where supported. Official marketplace install links will appear here only after each listing is accepted and verified.