agentus 0.4.0 → 0.4.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/README.md +4 -3
- package/README.zh-CN.md +3 -2
- package/docs/installation.md +6 -3
- package/docs/installation.zh-CN.md +5 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -49,10 +49,11 @@ first, else `newSession` fails with `-32000`). Without one the cockpit still run
|
|
|
49
49
|
logs in — you just have no backend to start a session on.
|
|
50
50
|
|
|
51
51
|
A plain Hermes install drives sessions; the cockpit's own extras — per-session **thinking
|
|
52
|
-
depth**, a permission mode that survives a restart, the **context-budget** field
|
|
53
|
-
|
|
52
|
+
depth**, a permission mode that survives a restart, the **context-budget** field, the **status
|
|
53
|
+
channel** (memory recall/save hints in the message stream) — come from the fork's integration
|
|
54
|
+
build instead. That is a five-line install:
|
|
54
55
|
[§ Which Hermes to run](docs/installation.md#which-hermes-to-run) — currently the tag
|
|
55
|
-
`agentus/v0.22.0/merge-
|
|
56
|
+
`agentus/v0.22.0/merge-20261017-2152`, on Hermes `v0.22.0`.
|
|
56
57
|
|
|
57
58
|
The first slot you start will use the Hermes home **your own agent already uses**
|
|
58
59
|
(`~/.hermes`) unless the backend row names another one — see "HERMES_HOME" below.
|
package/README.zh-CN.md
CHANGED
|
@@ -44,9 +44,10 @@ web bundle、配套 APK —— 然后直接退出,不启动任何东西)。
|
|
|
44
44
|
照样能跑、照样能登录 —— 只是没有后端可以开会话。
|
|
45
45
|
|
|
46
46
|
裸装的 Hermes 就能跑会话;驾驶舱自己的那几项能力 —— 按会话切换的**思考深度**、跨重启存活的**权限模式**、
|
|
47
|
-
|
|
47
|
+
**上下文预算**输入框、把记忆召回 / 存记忆提示送进消息流的 **status 通道** —— 来自 fork 的集成构建(tag)。
|
|
48
|
+
装法就五行:
|
|
48
49
|
[§ 该跑哪份 Hermes](docs/installation.zh-CN.md#该跑哪份-hermes) —— 当前是 tag
|
|
49
|
-
`agentus/v0.22.0/merge-
|
|
50
|
+
`agentus/v0.22.0/merge-20261017-2152`,基座 Hermes `v0.22.0`。
|
|
50
51
|
|
|
51
52
|
你启动的第一个 slot 会使用**你自己的 agent 已经在用的**那个 Hermes home(`~/.hermes`),除非后端那一行
|
|
52
53
|
指定了另一个 —— 见下面的「HERMES_HOME」。
|
package/docs/installation.md
CHANGED
|
@@ -34,8 +34,11 @@ brew install node # or https://nodejs.org/en/download
|
|
|
34
34
|
|
|
35
35
|
Plain Hermes is enough to drive sessions. The capabilities this cockpit itself leans on are **not**
|
|
36
36
|
in the released build — a per-session **thinking depth** (ACP `reasoning_effort`), a **permission
|
|
37
|
-
mode that survives a restart** and `session/load`,
|
|
38
|
-
256K/512K/768K/1M presets)
|
|
37
|
+
mode that survives a restart** and `session/load`, a free-form **context budget** (with
|
|
38
|
+
256K/512K/768K/1M presets), the **status channel** that carries memory-recall / save hints into the
|
|
39
|
+
cockpit's message stream, and **per-process skill roots** (`HERMES_EXTERNAL_SKILLS_DIRS`, which is
|
|
40
|
+
how a slot sees the cockpit's own skill without anything being written into your `~/.hermes`).
|
|
41
|
+
They live on the ACP branches of the fork
|
|
39
42
|
[`LiangYang666/hermes-agent`](https://github.com/LiangYang666/hermes-agent), and reach the cockpit
|
|
40
43
|
through one **tag per integration build**, in a namespace of its own:
|
|
41
44
|
|
|
@@ -48,7 +51,7 @@ ref and gets rebuilt, while a tag never moves — so pin the tag. The `agentus/`
|
|
|
48
51
|
ours apart from upstream's own tags (`v0.22.0`, `v0.22.0+canary.*`), and the timestamp in the
|
|
49
52
|
last segment sorts, so "newest" is a `sort -V`.
|
|
50
53
|
|
|
51
|
-
**Current integration build: `agentus/v0.22.0/merge-
|
|
54
|
+
**Current integration build: `agentus/v0.22.0/merge-20261017-2152`** — the newest tag on the fork,
|
|
52
55
|
built on Hermes `v0.22.0`. This line is for orientation only, not the source of truth: the
|
|
53
56
|
`TAG=$(…)` step below resolves the newest one on every run, so read it there if this sentence
|
|
54
57
|
ever looks stale.
|
|
@@ -31,8 +31,10 @@ brew install node # 或者 https://nodejs.org/en/download
|
|
|
31
31
|
### 该跑哪份 Hermes
|
|
32
32
|
|
|
33
33
|
裸装的 Hermes 足够跑会话。但驾驶舱自己依赖的那几项能力**不在发布版里** —— 按会话切换的**思考深度**
|
|
34
|
-
(ACP `reasoning_effort`)、**跨重启 / `session/load`
|
|
35
|
-
(带 256K/512K/768K/1M
|
|
34
|
+
(ACP `reasoning_effort`)、**跨重启 / `session/load` 存活的权限模式**、可自由填写的**上下文预算**
|
|
35
|
+
(带 256K/512K/768K/1M 预设)、把记忆召回 / 存记忆提示送进驾驶舱消息流的 **status 通道**,以及
|
|
36
|
+
**按进程指定的技能根**(`HERMES_EXTERNAL_SKILLS_DIRS` —— 驾驶舱靠它让槽位看见自己的 skill,
|
|
37
|
+
不往你的 `~/.hermes` 写任何东西)。它们在 fork
|
|
36
38
|
[`LiangYang666/hermes-agent`](https://github.com/LiangYang666/hermes-agent) 的 ACP 分支上,
|
|
37
39
|
按基座版本各有一个**集成构建的 tag**,自成命名空间:
|
|
38
40
|
|
|
@@ -44,7 +46,7 @@ agentus/<hermes 内部版本>/merge-<YYYYMMDD-HHMM>
|
|
|
44
46
|
tag。`agentus/` 这个前缀也把它和上游自己的 tag(`v0.22.0`、`v0.22.0+canary.*`)分开;最后一段是时间戳,
|
|
45
47
|
可排序,所以「最新」就是一次 `sort -V`。
|
|
46
48
|
|
|
47
|
-
**当前集成构建:`agentus/v0.22.0/merge-
|
|
49
|
+
**当前集成构建:`agentus/v0.22.0/merge-20261017-2152`** —— fork 上最新的那个 tag,基座 Hermes
|
|
48
50
|
`v0.22.0`。这行只为一眼看个大概,不是权威:下面的 `TAG=$(…)` 每次都会自己解析出最新,觉得这行过期就
|
|
49
51
|
以它为准。
|
|
50
52
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agentus",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.1",
|
|
4
4
|
"description": "Multi-session web cockpit for ACP-speaking coding agents (Qoder CLI / Hermes). UI has no intelligence — the agent lives in spawned CLI subprocesses.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|