Hephaestus

Copy-Paste Quickstart

Paste this into Claude Code, Codex, Gemini CLI, Antigravity, or Cursor. Let the AI install Hephaestus and tell you which command surface is active in that tool.

Install Hephaestus Agentlas for this workspace from this GitHub repo:
https://github.com/agentlas-ai/Hephaestus

Use the latest release/instructions. If anything errors, diagnose and fix it, retry, and confirm which command surface is active in this tool.

After it finishes, tell me the three primary commands I should use:
1. create/build agents
2. borrow public Hub agents
3. use agents saved in my Agentlas Cloud

Then also tell me the two power-user commands:
4. search Cloud and Hub candidates without invoking
5. call exact agent slugs I name
6. upload agents only after asking whether I mean private Cloud or public Hub

If anything fails, read the error, fix it, retry, and confirm Claude Code,
Codex, Gemini CLI, Antigravity, and Cursor registration status.

Three Primary Commands

Utility Commands

Fresh installs and updates prune the old visible /hephaestus chat command so new users see the clean command surface above: three primary commands, plus search, call, and upload utilities when they need explicit control.

New In v0.7.19

• Short command surface. The visible commands are now /hep-build, /hep-network, /hep-cloud, /hep-search, /hep-call, and /hep-upload across Claude Code, Codex, Gemini CLI, Antigravity, Cursor, OpenCode, and terminal installs.
• Explicit upload gate. /hep-upload always asks whether you mean private Agentlas Cloud or public Agentlas Hub before it packages, publishes, registers, or uploads anything.
• Cleaner installs. Fresh installs and updates prune stale /hephaestus-* chat command files while preserving compatibility for older terminal callers.

Hephaestus is the open core engine that makes Agentlas behave like an agent operating system instead of a one-off prompt generator. It gives developers five connected control planes:

• Meta-agent builder. Classify intent, ask the missing setup questions, and emit one agent, a multi-agent team, or a clean package with runtime adapters.
• A2A Hub router. Route requests through local routing cards first, then approved Agentlas Hub fallback, with receipts for every handoff.
• Hephaestus Stormbreaker. Keep long-running work inside a scope lock, failure-memory check, verifier-first plan, parallel session fabric, evidence loop, review gate, and final gate so agents cannot silently stop or claim completion before checks pass.
• Project ontology. Turn approved project sources into local graph, search, and source-lineage context agents can query without sweeping unrelated folders. This is not the Hub marketplace search. It is the project-local knowledge/memory map that routed agents may consult when a task needs grounding.
• Memory, self-evolution, and security gates. Admit durable memory, promote skills, verify installs, scan packages, and block unsafe publish paths before agents are allowed to keep or ship new behavior.

Hephaestus Network 2.0

One command, every runtime, all local:

/hep-build create a customer support agent
/hep-network borrow the right agents for this launch plan
/hep-cloud use the agent I shared to my Agentlas Cloud
/hep-search find agents for an ASO review workflow
/hep-call aso-researcher, reply-writer {draft replies for these reviews}

• Routing cards. Every agent, team, and plugin ships a standardized routing card (triggers, anti-triggers, capabilities, risk profile, memory behavior). Cards that fail the quality gates are never auto-routed.
• Local first. Explicit commands → project overrides → your local cards. The Agentlas Hub is a fallback that only ever receives redacted keywords — never your raw prompt.
• Memory stays local. Agent capability can come from the Hub; your user/project memory lives in ~/.agentlas/networking/ and never leaves the machine without an explicit export approval.
• Receipts, not execution. Every routing decision writes a receipt. The router only selects agents or Hub bundles; the host runtime enforces permissions when tools actually execute.
• Three primary commands. Use /hep-build to create or repair agents, /hep-network to borrow public Hub agents into a temporary task force, and /hep-cloud to use agents you saved or shared through Agentlas Cloud. Heavy users can add /hep-search to compare Cloud and Hub candidates without invoking, and /hep-call to prepare exact named agents. The lower-level ao, network, cards, and mcp commands stay available for automation and debugging.
• Temporary task forces. Composite /hep-network requests are decomposed only when needed, then returned as a Hub/local TF plan with Stormbreaker packets, session hints, ontology graph paths, Local Operator policy labels, and Memory/Playbook candidates in the receipt.
• Measured, not claimed. A routing benchmark (Korean + English) gates auto-routing: top-3 recall ≥ 90%, zero unsafe routes in the privacy suite.
• Stormbreaker operational evals. A separate scorecard compares native Codex, Hephaestus Network routing, and Hephaestus Stormbreaker on the same task fixtures.

A2A Agent Card Boundary

The A2A upgrade is the external agent interoperability boundary. It does more than find a Hub result: it imports, exports, and gates agent-to-agent cards without leaking local project state.

agentlas-cloud ao a2a import ./agent-card.json .
agentlas-cloud ao a2a export . --agent local/10-builder
agentlas-cloud route "run the release check" --caller local/orchestrator .

• Import is a proposal. External A2A AgentCard files become ExternalAgent proposals plus capability alignment edges only. Import never grants can_invoke, rejects malformed JSON, and caps untrusted skill lists.
• Export is whitelist-only. Internal agents are projected to /.well-known/agent-card.json from public fields. Private paths, local memory behavior, raw routing-card text, and policy rationale are redacted.
• Invocation is caller-gated. The CLI route --caller flag and MCP hephaestus_route.caller_id input thread the caller into the route gate, so blocked agent-to-agent calls stay blocked before a route is selected.

Details: [docs/hephaestus-network-