jmagar Bootstrap Plexus
Use this skill before first use of Plexus, after plugin install/upgrade, or when the user asks to repair missing host profiles.
Dynamic Bootstrap
This initializes missing persistent profiles from bundled templates. It never
overwrites existing REMOTE.md files. In Claude Code, the dynamic command below
is executable skill syntax. In Codex/OpenAI contexts, run the same shell command
with exec_command.
!python3 "${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-plugins/plexus}}/scripts/remote-context.py" --init $ARGUMENTS
Persistent Data Contract
Plexus must not store mutable host memory in the plugin source tree. Bundled
files under ${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-plugins/plexus}}/templates/remotes/ are
defaults only.
Persistent host profiles live at:
${CLAUDE_PLUGIN_DATA}/remotes/<host>/REMOTE.md
During local development outside an installed plugin, the fallback is:
~/.plexus/remotes/<host>/REMOTE.md
The user can override this with PLEXUS_DATA_DIR or --data-dir.
After Bootstrap
Report the data directory and any profiles seeded. If a profile already exists, leave it untouched and tell the user it was preserved.
To inspect a seeded profile:
python3 "${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-plugins/plexus}}/scripts/remote-context.py" <host> --no-probe