Skip to content

WIP: add trusted custom plugin harness#1

Open
JMidoro wants to merge 1 commit into
PsycherosAI:mainfrom
JMidoro:codex/custom-plugin-harness
Open

WIP: add trusted custom plugin harness#1
JMidoro wants to merge 1 commit into
PsycherosAI:mainfrom
JMidoro:codex/custom-plugin-harness

Conversation

@JMidoro
Copy link
Copy Markdown

@JMidoro JMidoro commented Jun 1, 2026

Summary

Adds a trusted, in-process custom plugin harness so local extensions can survive upstream updates without requiring forks. Plugins can extend Psycheros prompt construction, tools, routes, browser assets, and lifecycle hooks, while entity-core plugins can add MCP tools and additive result decorators.

Plugin-owned credentials live outside portable backups under .psycheros/plugin-secrets/<id>.env. The shared plugin API includes validation, isolated test fixtures, focused coverage, and a manual-install validator.

Affected packages

  • packages/psycheros
  • packages/entity-core
  • packages/entity-loom
  • packages/launcher
  • Workspace root / CI / docs

Also updates packages/launcher-v2 backup warnings and rollback-preservation coverage.

Checklist

  • deno check passes for the affected entry points
  • deno lint passes
  • deno fmt --check passes
  • First-person convention preserved in any new prompts / comments / docs
  • If a behavior changed, the relevant docs/ or CLAUDE.md is updated
  • If a new external dependency was added, it's justified in the description

No new external dependency was added. The shared API uses the existing hoisted @std/dotenv dependency.

Related issues

@JMidoro JMidoro changed the title add trusted custom plugin harness WIP: add trusted custom plugin harness Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant