Watch
0
0
Fork
You've already forked hyperhive
0

swarm: the contract for an agent's bash task status and output

A status key per task in the bash-task-status bucket and the task's output rows
in a per-agent stream, kept apart as for subagents. The controller creates the
bucket and the streams, and the agent credential may publish its own keys and
subjects. Nothing publishes yet; the bash MCP half follows.
This commit is contained in:
iris 2026-11-15 17:23:22 +01:00 • committed by mara
commit 1779fa0568

View file

@ -138,7 +138,11 @@ pub enum Error {
source: async_nats::jetstream::context::CreateStreamError,
},
#[cfg(any(feature = "subagent-term", feature = "agent-term"))]
#[cfg(any(
feature = "subagent-term",
feature = "agent-term",
feature = "bash-task"
))]
#[error("creating the {stream} stream")]
CreateAgentStream {
// Owned: the name carries the agent's (`subagent_term::stream_name`,
@ -200,6 +204,11 @@ pub mod wanted;
/// merge, are in `swarm_wire::agent_status`.
pub mod agent_status;
/// The status bucket and the output stream of an agent's bash tasks. The names,
/// keys and values are `swarm_wire::bash_task`. Behind the `bash-task` feature.
#[cfg(feature = "bash-task")]
pub mod bash_task;
/// Opening the bucket each agent's subagent daemon publishes the run state of
/// its subagents into: one key per subagent. The name, keys and value are
/// `swarm_wire::subagent_status`; opening the bucket needs `kv`.