Integrations

28 platforms, one protocol

OSOP integrates with AI coding agents, workflow orchestrators, agent frameworks, and design tools. Bidirectional converters for 6 formats, native plugins for the big three, drop-in rules for eleven more.

terminal

$ git clone https://github.com/Archie0125/osop-agent-rules.git
$ cd osop-agent-rules
$ ./install.sh          # auto-detects your tools
$ ./install.sh --all    # install for all 18 platforms
$ ./install.sh --list   # preview what would be installed

The installer checks for config directories (.cursor/, .windsurf/, etc.) and only installs for tools you have. Never overwrites existing files unless --force is passed.

Tier 1

Native integrations

First-class support with dedicated plugin systems, skill registries, or protocol-level integration.

Claude Code

Native Plugin · 5 slash commands

Live

OSOP ships as a native Claude Code plugin with 5 slash commands: /osop-log records sessions, /osop-report generates HTML reports, /osop-review runs security analysis, and /osop-optimize improves workflows from execution history. The plugin also includes a SessionEnd hook that auto-generates logs after significant work.

claude /install-plugin https://github.com/Archie0125/osop-skill

OpenClaw

ClawHub Registry · 5 published skills

Live

5 OSOP skills published on ClawHub — OpenClaw's community skill marketplace with 13,000+ skills. Each skill follows ClawHub metadata format with proper metadata.openclaw.requires declarations. Install individually or all at once.

clawhub install osop
clawhub install osop-log
clawhub install osop-report
clawhub install osop-review
clawhub install osop-optimize

GitHub Copilot

MCP Server · 9 tools exposed

Live

OSOP exposes 5 tools via the Model Context Protocol (MCP): validate, render, report, diff, and risk_assess. Any MCP-compatible client — Copilot, Cursor, Claude Desktop — can use OSOP tools natively without any custom integration.

pip install osop-mcp

Tier 2

Drop-in rule files

Every AI coding agent reads markdown instruction files — the only difference is the filename and directory. Copy one file and OSOP works.

Platform	File Location	Install
Cursor	.cursor/rules/osop-session-logging.mdc	`./install.sh --cursor`
OpenAI Codex	AGENTS.md (project root)	`./install.sh --codex`
Windsurf	.windsurf/rules/osop-session-logging.md	`./install.sh --windsurf`
Continue.dev	.continue/rules/osop-session-logging.yaml	`./install.sh --continue`
Aider	CONVENTIONS.md (project root)	`./install.sh --aider`
Cline	.clinerules/osop-session-logging.md	`./install.sh --cline`
Roo Code	.roo/rules/osop-session-logging.md	`./install.sh --roo-code`
Devin	playbooks/osop-session-logging.md	`./install.sh --devin`
Zed	.rules (project root)	`./install.sh --zed`
Sourcegraph Amp	AGENT.md (project root)	`./install.sh --amp`
Trae	project_rules.md (project root)	`./install.sh --trae`

How it works under the hood

Every AI coding agent reads markdown files for custom instructions. Cursor reads .cursor/rules/*.mdc, Windsurf reads .windsurf/rules/*.md, Codex reads AGENTS.md. The core instructions are identical across all platforms — only the filename and directory differ. This is why OSOP uses a single-source architecture: one CORE-INSTRUCTIONS.md with thin platform-specific wrappers.

Tier 3

Config-based integrations

Tools with custom configuration systems that support OSOP through their native config format.

Obsidian

Integrates via Obsidian Copilot's custom prompt system. Place the OSOP prompt in .obsidian/copilot-custom-prompts/ and the AI assistant gains workflow logging capabilities.

./install.sh --obsidian

PearAI

Add OSOP as a custom slash command in PearAI's config.json. Users invoke /osop-log to generate structured session records after completing work.

Add to config.json

Sweep AI

Uses the Claude Skills format (.claude/skills/SKILL.md) in JetBrains IDEs. OSOP provides a pre-built SKILL.md for immediate integration.

./install.sh --sweep

Heptabase

Integrates with Heptabase's AI assistant through custom prompt templates. Place OSOP instructions in your workspace and the AI gains structured workflow logging for research sessions and knowledge mapping.

./install.sh --heptabase

SWE-agent

Configured via YAML config files with a system_template directive. OSOP provides a ready-to-use config that injects session logging instructions.

./install.sh --swe-agent

Notion

Integrates with Notion's AI and automation features. Define OSOP workflows as Notion database templates — each workflow step becomes a page with properties for status, assignee, and timing. Use Notion API automations to trigger workflow transitions.

./install.sh --notion

Canva

Integrates with Canva's design workflow through Apps SDK. OSOP templates define creative review pipelines — from brief to draft to approval — with structured handoffs between designers, reviewers, and stakeholders.

./install.sh --canva

Figma

Integrates with Figma's plugin API and FigJam. OSOP workflows map design processes — user research, wireframe, prototype, review — as structured nodes. Use FigJam boards to visualize the workflow alongside design artifacts.

./install.sh --figma

All integration files are open source and available on GitHub.

View on GitHub Getting Started