agentus 0.3.6 → 0.3.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 -1
- package/README.zh-CN.md +2 -1
- package/docs/installation.md +6 -1
- package/docs/installation.zh-CN.md +5 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -51,7 +51,8 @@ logs in — you just have no backend to start a session on.
|
|
|
51
51
|
A plain Hermes install drives sessions; the cockpit's own extras — per-session **thinking
|
|
52
52
|
depth**, a permission mode that survives a restart, the **context-budget** field — come from the
|
|
53
53
|
fork's integration build instead. That is a five-line install:
|
|
54
|
-
[§ Which Hermes to run](docs/installation.md#which-hermes-to-run)
|
|
54
|
+
[§ Which Hermes to run](docs/installation.md#which-hermes-to-run) — currently the tag
|
|
55
|
+
`agentus/v0.22.0/merge-20261015-0014`, on Hermes `v0.22.0`.
|
|
55
56
|
|
|
56
57
|
The first slot you start will use the Hermes home **your own agent already uses**
|
|
57
58
|
(`~/.hermes`) unless the backend row names another one — see "HERMES_HOME" below.
|
package/README.zh-CN.md
CHANGED
|
@@ -45,7 +45,8 @@ web bundle、配套 APK —— 然后直接退出，不启动任何东西）。
|
|
|
45
45
|
|
|
46
46
|
裸装的 Hermes 就能跑会话；驾驶舱自己的那几项能力 —— 按会话切换的**思考深度**、跨重启存活的**权限模式**、
|
|
47
47
|
**上下文预算**输入框 —— 来自 fork 的集成构建（tag）。装法就五行：
|
|
48
|
-
[§ 该跑哪份 Hermes](docs/installation.zh-CN.md#该跑哪份-hermes)
|
|
48
|
+
[§ 该跑哪份 Hermes](docs/installation.zh-CN.md#该跑哪份-hermes) —— 当前是 tag
|
|
49
|
+
`agentus/v0.22.0/merge-20261015-0014`，基座 Hermes `v0.22.0`。
|
|
49
50
|
|
|
50
51
|
你启动的第一个 slot 会使用**你自己的 agent 已经在用的**那个 Hermes home（`~/.hermes`），除非后端那一行
|
|
51
52
|
指定了另一个 —— 见下面的「HERMES_HOME」。
|
package/docs/installation.md
CHANGED
|
@@ -45,9 +45,14 @@ agentus/<hermes version>/merge-<YYYYMMDD-HHMM>
|
|
|
45
45
|
|
|
46
46
|
A tag and not a branch, on purpose: the branch of the same name (under `yl-dev/`) is the working
|
|
47
47
|
ref and gets rebuilt, while a tag never moves — so pin the tag. The `agentus/` prefix also keeps
|
|
48
|
-
ours apart from upstream's own tags (`v0.
|
|
48
|
+
ours apart from upstream's own tags (`v0.22.0`, `v0.22.0+canary.*`), and the timestamp in the
|
|
49
49
|
last segment sorts, so "newest" is a `sort -V`.
|
|
50
50
|
|
|
51
|
+
**Current integration build: `agentus/v0.22.0/merge-20261015-0014`** — the newest tag on the fork,
|
|
52
|
+
built on Hermes `v0.22.0`. This line is for orientation only, not the source of truth: the
|
|
53
|
+
`TAG=$(…)` step below resolves the newest one on every run, so read it there if this sentence
|
|
54
|
+
ever looks stale.
|
|
55
|
+
|
|
51
56
|
Install Hermes normally first — its installer brings the Python/Node runtime and puts `hermes` on
|
|
52
57
|
your PATH — then run that build on top of that runtime:
|
|
53
58
|
|
|
@@ -41,9 +41,13 @@ agentus/<hermes 内部版本>/merge-<YYYYMMDD-HHMM>
|
|
|
41
41
|
```
|
|
42
42
|
|
|
43
43
|
用 tag 而不是分支是刻意的：同名分支（在 `yl-dev/` 下）是工作面、会被重建，而 tag 永不移动 —— 所以钉
|
|
44
|
-
tag。`agentus/` 这个前缀也把它和上游自己的 tag（`v0.
|
|
44
|
+
tag。`agentus/` 这个前缀也把它和上游自己的 tag（`v0.22.0`、`v0.22.0+canary.*`）分开；最后一段是时间戳，
|
|
45
45
|
可排序，所以「最新」就是一次 `sort -V`。
|
|
46
46
|
|
|
47
|
+
**当前集成构建：`agentus/v0.22.0/merge-20261015-0014`** —— fork 上最新的那个 tag，基座 Hermes
|
|
48
|
+
`v0.22.0`。这行只为一眼看个大概，不是权威：下面的 `TAG=$(…)` 每次都会自己解析出最新，觉得这行过期就
|
|
49
|
+
以它为准。
|
|
50
|
+
|
|
47
51
|
先正常装好 Hermes（它的安装器会带上 Python/Node 运行时，并把 `hermes` 放进 PATH），再把那份构建
|
|
48
52
|
套在那个运行时上跑：
|
|
49
53
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agentus",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.7",
|
|
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": {
|