What technical users can inspect
MSOCK ships the `sock` CLI as the engine behind SOCK and drives it on your behalf. Its read-only diagnostic commands can help support teams inspect the installed capabilities and harness state. The CLI is not a supported public automation or integration interface.
An add-on pack standard exists and is used internally and by a small number of existing authors, but it is not a documented, supported public developer platform.
What is not a public contract
| Surface | Current status |
|---|---|
| REST API | No supported public API. The backend and any auto-generated pages are not an integration contract |
| SDK | No published, supported package for external applications |
| Connector framework | Curated internally; no public third-party connector workflow |
| Desktop plugins | No extension point for third-party code |
| Add-On Market | The end-user portal is not available in this release; add-on lifecycle operations are restricted to platform administration and controlled authoring workflows |
Where the engine lives
The engine is installed per user, outside your project folders, and MSOCK keeps it up to date with the application. You do not install or upgrade it yourself, and you should not delete it while a session is running.
An installed engine declares what it can do:
sock capabilities --jsonThe application uses that declaration to decide whether the engine on a machine is compatible with the application build, and refuses to start sessions rather than failing command by command.
Safe diagnostic starting points
sock --help
sock status --capture cap-...
sock capabilities --json