The hive reads the agent-archetype key when it provisions and rebuilds an agent and keeps it in swarm-agent-archetypes.json. For an archetype agent the meta flake has no agent-<name> input and mkAgent imports hyperhive.hyperhiveArchetypes.<name>.module; provisioning, rebuilds, the meta-input cascade, a deploy's rev and the startup migration skip the config repos. The harness gets HIVE_ARCHETYPE and the system prompt says the agent has no config repo. The create form sends the picked archetype. Adds the android-dev built-in. Refs #5386
34 lines
1.1 KiB
Nix
34 lines
1.1 KiB
Nix
# The archetypes this flake ships, exposed as `hyperhiveArchetypes`. Each is
|
|
# `{ module; meta; }`: `module` is a NixOS module for the agent's container,
|
|
# `meta` is plain data (no derivations, no `pkgs`), because the swarm
|
|
# builder evaluates `meta` alone and swarm-controller stores it as JSON.
|
|
# `meta` fields: `description` (required), `permissions`, `limits`,
|
|
# `inference`, in the shapes `POST /api/agents` takes them; see
|
|
# docs/swarm/archetypes.md.
|
|
{
|
|
reviewer = {
|
|
module = { };
|
|
meta = {
|
|
description = "Reviews pull requests and replies. It can run hive-forge and git (execution), and holds messaging and inbox; it has no get_agent_meta (meta).";
|
|
permissions = [
|
|
"messaging"
|
|
"inbox"
|
|
"execution"
|
|
];
|
|
};
|
|
};
|
|
android-dev = {
|
|
module =
|
|
{ pkgs, ... }:
|
|
{
|
|
environment.systemPackages = [
|
|
pkgs.android-tools
|
|
pkgs.gradle
|
|
pkgs.jdk
|
|
];
|
|
};
|
|
meta = {
|
|
description = "Builds Android apps: adb and fastboot (android-tools), Gradle and a JDK are installed. It holds the default permissions.";
|
|
};
|
|
};
|
|
}
|