@botbotgo/agent-harness 0.0.97 → 0.0.99
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 -0
- package/README.zh.md +4 -0
- package/dist/package-version.d.ts +1 -1
- package/dist/package-version.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -72,12 +72,15 @@ Boundary documents live in:
|
|
|
72
72
|
|
|
73
73
|
- `docs/upstream-feature-matrix.md`
|
|
74
74
|
- `docs/product-boundary.md`
|
|
75
|
+
- `docs/acp-support-plan.md`
|
|
75
76
|
- `docs/feature-checklist.md`
|
|
76
77
|
- `docs/long-term-memory.md`
|
|
77
78
|
- `docs/app-task-pattern.md`
|
|
78
79
|
- `docs/model-layering.md`
|
|
79
80
|
- `docs/coding-agent-guide.md`
|
|
80
81
|
|
|
82
|
+
ACP is the intended future client protocol direction when external tools need a standard runtime boundary. The harness should become ACP-capable while keeping runtime lifecycle, persistence, recovery, and governance harness-owned.
|
|
83
|
+
|
|
81
84
|
Recommended orchestration shape for long-running flows:
|
|
82
85
|
|
|
83
86
|
- let callers select the host agent explicitly whenever possible
|
|
@@ -636,6 +639,7 @@ For backend-specific options, prefer the upstream concept directly inside `spec.
|
|
|
636
639
|
- `agent-harness` is not a third agent framework
|
|
637
640
|
- public runtime contract stays generic and small
|
|
638
641
|
- application-level orchestration and lifecycle management stays in the harness
|
|
642
|
+
- ACP should be the preferred future external client protocol instead of a parallel harness-only protocol
|
|
639
643
|
- upstream LangChain v1 and DeepAgents concepts should be expressed as directly as possible in YAML
|
|
640
644
|
- when a feature can be expressed in YAML, prefer YAML over expanding the public API
|
|
641
645
|
- recovery, approvals, threads, runs, and events are runtime concepts, not backend escape hatches
|
package/README.zh.md
CHANGED
|
@@ -72,12 +72,15 @@
|
|
|
72
72
|
|
|
73
73
|
- `docs/upstream-feature-matrix.md`
|
|
74
74
|
- `docs/product-boundary.md`
|
|
75
|
+
- `docs/acp-support-plan.md`
|
|
75
76
|
- `docs/feature-checklist.md`
|
|
76
77
|
- `docs/long-term-memory.md`
|
|
77
78
|
- `docs/app-task-pattern.md`
|
|
78
79
|
- `docs/model-layering.md`
|
|
79
80
|
- `docs/coding-agent-guide.md`
|
|
80
81
|
|
|
82
|
+
当外部工具需要标准运行时边界时，ACP 是预期的未来客户端协议方向。`agent-harness` 应该具备 ACP 能力，同时继续把运行时生命周期、持久化、恢复与治理保留在 harness 内部。
|
|
83
|
+
|
|
81
84
|
长链路编排的推荐形态：
|
|
82
85
|
|
|
83
86
|
- 尽量由调用方显式指定要运行的 host agent
|
|
@@ -630,6 +633,7 @@ spec:
|
|
|
630
633
|
- `agent-harness` 不是第三个 agent 框架
|
|
631
634
|
- 公共运行时契约保持通用且精简
|
|
632
635
|
- 应用级编排与生命周期管理留在 harness 中
|
|
636
|
+
- ACP 应作为优先对齐的未来外部客户端协议，而不是再做一套并行的 harness 私有协议
|
|
633
637
|
- 应尽量在 YAML 中直接表达 LangChain v1 与 DeepAgents 的概念
|
|
634
638
|
- 能用 YAML 表达的能力，优先 YAML 而非扩张公共 API
|
|
635
639
|
- 恢复、审批、线程、运行与事件是运行时概念，不是后端逃生舱
|
|
@@ -1 +1 @@
|
|
|
1
|
-
export declare const AGENT_HARNESS_VERSION = "0.0.
|
|
1
|
+
export declare const AGENT_HARNESS_VERSION = "0.0.98";
|
package/dist/package-version.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export const AGENT_HARNESS_VERSION = "0.0.
|
|
1
|
+
export const AGENT_HARNESS_VERSION = "0.0.98";
|