@kolisachint/hoocode-agent 0.5.28 → 0.5.30

package/docs/plugins.md

@@ -107,8 +107,9 @@ Then package for distribution:
 
 ## Model-facing tools
 
-When plugin tooling is enabled (`--enable-plugintools`, or the
-`enablePluginTools` setting), the model gets its own lifecycle tools rather than
+When plugin tooling is enabled (`--enable-plugintools`, the `enablePluginTools`
+setting, or `/settings` under **Plugins**), the model gets its own lifecycle
+tools rather than
 going through the slash command: `SearchPlugins`, `ListPlugins`,
 `SuggestPluginInstall`, `InstallPlugin`, `UninstallPlugin`, `UpdatePlugin`,
 `ProposePlugin`, `RemovePluginCapability`, and `PackagePlugin`.

package/docs/settings.md

@@ -101,6 +101,27 @@ Set `HOOCODE_SKIP_VERSION_CHECK=1` to disable the HooCode version update check.
 }
 ```
 
+### Context budget
+
+Everything in the system prompt and in an active tool's schema is re-sent on
+every request. These three settings decide how large that is, and `/settings`
+groups them under **Context** with the live per-turn cost printed under the
+list.
+
+| Setting | Type | Default | Description |
+|---------|------|---------|-------------|
+| `light` | boolean | `false` | Low-token preset: `read`/`write`/`edit`/`bash` only with stripped schemas, a terse system prompt, and no subagents/TodoWrite/skills/context files |
+| `contextGc` | boolean | `true` | Stub superseded read results out of the outgoing context |
+
+`light` is read at startup to pick the tool set and the system prompt, so
+toggling it in `/settings` applies on the next session. `--light` turns it on
+for a single run. Auto-compaction lives in the same category and is documented
+under [Compaction](#compaction).
+
+`/settings` also prices each tool by what its schema costs per turn, on the
+switch itself, so it is clear which one is worth turning off. `hoocode
+--print-token-surface` prints the same measurement as text.
+
 ### Branch Summary
 
 | Setting | Type | Default | Description |
@@ -222,6 +243,49 @@ narrowing the window to nothing. As with all settings, a project
 `.hoocode/settings.json` overrides the global one, so a repo can carry its own
 window.
 
+### Plugins and artifacts
+
+Where hoocode writes what it authors. Both are editable from `/settings` under
+**Plugins**, which writes the global settings file — the layout a machine
+targets is an environment-level choice, so it is set once rather than passed on
+every run.
+
+| Setting | Type | Default | Description |
+|---------|------|---------|-------------|
+| `enablePluginTools` | boolean | `false` | Master switch for the autonomous plugin system: the lifecycle tools, `ProposePlugin`, and the plugin-reuse nudge |
+| `platform` | string \| string[] | - | Vendor layout(s) to write artifacts in: `claude`, `github` (aliases `copilot`, `gh`), `agents` (alias `native`) |
+| `pluginInstallScope` | string | `"user"` | Where an autonomous plugin install lands: `user` (`~/.agents/plugins`) or `project` (`<cwd>/.agents/plugins`, shared once committed) |
+
+```json
+{ "enablePluginTools": true, "platform": ["claude", "github"], "pluginInstallScope": "user" }
+```
+
+`/settings` writes the global file. If a project `.hoocode/settings.json` sets
+one of these keys it is merged over that on the next session, so the pane marks
+the row as overridden rather than letting the change look permanent.
+
+`enablePluginTools` is off by default and is the one gate for the whole
+autonomous system — see [Plugins](plugins.md). Toggling it in `/settings`
+attaches the tools on the next session, since they are wired up when the session
+is built; the reuse nudge re-reads the setting and follows immediately. The
+`--enable-plugintools` flag turns it on for a single run. Slash-command plugin
+management (`/plugin`) is unaffected either way.
+
+`platform` governs the two things hoocode *writes*: authored plugins, and the
+`/new-skill`, `/new-agent` and `/new-command` scaffolds. Reading is unaffected —
+every vendor convention is read regardless of this setting.
+
+It takes a list because emitting for two platforms at once is a supported shape;
+in `/settings` the three tokens are independent toggles for that reason.
+Unsetting it (all toggles off) is not the same as targeting nothing: the
+defaults come back, which are `claude` for an authored plugin and `.hoocode/`
+for a scaffold. `agents` is a scaffold-only target — a plugin is a distribution
+unit and the native layout belongs to no marketplace — so plugin authoring
+filters it out rather than failing.
+
+The `--platform` CLI flag sets the same targets for a single run and overrides
+this setting.
+
 ### Model Cycling
 
 | Setting | Type | Default | Description |

package/docs/usage.md

@@ -371,9 +371,9 @@ hoocode --no-extensions -e ./my-extension.ts
 
 #### Light mode
 
-`--light` (or the `light` setting) trims the session to the smallest useful
-fixed per-turn surface, for small or local models that waste context on harness
-boilerplate:
+`--light` (or the `light` setting, editable in `/settings` under **Context**)
+trims the session to the smallest useful fixed per-turn surface, for small or
+local models that waste context on harness boilerplate:
 
 - Only `read`, `write`, `edit`, and `bash`, with short descriptions and stripped
   parameter schemas. `bash` subsumes grep/find/ls — search happens via the shell.

package/examples/extensions/custom-provider-anthropic/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-custom-provider-anthropic",
 	"private": true,
-	"version": "0.3.28",
+	"version": "0.3.30",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/examples/extensions/custom-provider-gitlab-duo/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-custom-provider-gitlab-duo",
 	"private": true,
-	"version": "0.3.28",
+	"version": "0.3.30",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/examples/extensions/sandbox/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-sandbox",
 	"private": true,
-	"version": "0.3.28",
+	"version": "0.3.30",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/examples/extensions/with-deps/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@kolisachint/hoocode-extension-with-deps",
 	"private": true,
-	"version": "0.3.28",
+	"version": "0.3.30",
 	"type": "module",
 	"engines": {
 		"bun": ">=1.0.0"

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@kolisachint/hoocode-agent",
-	"version": "0.5.28",
+	"version": "0.5.30",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"hoocodeConfig": {
@@ -49,9 +49,9 @@
 		"prepublishOnly": "npm run clean && npm run build"
 	},
 	"dependencies": {
-		"@kolisachint/hoocode-agent-core": "^0.5.28",
-		"@kolisachint/hoocode-ai": "^0.5.28",
-		"@kolisachint/hoocode-tui": "^0.5.28",
+		"@kolisachint/hoocode-agent-core": "^0.5.30",
+		"@kolisachint/hoocode-ai": "^0.5.30",
+		"@kolisachint/hoocode-tui": "^0.5.30",
 		"@silvia-odwyer/photon-node": "^0.3.4",
 		"chalk": "^5.5.0",
 		"cli-highlight": "^2.1.11",