Plugin API 1.0
PySH v1 provides a stable extension boundary for trusted local Python plugins. Trusted plugins run inside the PySH process and are enabled explicitly. A separate manifest-driven subprocess runtime defines bounded IPC, capability grants, and resource budgets for isolated plugins.
Read Plugin DocsA Trusted Plugin
Trusted Plugin API 1.0 plugins are trusted Python code. Enabling one allows it to execute inside the PySH process with the current user's authority. The Plugin API is not a sandbox.
class ExamplePlugin:
name = "example"
version = "0.1.0"
api_version = (1, 0)
def register(self, api):
api.register_command("hello", self.hello)
def hello(self, argv):
print("hello from plugin")
return 0
def configure(shell):
shell.enable_plugin("example")
What PySH v1 Ships
Trusted Plugin API 1.0
Versioned in-process extension API for explicitly enabled local Python plugins.
Explicit Enablement
Plugin files do not execute merely because they exist. User and project-local plugin loading is opt-in.
Stable Registration Surface
Commands, completers, prompt segments, and lifecycle hooks are registered through the documented Plugin API.
Isolated Plugin Runtime
Separate subprocess architecture with bounded IPC, parent-mediated capability grants, resource budgets, and structured diagnostics.
Process isolation is not an operating-system sandbox. A same-user child retains the operating system's own authority unless the OS independently restricts it.
What PySH v1 Does Not Claim
- ✕No built-in online plugin marketplace.
- ✕No automatic plugin installation.
- ✕No automatic network lookup of plugins.
- ✕No official Git/Docker/Kubernetes/AWS plugin catalog in v1.0.0.
- ✕No claim that isolated plugins provide OS-level sandboxing.
Read the Plugin API Documentation
The documentation covers the plugin class, explicit enablement, and the isolation boundary. Academy Track 4 offers learning material for plugin development.