Skip to content
Development
Command

/hep-network

Staff a task from registered Local, owner Cloud, and public Hub agents.

From plugin
agentlas-os
1.2k14 skills5 agents14 commands1 MCP
Install
> /plugin marketplace add agentlas-ai/Agentlas-OS
> /plugin install hephaestus@agentlas-core-engine

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/hep-network

Context preview

What this command does when you run it.

Staff a task from registered Local, owner Cloud, and public Hub agents.

Command definition

hep-network.md
description: Staff a task from registered Local, owner Cloud, and public Hub agents.
argument-hint: '<request>'
allowed-tools: Bash, Read, Glob, Grep

Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.

/hep-network

Raw request: `$ARGUMENTS`

You are the active top-level workforce orchestrator. Use the local Agentlas OS MCP server named `hephaestus-network`, the only host-visible Workforce MCP. Core reaches Cloud and Hub through its internal upstream client. Network means all registered Local agents, the signed-in owner's Cloud agents, and public Hub agents.

The user does not need to say `goal`. First call `workforce.goal_context` for the current project. If it returns an active binding for this ongoing work, reuse that exact roster and `goalId` before considering recruitment.

Before the first Cloud or Hub source call, reuse the installed Agentlas sign-in. Resolve the runner in this order and use it only for authentication; the host LLM still performs staffing through the Workforce MCP tools:

RUNNER=""
for candidate in \
  "$HOME/.agentlas/runtime/current/bin/hephaestus" \
  "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/bin/hephaestus}" \
  "${PLUGIN_ROOT:+$PLUGIN_ROOT/bin/hephaestus}" \
  "./bin/hephaestus"
do
  if [ -n "$candidate" ] && [ -x "$candidate" ]; then RUNNER="$candidate"; break; fi
done
[ -n "$RUNNER" ] && "$RUNNER" auth ensure --timeout 180 >/dev/null 2>&1 || true

1. Author a redacted `agentlas.workforce-work-order.v1` with distinct role slots: a specific `task`, `cardinality`, `criticality`, and — only when they genuinely constrain the hire — required communities/skills/knowledge, runtimes, and `languages`. Leave every other slot field out entirely: an absent list field IS the empty constraint (the wire normalizes absent to []). Do not fill requiredToolCapabilities, requiredAuthorities, forbiddenAuthorities, consumes, produces, requiredRoles, or modalities — tools, authorities, and modalities attach to the executing runtime, not the agent card, so those gates only exclude real candidates; describe ordinary inputs/outputs in the task text and inter-slot handoffs in `edges`. Keep private files, memory, secrets, direct identifiers, and raw local context on-host. Write every discovery-facing field (statement, role descriptions, required skills/knowledge, artifacts) in English, faithfully translating a non-English request rather than passing its original wording through: the candidate corpus is English and cross-lingual matching silently buries the correct agent (measured: an identical query ranked its target 1st in English and 144th in Korean). Keep an untranslatable proper term alongside a short English gloss, e.g. `종합소득세 (Korean comprehensive income tax)`. The `languages` slot is the delivery requirement, not the search language — set it to the language the work product must be produced in (e.g. `ko`) even though the order itself is written in English. 2. Call `workforce.search_candidates` on `hephaestus-network` with `{workOrder, sourceScope: "network"}` and keep the complete response as `federationResult`. Preserve every source receipt and provenance row. An unavailable source is explicit; it is not permission to pretend that source participated. 3. As the active host LLM, author `agentlas.workforce-selection.v1` from the returned content and qualification evidence. Call `workforce.validate_selection` with `{workOrder, selection}` and keep its accepted response as `federatedSelection`. Revise on rejection. Deterministic code may enforce governance but must not choose, rerank, or silently substitute the roster. 4. Call `workforce.prepare_execution` with `{workOrder, selection, federatedSelection, projectDir, goalId?}`. `projectDir` is mandatory. Pass the incumbent `goalId` when continuing; otherwise Core derives one from the WorkOrder id. Core must automatically bind a successful preparation before execution, so continuity cannot be skipped because no explicit goal mode was requested. Require each worker to retain its exact source plus release, package hash, content digest, runtime-bundle digest, permission policy, and execution context pins. Recompute digests and fail closed on drift. 5. On later turns call `workforce.goal_context` first: reuse the incumbent roster plus local skills when sufficient; recruit only a real gap and pass the same `goalId` to preparation so new releases append. Record `reuse|local-only|recruit|standby|blocked` with `workforce.record_goal_turn`. 6. Before every bound invocation, advertise the live host sessions and call `model.resolve_allocation` with that inventory plus the host-owned stage: `planner`/`manager-plan`, `worker`, `manager-synthesis`/`synthesis`, or `verifier`. Use the receipt's exact provider, model, and effort for that invocation. Model pins and ceilings come only from the MCP server's operator policy, never from the task or tool arguments. A missing worker policy inherits orchestrator; orchestrator never falls through to worker. 7. Run only the bound workers useful for this turn. For a selected team, preserve its authoritative manager/worker graph. Run planner/manager, workers, synthesis, and verifier as distinct invocations with explicit artifact handoffs. Allocation receipts have `usage: null` before execution, so record actual usage on the later invocation/run receipt instead of inventing zero. 8. Report `executed` only when the execution receipt proves every selected invocation, handoff, synthesis, and an independent passing verifier. Otherwise report the last truthful state: `selected`, `prepared`, `source_unavailable`, `blocked`, or `failed`.

The roster remains bound across turns, sessions, restarts, and context compaction until the whole goal is explicitly completed/cancelled through `workfor

Read more
Ships withagentlas-os

Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.

Get the whole plugin