Skip to content
Development
Command

/hep-cloud

Staff a task only from the signed-in owner's Agent Cloud 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-cloud

Context preview

What this command does when you run it.

Staff a task only from the signed-in owner's Agent Cloud agents.

Command definition

hep-cloud.md
description: Staff a task only from the signed-in owner's Agent Cloud agents.
argument-hint: '<request>'
allowed-tools: Bash, Read, Glob, Grep

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

/hep-cloud

Raw request: `$ARGUMENTS`

Act as the temporary top-level workforce orchestrator. Use the local Agentlas OS MCP server `hephaestus-network` and call the Workforce tools with exact `sourceScope: "cloud"`. This command may search only packages owned by the signed-in Agentlas account. It must not add Local or public Hub candidates.

Before the first Cloud 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`; private project grounding stays on-host. 2. Call `workforce.search_candidates` with `{workOrder, sourceScope: "cloud"}` and keep the complete response as `federationResult`. 3. Author the final `agentlas.workforce-selection.v1` as the active host LLM, then call `workforce.validate_selection` with `{workOrder, selection}` and keep the response as `federatedSelection`. Revise on rejection; do not accept a deterministic picker or unrelated fallback. 4. Call `workforce.prepare_execution` with `{workOrder, selection, federatedSelection, projectDir}`. Require every selected row to remain pinned to source `cloud`, exact release, package hash, content digest, runtime bundle, permission policy, and context digest. 5. Execute distinct planner/manager, worker, synthesis, and verifier calls with explicit artifact handoffs. Preserve packaged Team graphs.

If owner authentication or the Cloud source is unavailable, report `source_unavailable` and the Core receipt. Do not silently search Local or Hub, call a legacy route, or expose a direct remote `agentlas` MCP alongside Core. A prepared roster is not proof of execution.

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