Extensions for Silo

Install from the app (Settings → Extensions), or from a shell: silo install <id>

Agent Monitor v0.2.11
silo.agent-monitor

At-a-glance agent status in the Workspaces panel: rows for coding agents that are working or finished and need attention, cleared when you view the terminal.

849 ↓
Documents Side Panel v0.1.5
silo.docs-panel

Browse and preview markdown documentation from configurable folder roots.

fs:read 841 ↓
Follow-ups v0.2.2
silo.follow-ups

Mark editor and terminal tabs to come back to later — toolbar Flag toggle, tab chip, and a Workspaces panel rollup.

600 ↓
GitHub Actions v0.1.21
silo.github-actions

Monitor GitHub Actions workflow runs across workspace repos — status bar, workspace badges, and failure notifications.

process 852 ↓
GitHub Issues v0.1.5
silo.github-issues

GitHub issues for workspace repos in a side panel — status, labels, assignees, and drill-in details, with quick copy for handing work to an agent.

process 649 ↓
GitHub Pull Requests v0.1.17
silo.github-prs

GitHub pull requests for workspace repos in a side panel — review state, CI checks, and drill-in details at a glance.

process 769 ↓
Local Web Viewer v0.1.6
silo.local-web-viewer

Embed local dev servers and file:// pages as dock panels alongside your code.

webview 836 ↓
Skills Manager v0.1.2
silo.skills-manager

Agent Skills side panel — inventory of project + user installs, with a dock-anchored sheet to browse and install from skills.sh.

fs:readnetwork 23 ↓
System Monitor v0.3.5
silo.system-monitor

Live CPU and memory charts in a side panel and status bar — cross-platform (macOS, Linux, Windows).

processfs:read 862 ↓

Extension questions

How do I install an extension?

From the app: Settings → Extensions → Browse. From a shell: silo install <id>. Every install shows a permission prompt first — extensions run unsandboxed, so only install ones you trust.

How do I publish an extension?

Register it once via the publish form, then cut a GitHub release with the built package. See Publishing an extension for the full walkthrough.

How does the registry work?

It's a git-backed index, not a service — every publish is a commit, so the history is a public audit log. See RFC 0014 for the design.

Found a problem with an extension?

Open an issue on the registry repo — publishers and maintainers triage from there.