Create ReCursor-Plugins Repository for Extensions and Integrations #3
Description
Overview
Establish a separate repository for ReCursor plugins, extensions, and integrations with external coding agents, maintaining the modular architecture defined in architecture/overview.md.
Background
Per architecture/overview.md, ReCursor supports multiple integration paths:
| Integration | Status | Use Case |
|---|---|---|
| Claude Code Hooks | ✅ Supported | Event observation (one-way) |
| Agent SDK | ✅ Supported | Parallel agent sessions |
| MCP | ✅ Supported | Tool interoperability |
A plugins repository would extend this to support additional coding agents and custom tooling.
Goals
- Keep core ReCursor mobile app (
apps/mobile/) focused on UI and Bridge connection - Enable modular integrations with other AI coding agents
- Maintain clear separation between core and community contributions
- Follow existing project structure conventions (per project-structure.md)
Scope
Based on research.md findings, potential integrations include:
| Agent | Stars | Integration Approach |
|---|---|---|
| OpenCode | ~122K | WebSocket bridge (similar pattern) |
| Aider | ~42K | Git-native, CLI pass-through |
| Goose | ~33K | MCP extensibility |
| Cline | ~59K | Human-in-the-loop approvals |
Package Types
| Type | Description | Example |
|---|---|---|
| Agent Adapter | Connect ReCursor to different coding agents | recursor-opencode-adapter |
| Tool Extension | Additional tools for Agent SDK sessions | recursor-deploy-tool |
| UI Theme | OpenCode-style UI customizations | recursor-theme-dark |
| Notification Handler | Custom push notification patterns | recursor-slack-notifier |
Naming Convention
All packages MUST use the recursor- prefix for discoverability:
recursor-<type>-<name>
Examples:
├── recursor-adapter-opencode
├── recursor-adapter-aider
├── recursor-tool-deploy
└── recursor-theme-midnight
Proposed Repository Structure
ReCursor-Plugins/
├── adapters/
│ ├── recursor-adapter-opencode/
│ ├── recursor-adapter-aider/
│ └── recursor-adapter-goose/
├── tools/
│ └── recursor-tool-deploy/
├── themes/
│ └── recursor-theme-midnight/
├── templates/
│ └── plugin-template/ # Starter kit for new plugins
└── README.md
Deliverables
- Define plugin/adapter interface contract (align with bridge-protocol.md)
- Create
ReCursor-Pluginsrepository under RecursiveDev org - Establish contribution guidelines (reference CONTRIBUTING.md)
- Create plugin template repository
- Document adapter patterns for multi-agent support (reference agent-sdk.md)
Principles
- Modularity — Each adapter is independently versioned
- Bridge Compatibility — All adapters work with ReCursor Bridge Server (per bridge-protocol.md)
- OpenCode UI Consistency — Extensions must not break OpenCode-style UI patterns
Constraints
From AGENTS.md:
Claude Code Remote Control is first-party only. Do not claim we can join/mirror a user's Claude Code Remote Control session unless official docs explicitly provide it.
Plugins must only use supported integration mechanisms: Hooks, Agent SDK, MCP.
Related
- Architecture: architecture/overview.md
- Integration docs: integration/
- Bridge protocol: bridge-protocol.md
- Research: research.md