@kimbho/kimbho-cli 0.1.6 → 0.1.7
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.
- package/README.md +2 -0
- package/dist/index.cjs +564 -99
- package/dist/index.cjs.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -84,10 +84,12 @@ When resuming the current saved session, that saved session context is also inje
|
|
|
84
84
|
After the agent changes workspace state, it now has to pass a verification step before the task can finish.
|
|
85
85
|
If verification fails, Kimbho forces a repair pass before the next rerun and blocks the task after the configured repair budget is exhausted.
|
|
86
86
|
If a non-debugger specialist burns through that budget, Kimbho automatically hands the task to `test-debugger` and keeps the same task id/dependency chain intact.
|
|
87
|
+
The tool layer now enforces the configured sandbox and approval policy for high-risk actions: read-only sandboxes reject mutating tools, and destructive shell commands like `rm -rf` or `git reset --hard` are blocked under manual approval mode.
|
|
87
88
|
When the workspace is a git repository with a valid `HEAD`, specialist tasks now run in isolated git worktrees and Kimbho reapplies the resulting diff back to the main workspace.
|
|
88
89
|
If multiple specialist tasks are ready at the same time, Kimbho now schedules them concurrently in separate worktrees and surfaces their diff integration live in the shell.
|
|
89
90
|
Those concurrent integrations are now serialized, so overlapping edits do not race generic patch application anymore.
|
|
90
91
|
If a direct integration fails, Kimbho now replays the specialist diff on top of the latest workspace snapshot in a retry sandbox, reapplies a refreshed patch when that drift is mergeable, and preserves the original patch artifact when it is not.
|
|
92
|
+
When the replay path still cannot land, Kimbho now writes an integration-conflict bundle with the relevant patch paths, conflicting files, failure output, and operator next steps.
|
|
91
93
|
Kimbho also has managed background process tools and live HTTP verification: `process.start`, `process.list`, `process.logs`, `process.stop`, and `http.fetch`.
|
|
92
94
|
Kimbho now also has browser-session tools for headless Chrome verification: `browser.open`, `browser.inspect`, `browser.click`, `browser.fill`, `browser.list`, and `browser.close`.
|
|
93
95
|
Shell runs now surface model-usage telemetry when the provider returns token counts.
|