Plugins

Install Obris as a plugin in your AI of choice. One bundle per ecosystem; same Obris underneath.

The plugin's goal is to sync your Obris knowledge to disk through the obris CLI, where the AI can read your topics as files. That's faster than calling a server every time, and it leaves the AI more room to focus on what you actually asked. The bundled MCP server keeps your knowledge reachable when the AI doesn't have filesystem access.

Each AI ecosystem has its own plugin format, so we ship a plugin per ecosystem. Pick the one that matches the AI you actually use.

Which plugin do I want?

Use the Obris Claude Plugin if you talk to Claude in Claude Code (the terminal CLI) or in Cowork (the Claude desktop app). One bundle covers both.

Use the Obris Codex Plugin if you talk to Codex in the Codex CLI or the Codex desktop app. Install runs through the CLI; the App picks up the installed plugin automatically. For Codex IDE extensions, connect Obris over MCP via an MCP connector instead.

You can install both. The same Obris account is behind every surface, so what you save in one shows up in another. The plugins shell out to the same obris CLI underneath, so the sync workflow is identical no matter which agent kicks it off.

Without a plugin

If you would rather not install anything plugin-shaped, you can still connect Obris directly:

The Obris CLI does the disk-level sync work on its own.
The Obris MCP server is reachable from any MCP-compatible client without a plugin wrapper.
For ChatGPT, the Custom GPT setup connects an Obris expert without any local install.