Watch
0
0
Fork
You've already forked hyperhive
0

swarm: the commands and skills an agent's message box offers

GET /api/agents/{name}/commands answers with the swarm's own commands, a table
in the controller, then the skills the agent's harness published to its key of
the agent-commands bucket. The published part is untrusted and cut down: plain
names only, no repeats, never a command's name, a capped list and one short line
per description. The agent credential may publish its own key. Nothing publishes
yet; the harness half and the swarm UI menu follow.
This commit is contained in:
iris 2026-11-15 19:42:17 +01:00
commit 8f11a38d17
2 changed files with 389 additions and 7 deletions

View file

@ -0,0 +1,18 @@
//! The connection side of the agent skill list KV bucket: opening it. The
//! bucket's name, key and value are `swarm_wire::agent_commands`.
/// Open the bucket, creating it if nothing has yet. `history: 1`: the swarm
/// wants each agent's current skills, not the ones it had before.
#[cfg(feature = "kv")]
pub async fn open_or_create(
client: &async_nats::Client,
) -> Result<async_nats::jetstream::kv::Store, crate::Error> {
let js = async_nats::jetstream::new(client.clone());
crate::kv::open_or_create(
&js,
swarm_wire::agent_commands::BUCKET,
"agent-commands",
"The skills each agent has, as its harness last published them".to_owned(),
)
.await
}

View file

@ -214,6 +214,10 @@ pub mod bash_task;
/// `swarm_wire::subagent_status`; opening the bucket needs `kv`.
pub mod subagent_status;
/// Opening the bucket each agent's harness publishes its skills into. The name,
/// key and value are `swarm_wire::agent_commands`; opening the bucket needs `kv`.
pub mod agent_commands;
/// Opening the bucket agent icons are published into: one key per agent, with
/// no hive in it, unlike [`agent_status`]. The name, media type and subject,
/// and why the placement stays out of the key, are in `swarm_wire::agent_icon`.