Feature Request: Opencode Compatibility Adapter for PAI Integration

[wallase16]

🎯 Feature Request

Create an official Opencode compatibility adapter for Daniel Miessler's Personal AI Infrastructure (PAI) to enable cross-platform AI agent support.

📋 Problem Statement

PAI currently claims platform agnosticism ("works with any AI platform") but is entirely Claude Code-dependent in practice. Opencode users cannot access PAI's powerful personal AI infrastructure due to architectural incompatibilities.

🔍 Research Findings

PAI Current Limitations:

• Hook System: Requires Claude Code's specific TypeScript hooks (initialize-pai-session.ts, update-tab-titles.ts)
• Directory Structure: Hardcoded to ~/.claude/ (Claude Code's home directory)
• Settings Format: Uses Claude Code's exclusive settings.json schema
• Skills Framework: Dependent on Claude Code's natural language routing
• MCP Integration: Designed for Claude Code's MCP implementation

Opencode Capabilities:

• Plugin System: Extensible with event hooks (tool.execute.before, event, etc.)
• Agent Framework: Primary/subagent system with tool permissions
• Configuration: JSON-based with schema validation and environment variables
• MCP Support: Comprehensive MCP server integration
• Client/Server: HTTP server architecture for universal access

No Cross-Platform Evidence:

• Zero documented cases of PAI working with non-Claude platforms
• Community discussions exclusively reference Claude Code usage
• All troubleshooting assumes Claude Code environment
• GitHub issues confirm "PAI needs Claude Code" (Discussion What should I see when finished installation to know PAI is installed. #89)

🛠️ Proposed Solution

Phase 1: Platform Abstraction Layer

Create adapters/ directory in PAI:

adapters/
├── claude-code/     # Current implementation
├── opencode/        # New adapter needed
├── gpt-cli/         # Future adapters
└── platform-agnostic/  # Common interface

Phase 2: Opencode Adapter Implementation

• Translate PAI hooks to Opencode plugin events
• Map PAI skills to Opencode agents
• Convert PAI settings to Opencode JSON format
• Bridge directory structure differences

Phase 3: Configuration Migration

• Automatic detection of Opencode environment
• Transform .claude/ structure to Opencode-compatible format
• Maintain backward compatibility with Claude Code

📊 Technical Requirements

PAI Changes Needed:

1. Platform Interface: Abstract core PAI functionality from Claude Code dependencies
2. Hook Translation: Convert TypeScript hooks to platform-agnostic events
3. Config Adapter: Transform settings between formats
4. Skill Mapping: Translate PAI skills to agent definitions

Opencode Changes Needed:

1. PAI Plugin: Official plugin to load PAI infrastructure
2. Configuration Import: Support for PAI configuration files
3. Directory Bridge: Map .claude/ to Opencode's structure
4. Skill Integration: Load PAI skills as Opencode agents

🎯 Expected Benefits

• True Platform Agnosticism: PAI works with Claude Code, Opencode, GPT, Gemini
• Larger User Base: Opencode's open-source nature expands PAI adoption
• Reduced Vendor Lock-in: Users can choose AI platform based on needs
• Community Growth: Cross-platform compatibility drives contributions

📝 Implementation Considerations

• Maintain backward compatibility with existing Claude Code integration
• Follow Opencode's plugin development guidelines
• Ensure security best practices across platforms
• Provide migration tools for existing users

🔗 Related Issues

• Contradictory definitions for PAI_DIR variable - Inconsistency in Setup Instructions #92: Contradictory definitions for PAI_DIR variable
• Automated Documentation needs human supervision #95: Automated Documentation needs human supervision
• stop-hook.ts looks for a config file in iCloud path #96: stop-hook.ts looks for config file in iCloud path

📊 Impact Assessment

High Impact: Enables PAI's mission of "AI for everyone" by supporting truly platform-agnostic operation.

[KristofStroobants]

Very interested to see if this will het some traction. Have played around with PAI but also work with Gemini and opencode. So this makes a lot of sense

[danielmiessler]

Thanks for the detailed proposal @wallase16!

Current Status: PAI is intentionally built around Claude Code for v1.0. The "platform agnostic" claim in early docs was aspirational rather than current state.

Why Claude Code first:

• Claude Code's hooks, MCP, and agent system are mature and well-documented
• Building a stable foundation is priority before adding complexity
• The skills/agents/hooks architecture is portable in concept, but implementations are platform-specific

On Platform Abstraction:
The proposal for adapters/ is interesting but premature. We first need:

1. Stable v1.0 with clear contracts (see PAI_CONTRACT.md)
2. Community adoption and feedback
3. Understanding of which features are actually portable

What Would Help:
If you're interested in Opencode compatibility:

1. Fork PAI and experiment with what translates
2. Document which PAI concepts map to Opencode equivalents
3. Share findings - this informs future architecture decisions

We've updated the README to clarify that PAI is currently built on Claude Code. True platform agnosticism may come later, but isn't a v1.0 priority.

Keeping this open as a feature request for future consideration.

— Kai 🤖

[danielmiessler]

Closing as acknowledged feature request.

This is a thoughtful proposal for Opencode compatibility. While not currently on the roadmap, the modular architecture of PAI (skills, hooks, agents) should make such an adapter feasible as a community contribution.

Key considerations noted:

• LLM abstraction layer
• Skill/workflow portability
• Hook translation

If someone wants to pursue this, the skill structure documented in skills/CORE/SKILL-STRUCTURE-AND-ROUTING.md would be the starting point.

[wallase16]

I am working on suggested solution, and as soon as I work out the kinks I will be sharing my findings.

[erskingardner]

@wallase16 any progress on this?