@oked/claude-code 0.6.25 → 0.6.27

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -18,7 +18,7 @@ oked init
18
18
 
19
19
  `oked init` writes a `PreToolUse` hook into the current project's `.claude/settings.json`, opens the device-pairing page in your browser, and stores the API key in `~/.oked/config.json`. Open a new Claude Code session in that project.
20
20
 
21
- You can also install OKed as a Claude Code plugin, with no global npm install. In Claude Code run `/plugin marketplace add oked-ai/oked-sdk`, then `/plugin install oked@oked`, then `/oked:pair`. The plugin ships the hook as one file and reads the API key from the plugin configuration (`CLAUDE_PLUGIN_OPTION_APIKEY`). Until you pair, a risky action returns `ask`. See [plugins/claude-code](../../plugins/claude-code).
21
+ You can also install OKed as a Claude Code plugin, with no global npm install. In Claude Code run `/plugin marketplace add oked-ai/oked-sdk`, then `/plugin install oked@oked`, then `/oked:pair`. The plugin ships the hook as one file. It reads the API key only from the plugin API key field (`CLAUDE_PLUGIN_OPTION_APIKEY`). While that field is empty, a risky action returns `ask`. An optional GitHub token field fills pull request titles. The plugin does not approve a tool call: an approval leaves the decision to Claude Code's normal permission flow. The settings hook in this package still returns an explicit allow. See [plugins/claude-code](../../plugins/claude-code).
22
22
 
23
23
  If the plugin is enabled, `oked init` does not add a settings hook. If both are already installed, the plugin gates and the settings hook stands down, so the action is asked once. `oked uninstall` removes the project settings entry. Turning the plugin off makes that entry gate again.
24
24
 
@@ -51,9 +51,9 @@ The hook uses a four-tier classifier. Classification is effect-based: it detects
51
51
 
52
52
  A Bash command that matches none of those effect categories defaults to `safe`. Cloud CLI reads (`aws s3 ls`, `kubectl get`, `terraform plan`), `--help`, and dry runs are `safe`. Running a command is not, by itself, a reason to interrupt you. Unknown tools that are not Bash default to `review`. MCP tools named `delete_*`, `drop_*`, or `remove_*` are `high_stakes`.
53
53
 
54
- `bash -c`, `sh -c`, `powershell -Command`, `pwsh -c`, and `cmd /c` are classified by the command inside them. A broken `\"` on a recursive delete asks even when the text names `node_modules`, a build directory, or a temp folder. That quoting is how a cleanup became a drive-root delete on Windows.
54
+ `bash -c`, `sh -c`, `powershell -Command`, `pwsh -c`, and `cmd /c` are classified by the command inside them. A parenthesis subshell, a brace group, a loop or `if` body, and a command substitution inside double quotes are classified by the inner command too. A broken `\"` on a recursive delete asks even when the text names `node_modules`, a build directory, or a temp folder. That quoting is how a cleanup became a drive-root delete on Windows.
55
55
 
56
- Deleting only a temp directory (`/tmp/foo`, `$env:TEMP\foo`, `%TEMP%\foo`) or a build output directory (`build`, `dist`, `.next`) stays `warning`. `rmdir` of an empty folder stays `warning`. `git clean -n` and `Format-Volume -WhatIf` stay `safe`.
56
+ Deleting only a temp directory (`/tmp/foo`, `$env:TEMP\foo`, `%TEMP%\foo`), a build output directory (`build`, `dist`, `.next`), or a relative `node_modules` path (`node_modules`, `backend/node_modules`) stays `warning`. `rm -rf /abs/node_modules`, `rm -rf $X/node_modules`, and `rm -rf ../node_modules` still ask. `rmdir` of an empty folder stays `warning`. `git clean -n` and `Format-Volume -WhatIf` stay `safe`.
57
57
 
58
58
  ### Subagents, PowerShell, and commands the hook cannot see
59
59
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@oked/claude-code",
3
- "version": "0.6.25",
3
+ "version": "0.6.27",
4
4
  "description": "OKed for Claude Code - zero-code human approval for sensitive actions",
5
5
  "type": "module",
6
6
  "bin": {
@@ -44,8 +44,8 @@
44
44
  "access": "public"
45
45
  },
46
46
  "dependencies": {
47
- "@oked/hook-core": "0.6.25",
48
- "@oked/sdk": "0.6.25"
47
+ "@oked/hook-core": "0.6.27",
48
+ "@oked/sdk": "0.6.27"
49
49
  },
50
50
  "devDependencies": {
51
51
  "typescript": "^7.0.2"