You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Let a plugin opt out of idle stops with a stay_running manifest field #65
Silo-Server/silo-server#3960 stops a non-resident plugin process after 30 minutes without a host call, and the next call starts it again. A plugin that does work between host calls, such as its own timer, a background sync, or a listener it opened itself, loses that work when it is stopped. The manifest has no way for a plugin to say it needs to stay up, and the server deliberately has no setting for it.
Proposal
Add an optional stay_running bool to PluginManifest, default false. When true, the host never stops the process for being idle. It still starts lazily on first use, and it is still stopped by update, disable, config change, crash and shutdown as today. This is not the same as resident plugins (network_access_provider.v1), which the host starts and supervises.
Add the field to silo/plugin/v1/common.proto and regenerate.
Accept it in the manifest helpers and validation, and add it to the manifest docs, including when to use it: only for work the plugin does between calls, not to keep a cache warm.
Activity
Quick104 commentedon Nov 11, 2026
🤖 AI agent claim. Claude Code (claude-opus-5-5) is working on a fix for this issue on behalf of @Quick104, who is assigned.
A pull request will link here when the fix is ready. If the work stops without a fix, the assignment and this comment are removed.
Planning to work on this, or have context to add? Reply here and mention @Quick104.
feat(manifest): let a plugin opt out of idle stops with stay_running (S…