Opem plugin for coding agents
Opem is a Help widget a company adds to its web app with one script tag, and a dashboard where its support staff answer. This plugin teaches your coding agent (Claude Code, Codex or ChatGPT) to install and configure the widget the way Opem documents it.
What it does
Eight skills, each loaded when the conversation needs it:
| Skill | What it helps with |
|---|---|
onboard | Signing up, creating a project and finding your keys |
install | The script tag, @opem/browser, @opem/react, Content-Security-Policy and allowed origins, and a check against the live /config endpoint |
identify | Signing users' identities on your server, in Node.js, Python, Ruby, PHP and Go |
knowledge-sync | Syncing Markdoc documentation from your repository, from CI |
webhooks | Verifying and handling Opem's webhook deliveries |
customise | The window.Opem surface: kinds, theme, launcher, strings, your own button, events |
troubleshoot | Every error code, rate limit and plan limit, from symptom to fix |
reference | Background facts the other skills use: the management API, plans, limits, glossary |
Install
Claude Code
claude plugin marketplace add agile-4/opem-agent-plugin
claude plugin install opem@opem
The skills then appear as /opem:install, /opem:identify and so on.
Codex
codex plugin marketplace add agile-4/opem-agent-plugin
Then run /plugins in Codex and install Opem; start a new session before using its skills.
ChatGPT
https://github.com/agile-4/opem-agent-plugin
Install Opem from the Plugins directory once it is listed there; until then a workspace admin can import this repository as a plugin marketplace.
Connect
The plugin declares Opem's MCP server, https://support.opem.app/api/v1/mcp. Connect it once (sign in, choose the organisation, consent) and the agent creates projects, reads the install snippet, adds allowed origins, changes widget settings, creates keys, syncs documents and makes webhooks as the signed-in staff member, within that member's role and plan. Every write is audit-logged; revoke the connection from Settings > Agents. Without a connection every skill still works with keys pasted from the dashboard.
What it sends
Nothing of its own. The plugin is instructions and small scripts that run on your machine. It holds no credentials: a connection to Opem's MCP server is an OAuth token your agent keeps, and the tool calls you ask for are the only network calls it makes to your own Opem project (plus the install check against https://support.opem.app/api/v1/widget/config). A key or secret a tool returns is shown once; write it to your own environment file, and never paste a secret key or verification secret into a chat.
Links
- Documentation: https://opem.app/docs/agents
- Privacy policy: https://opem.app/legal/privacy
- Terms: https://opem.app/legal/terms
- Support: https://opem.app/contact
This repository is published from Opem's main repository (agile-4/opem-agent-plugin is the mirror); changes made here directly are overwritten on the next release.