Repository navigation
SeniorOS 0.8.0
SeniorOS as an OpenCode plugin, and a guard that also protects the settings, hooks and plugins of the host it runs in.
Added
-
OpenCode 1.x plugin. Add
"plugin": ["senioros"]toopencode.jsonand restart OpenCode. The plugin:- registers the
senior-*skills; - adds the routing rules to the system prompt;
- fails destructive
bashcalls. OpenCode's tool hook cannot ask, so the agent shows what would be lost and lets the user run the command; - runs the finish gate when a session goes idle, and sends failing checks back to the session.
- registers the
-
The guard protects the agent's own configuration. An agent that could rewrite these files could switch SeniorOS off:
Host Protected files Claude Code .claude/settings*.json,.claude/plugins/Codex .codex/config.toml,hooks.json,plugins/Cursor .cursor/hooks.json,plugins/OpenCode opencode.json, plugin foldersAntigravity .geminihooks and rulesCoverage:
- Shell commands that change these files need confirmation, including quoted scripts and command substitutions.
- The file-edit tools of Claude Code, Codex (
apply_patch) and OpenCode are covered too. - Cursor and Antigravity have no hook before a file edit, so there only shell commands are covered.
Fixed
- The finish gate tells the agent to stay within what the user asked. The second time it sends the agent back for unchanged code, it tells the agent to repeat its explanation and stop. Before, in OpenCode, an agent sent back twice edited a test the user had said not to touch.
Verified
In OpenCode 1.14.34 on Windows:
- the guard blocked
git reset --hardand an edit toopencode.json; - the finish gate sent the agent back on a failing test;
- with the new wording, the agent kept its explanation and changed nothing it was told not to touch (one run).
Not yet tested in the host: the Claude Code Edit and Codex apply_patch protection, OpenCode 1.2, macOS and Linux.
Install
- OpenCode:
{ "plugin": ["senioros"] }inopencode.json - CLI:
npm install -g senioros@0.8.0