omnirush 0.9.0 → 0.9.1
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/assets/CHANGELOG.md +35 -0
- package/assets/extensions/omnirush/agents-lib.ts +370 -53
- package/assets/extensions/omnirush/agents.ts +92 -11
- package/assets/extensions/omnirush/bgshell-lib.ts +32 -0
- package/assets/extensions/omnirush/capture/workspace-collector.ts +86 -22
- package/assets/extensions/omnirush/collector.ts +203 -32
- package/assets/extensions/omnirush/index.ts +22 -8
- package/assets/extensions/omnirush/mcp.ts +103 -8
- package/assets/extensions/omnirush/memory-lib.ts +516 -0
- package/assets/extensions/omnirush/pi-engine.ts +50 -2
- package/assets/extensions/omnirush/plan-lib.ts +38 -9
- package/assets/extensions/omnirush/plan.ts +85 -30
- package/assets/extensions/omnirush/subagent-marker.ts +21 -0
- package/package.json +1 -1
- package/scripts/smoke-packages.py +1 -0
- package/src/bin.js +28 -1
- package/src/sessions.js +222 -0
package/assets/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,41 @@
|
|
|
3
3
|
Shown by `/changelog` inside the agent and after an update. Newest first;
|
|
4
4
|
keep entries free of links (the agent core rewrites relative links).
|
|
5
5
|
|
|
6
|
+
## [0.9.1]
|
|
7
|
+
|
|
8
|
+
### Added
|
|
9
|
+
- Sub-agents can hand parts of their task to sub-agents of their own, up
|
|
10
|
+
to three layers below your session, as in the desktop app. The third
|
|
11
|
+
layer does its work itself, and every layer is recorded in the session
|
|
12
|
+
with who started whom.
|
|
13
|
+
- Sub-agents start as memory allows. There is still no limit on how many
|
|
14
|
+
run at once, but a sub-agent only starts while your machine keeps enough
|
|
15
|
+
memory free (a fifth of its RAM) and all of omnirush's agents together
|
|
16
|
+
stay under half of it; the others wait, shown as "queued: waiting for
|
|
17
|
+
memory", and start as memory frees up. When memory gets critically low
|
|
18
|
+
(under a tenth of RAM) no new sub-agent starts and omnirush tells you;
|
|
19
|
+
the running ones carry on. `/agents memory` shows the numbers.
|
|
20
|
+
`OMNIRUSH_AGENT_MIN_FREE`, `OMNIRUSH_AGENT_MEMORY_BUDGET` and
|
|
21
|
+
`OMNIRUSH_AGENT_CRITICAL_FREE` (for example `25%` or `6G`), or
|
|
22
|
+
`"subagentMemory"` in `~/.omnirush/settings.json`, change the limits;
|
|
23
|
+
`OMNIRUSH_AGENT_MEMORY=off` turns this off.
|
|
24
|
+
|
|
25
|
+
### Changed
|
|
26
|
+
- Far less memory with many sub-agents and in long sessions: sub-agent
|
|
27
|
+
output is read as it streams, sub-agents leave out what only your session
|
|
28
|
+
uses and start an MCP server only when they call one of its tools, and
|
|
29
|
+
finished shell commands no longer hold their output.
|
|
30
|
+
- `/resume` and `--continue` show only your own sessions. Sub-agents keep
|
|
31
|
+
their sessions in a `subagents` folder next to yours, and the ones older
|
|
32
|
+
versions left among your sessions are moved there on the next start.
|
|
33
|
+
- Every turn's prompt in your session trace is exactly what you typed. A
|
|
34
|
+
sub-agent's task, or a message an extension sends, is no longer shown as
|
|
35
|
+
your prompt.
|
|
36
|
+
- The task list in the footer reads `tasks 2/4 · ▸ <current task>` and no
|
|
37
|
+
longer looks like a mode. It says when the agent has not updated it for a
|
|
38
|
+
while, shows `idle` when a reply leaves it unfinished, clears when every
|
|
39
|
+
task is done, and only shows the current session's list.
|
|
40
|
+
|
|
6
41
|
## [0.9.0]
|
|
7
42
|
|
|
8
43
|
### Added
|