@kimbho/kimbho-cli 0.1.5 → 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 CHANGED
@@ -22,7 +22,7 @@ From a packed tarball:
22
22
 
23
23
  ```bash
24
24
  npm run pack:cli
25
- npm install -g ./kimbho-kimbho-cli-0.1.0.tgz
25
+ npm install -g ./kimbho-kimbho-cli-0.1.5.tgz
26
26
  ```
27
27
 
28
28
  ## Usage
@@ -36,13 +36,14 @@ kimbho plan "build a coding agent"
36
36
  kimbho /models openrouter --search claude --limit 10
37
37
  ```
38
38
 
39
- Bare `kimbho` opens the interactive shell. Within that shell, plain-English input is sent to the active model, and slash commands like `/plan`, `/run`, `/models`, and `/brains` are supported. Provider and model selections apply to all agent roles by default.
39
+ Bare `kimbho` opens the interactive shell. Within that shell, plain build/change prompts are routed into the agent runtime by default, while `/ask` keeps a plain chat path to the active model. Slash commands like `/plan`, `/run`, `/models`, and `/brains` are supported too. Provider and model selections apply to all agent roles by default.
40
40
 
41
41
  Useful shell commands:
42
42
 
43
43
  ```bash
44
44
  /status
45
45
  /ask say hello from lm studio
46
+ /ask explain this codebase
46
47
  /providers
47
48
  /providers add openrouter
48
49
  /providers use openrouter-main
@@ -53,9 +54,20 @@ Useful shell commands:
53
54
  /plan build a coding agent
54
55
  /run scaffold a SaaS starter
55
56
  /resume --execute --max-auto-tasks 2 --max-repair-attempts 2
57
+ /review
56
58
  /quit
57
59
  ```
58
60
 
61
+ Example direct execution prompt:
62
+
63
+ ```bash
64
+ build a landing page for a small storefront
65
+ ```
66
+
67
+ That prompt now runs through the agent execution path, streams live task and tool activity while it executes, and then prints the saved session summary instead of returning a plain chat answer.
68
+ During an active shell run, `Ctrl+C` now requests a pause instead of killing the shell; use `/resume` to continue the saved session.
69
+ Shell runs now also show a compact live run board with active tasks, budgets, token usage, and the latest runtime note while execution is in flight.
70
+
59
71
  LM Studio example:
60
72
 
61
73
  ```bash
@@ -65,9 +77,23 @@ LM Studio example:
65
77
  ```
66
78
 
67
79
  `run` now auto-executes the supported ready-task frontier and persists session events. Specialist tasks are executed through a bounded model-driven tool loop that can list files, search source contents, read files, write files, apply patches, inspect git diff, run verification commands, and emit resumable transcripts. `resume --execute` continues that frontier from the latest session snapshot.
80
+ Kimbho also has repo intelligence tools (`repo.index`, `repo.query`) so agents can reason over symbols, routes, schemas, packages, and import edges instead of relying only on raw file reads.
81
+ For empty workspaces, Kimbho now has deterministic scaffold presets for `static-landing`, `node-cli-typescript`, `next-prisma-postgres`, and `kimbho-cli-monorepo`, so the scaffold task can generate a real starter app without needing preexisting repo state or a prior `.kimbho/config.json`.
82
+ For existing repositories, specialists now preload deterministic repo context before the first model action: `repo.index`, `repo.query`, and a small set of repo-defining file reads are injected automatically into the transcript and prompt context.
83
+ When resuming the current saved session, that saved session context is also injected into the next specialist run so the model does not restart from zero.
68
84
  After the agent changes workspace state, it now has to pass a verification step before the task can finish.
69
85
  If verification fails, Kimbho forces a repair pass before the next rerun and blocks the task after the configured repair budget is exhausted.
70
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.
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.
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.
90
+ Those concurrent integrations are now serialized, so overlapping edits do not race generic patch application anymore.
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.
93
+ Kimbho also has managed background process tools and live HTTP verification: `process.start`, `process.list`, `process.logs`, `process.stop`, and `http.fetch`.
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`.
95
+ Shell runs now surface model-usage telemetry when the provider returns token counts.
96
+ If a specialist starts a managed process inside an isolated worktree, Kimbho now stops it automatically before cleaning that worktree up.
71
97
 
72
98
  Useful tuning flags:
73
99