agentlas-core-engine-m…
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into…
Staff a task only from Agentlas agents registered on this machine.
Claude Code
$ npx -y skills add agentlas-ai/Agentlas-OS --skill hep-local --agent claude-code
Codex
$ npx skills add agentlas-ai/Agentlas-OS --skill hep-local -a codex -y
Cursor
$ npx skills add agentlas-ai/Agentlas-OS --skill hep-local -a cursor -y
Gemini CLI
$ npx skills add agentlas-ai/Agentlas-OS --skill hep-local -a gemini-cli -y
GitHub Copilot
$ npx skills add agentlas-ai/Agentlas-OS --skill hep-local -a github-copilot -y
OpenCode
$ npx skills add agentlas-ai/Agentlas-OS --skill hep-local -a opencode -y
Windsurf
$ npx skills add agentlas-ai/Agentlas-OS --skill hep-local -a windsurf -y
name: hep-local description: Staff a task only from Agentlas agents registered on this machine.
Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.
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: "local"`. Before every unpinned discovery, Core refreshes the current safe snapshot for each active registered Local source, creating a new release when the source folder changed. This command searches only that registered Local inventory; it must not add owner Cloud or public Hub candidates. A prepared or goal-bound selection remains pinned to its exact release. `network reindex` rebuilds the card cache but is not the release refresh mechanism, and a new source still requires explicit registration.
1. Author a redacted `agentlas.workforce-work-order.v1`; private project grounding stays on-host. 2. Call `workforce.search_candidates` with `{workOrder, sourceScope: "local"}` and keep the complete response as `federationResult`, including its local registry receipt and the projected menu's `selectionSessionId`. Do not echo the projected menu back as `federationResult` — Core resolves the complete federation state locally from that session. 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 `local`, exact package/content identity, 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 the local Core MCP or registered inventory is unavailable, report `source_unavailable`; do not silently search Cloud or Hub. A prepared roster is not proof of execution.
If `workforce.prepare_execution` refuses with a `repair` object, the agent is broken, not absent. Say in plain words what `repair.meaning` says, offer the first `available` action in `repair.repair`, and run its `command` only after the user agrees. When a repair reports `reselectionRequired: true`, select again (`workforce.validate_selection`, then `workforce.prepare_execution`); never swap in a different agent without a new selection. A refusal that carries `alternates` lists other callable agents from the same search: present them as candidates and let the user or the selection step choose.
A package the builder wrote to the global agent folder is registered automatically at the next local search once it passes `contract verify`; one that does not pass is not registered and is named with its first blockers. `hephaestus workforce local-autoregister` does it now and prints `contractFailing` and `refused` rows, which is where to look when an agent you built is missing from the menu.
For a `partial` or `failed` result, report each source receipt's exact `failureCode`. Never collapse several receipts into one, substitute a different code, or relabel the outcome.
An open-source AI agent OS inspired by OpenAI Dots, Meta Muse, Claude Duet, Nous Hermes, and Mem0. Built to lead entire projects rather than isolated prompts. Model-agnostic (BYOM) and native to Claude Code, Codex, Cursor, Antigravity, and Agentlas Desktop.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into…
Use when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local…
Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or…
Turn the current interactive conversation into an owner-reviewed reusable Agentlas agent; accept JSON or JSONL only for explicit…
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers,…
Agentlas 시스템 운용 절차 — hep-network 편성, cargo/Agent Cloud·marketplace 활용, workforce 로스터 재사용, 메모리 계약. One(개인 에이전트)이 Agentlas를 조작할 때 이…
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
Create a new Architecture Decision Record with sequential numbering and AgentDB registration