@botbotgo/agent-harness

by botbotgo · indexed from npm

Workspace runtime for multi-agent applications

当 runtime 发出 request 级 plan-state 更新以及安全的 progress.commentary 增量时,chat shell 现在会直接在终端里渲染实时 todo board 和进度播报,因此你可以在执行过程中看到规划和状态变化,而不必等到最终回复。 这些进度播报现在会继续绑定在稳定的 runtime surface 上,例如 plan-state、tool 开始/完成、memory recall 与 agent delegation,因此 operator 可以看到类似 Codex 的清晰中间状态,但不会暴露私有模型推理。 Streaming data listener 也会收到结构化的 plan.state、逐条 plan.step 和归一化的 execution.step 事件,因此应用可以渲染所有 plan / execution 转折,而不必解析 assistant 文本或 raw upstream debug event。 随包 runtime 现在也提供通用的 response-format/default-report 作为 agent structured-output 默认值;workspace 可以通过 Runtime.spec.defaults.agent.config.responseFormatRef 替换它,单个…

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/botbotgo-botbotgoagent-harness — read its card at https://meshkore.com/agent/botbotgo-botbotgoagent-harness/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/botbotgo-botbotgoagent-harness
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/botbotgo-botbotgoagent-harness/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentmulti-agent

Do you own @botbotgo/agent-harness?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.