yigitkonur/plugin-kernel-sh

two claude code plugins for kernel cloud browsers. pick the one that matches what you're doing, or install both:
| plugin | for when | what it gives you |
| kernel-browser | claude code should use a cloud browser: browse, read, fill forms, act on sites you're logged in to, without running chrome on your laptop | the kernel mcp server, skills for browsing, logging in (hosted page, live view, 1password) and cleaning up, and hooks that tag, track and delete every browser a session creates |
| kernel-dev | you're writing code that uses kernel (typescript, @onkernel/sdk, the kernel cli) | a live-tested knowledge skill, debugging, login, audit and site-profiling workflows, and hooks that catch deprecated fields and leaked api keys |
the facts in here were checked against @onkernel/sdk, the kernel cli, the kernel mcp server's source and live runs on a real account (receipts: verified-facts.md). anything that wasn't run live says "(unverified)" or "(untested)" right in the text.
## install
Every plugin of ours is installed once, globally, and off, then turned on per project. Nothing runs and no tokens are spent in chats that don't switch it on. It works the same in Claude Code and Codex.
### 1. install them globally
Claude Code
sh
claude plugin marketplace add yigitkonur/plugin-kernel-sh
claude plugin install kernel-dev@plugin-kernel-sh -s user # stays off: defaultEnabled is false in the manifest
claude plugin install kernel-browser@plugin-kernel-sh -s user
Codex (0.163+)
sh
codex plugin marketplace add yigitkonur/plugin-kernel-sh
codex plugin add kernel-dev@plugin-kernel-sh
codex plugin add kernel-browser@plugin-kernel-sh
codex-plugin-project.sh global-off kernel-dev@plugin-kernel-sh # Codex has no enable/disable command; this keeps it off everywhere
codex-plugin-project.sh global-off kernel-browser@plugin-kernel-sh
All our plugins, both hosts, plus the plugin command and the 6-hourly update job, in one line:
sh
curl -fsSL https://raw.githubusercontent.com/yigitkonur/plugin-kit/main/install.sh | sh -s -- --all
### 2. turn them on in a project
sh
cd your-project
plugin on kernel-dev # Claude Code and Codex, this folder only
plugin off kernel-dev # undo
plugin # or pick from a list (TUI)
By hand, without the plugin command:
sh
claude plugin enable kernel-dev@plugin-kernel-sh --scope project # undo: claude plugin disable kernel-dev@plugin-kernel-sh --scope project
claude plugin enable kernel-browser@plugin-kernel-sh --scope project # undo: claude plugin disable kernel-browser@plugin-kernel-sh --scope project
codex-plugin-project.sh on kernel-dev@plugin-kernel-sh . --trust # undo: codex-plugin-project.sh off kernel-dev@plugin-kernel-sh
codex-plugin-project.sh on kernel-browser@plugin-kernel-sh . --trust # undo: codex-plugin-project.sh off kernel-browser@plugin-kernel-sh
Restart claude / codex in that folder afterwards.
Codex reads a folder's .codex/config.toml only when the folder is trusted; --trust adds that, and it also enables the folder's hooks and rules, so use it for your own projects only. plugin and codex-plugin-project.sh come from plugin-kit (the one-line installer above).
### 3. updates
A plugin updates only when its version changes, and this repo's release workflow bumps it on every shipped change. Machines pick it up with plugin update, or by themselves with the 6-hourly job (plugin autoupdate install). By hand: