Plugins

Optional by design.

The base shell stays focused. Plugins add interfaces, hooks, and profiles without becoming permanent core behavior.

Explore the registry

The public registry includes UI surfaces, harness hooks, profiles, and theme hooks. The complete current roster and its capability contracts live in the Plugin System documentation.

aphotic plugin list --remote
aphotic plugin list --remote --refresh
aphotic plugin install <name>

The catalogue caches to disk after the first fetch, so listing stays fast as the registry grows. Pass --refresh to fetch it again.

Components and descriptors

The components plugins build on stay stable. Interact is the current component for hover and press. StateLayer stays for compatibility and wraps Interact, so plugins written against it keep loading.

A plugin declares an agent harness with a [harness.<id>] table in its manifest, and a drop-in at ~/.config/aphotic/harnesses/<id>.toml overrides a manifest descriptor or adds a harness of your own. aphotic agent harnesses merges both sources. The engine capability works the same way for inference engines, with an [engine] block and drop-ins at ~/.config/aphotic/engines/<id>.toml; descriptors are parsed and validated, and the surfaces that consume them come later.

Shelf tab contracts

The Sonar and Shelves feature under review adds edge tabs with output placement and lifecycle gates. See the plugin contract and controls.