iosm-cli 0.2.11 → 0.2.12
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/CHANGELOG.md +17 -0
- package/README.md +2 -1
- package/dist/core/system-prompt.d.ts.map +1 -1
- package/dist/core/system-prompt.js +1 -0
- package/dist/core/system-prompt.js.map +1 -1
- package/dist/core/tools/task.js +1 -1
- package/dist/core/tools/task.js.map +1 -1
- package/docs/cli-reference.md +1 -0
- package/docs/interactive-mode.md +1 -0
- package/package.json +1 -1
package/docs/cli-reference.md
CHANGED
|
@@ -303,6 +303,7 @@ Best-practice patterns:
|
|
|
303
303
|
- File mutation: prefer `edit` for surgical changes and `write` for full rewrites; use `fs_ops` for `mkdir/move/copy/delete`, with `force=true` only when replacement/no-op behavior is intentional.
|
|
304
304
|
- Verification: prefer `test_run` / `lint_run` / `typecheck_run` over ad-hoc bash commands for deterministic runner resolution and normalized status reporting.
|
|
305
305
|
- Long-running shell jobs: prefer detached `bash` (`run_in_background=true`) or interactive `! <command> &`, then monitor with `/bg` instead of blocking the foreground turn.
|
|
306
|
+
- Project/server startup requests (for example "run project", "start dev server", watcher modes): default to detached background execution and return/process `backgroundTaskId` for status/log/stop follow-up.
|
|
306
307
|
- DB operations: prefer `db_run` with named profiles; keep read flows in `query/schema/explain` and use `allow_write=true` only for `exec/migrate`.
|
|
307
308
|
- Structured data transforms: use `jq`/`yq` to compute/preview transforms, then persist the final state through `edit`/`write`.
|
|
308
309
|
- Semantic retrieval: use `semantic_search status` first when relevance looks stale, then run `query`; run `index`/`rebuild` when config or index freshness requires it.
|
package/docs/interactive-mode.md
CHANGED
|
@@ -115,6 +115,7 @@ In `/semantic setup`, the headers step is optional: press `Enter` on empty input
|
|
|
115
115
|
`/ultrathink` without query reuses the latest meaningful user request from session context.
|
|
116
116
|
If early passes produce no tool evidence, ultrathink injects an internal grounding retry so the agent probes the workspace with read-only tools before continuing.
|
|
117
117
|
Run detached shell jobs with `! <command> &` (example: `! npm run dev &`) and manage them using `/bg`, `/bg status <id>`, `/bg logs <id> [lines]`, `/bg stop <id>`.
|
|
118
|
+
For agent-driven execution, prompts like "start/run project", "start dev server", or watcher startup are treated as detached background jobs by default unless foreground output is explicitly requested.
|
|
118
119
|
`/swarm` enforces `Scopes -> Touches -> Locks -> Gates -> Done`. If effective contract is missing, it blocks execution and opens a bootstrap menu (auto-draft, guided Q&A, or manual `/contract` editor).
|
|
119
120
|
`/orchestrate --parallel` defaults `--max-parallel` to `--agents` when omitted and auto-selects `meta` workers when profiles are not explicitly set (outside read-only host contexts).
|
|
120
121
|
For orchestrate assignments, `delegate_parallel_hint` is carried into child task calls; high hints should trigger nested delegate fan-out or explicit `DELEGATION_IMPOSSIBLE`.
|