Files
John SmithandClaude Opus 5.5 3a6d104fcf chore(data): backfill kind, topics and compat for every entry; follow renamed repos
- kind/topics: keyword first pass, then reviewed and corrected by hand for all 513 entries
- compat: detected from npm packages, package.json and source (scripts/utils/compat.js). Plugins: 134 v2, 125 v1, 12 unverified; 13 entries the review loop marked V2 pin @opencode-ai/plugin 1.x, and ~20 loop V2 verdicts based only on the absence of V1 markers are V1 plugin functions in source
- npm and path filled where verifiable (package repository matches the entry); 9 bogus npm values from install prose were not kept
- 29 repo URLs updated to the renamed/transferred repository; xberg-io entries point at their live repos instead of the archived monorepo; lavi uses repo + path instead of a /tree/ URL
- removed projects/opencode-sessions.yaml (same repo as plugins/opencode-sessions.yaml)
- install: renamed to installation:, mojibake fixed, inline HTML links removed from two descriptions

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-17 13:00:22 -04:00

9 lines
901 B
YAML

name: Stay Awake
repo: https://github.com/AuroraAeon/opencode-stay-awake
tagline: Keep the computer awake only while a session is generating
description: Long agent runs (model streaming, tool execution, compaction, rate-limit retries) routinely take minutes with no user input, and default OS power settings treat that as idle and suspend mid-prompt. This plugin holds a system sleep inhibitor for exactly as long as any session is generating, then releases it — caffeinate -dims -w <server pid> on macOS, systemd-inhibit on Linux, no-op elsewhere. Busy detection is event-driven rather than polling, so a tool call that runs for minutes keeps its work item open instead of being released mid-run. Every inhibitor is bound to the server pid and a stale cap bounds any lost end event, so the machine can never be wedged awake. Zero dependencies, MIT.
kind: plugin
topics:
- environment
compat: v2