agentlas-ai/Agentlas-OS

Agent Team Design defines agent teams, role boundaries, handoffs, memory owners, policy owners, and evaluation roles for multi-agent systems. Use it when creating a new team, a meta-agent, or an agent operating system repository.

Agentlas provides a single entry point for all Agentlas commands, including staffing federated workforces, building agent teams, running DAG graphs, browser automation, and searching agent catalogues. Use it when orchestrating multi-agent systems.

Agentlas Auto-Activation turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files. Use it when adding or auditing local runtime behavior that activates project continuity.

Agentlas Browser runs headless browser interactions via CDP for Agentlas tasks, such as rendering pages, completing form flows, and capturing visual evidence when a URL or query requires a real browser.

Agentlas Build designs, assembles, and packages installable single agents or multi-agent teams. Use it after /agentlas-build, /agentlas build, or /hep-build to classify mode, interview requirements, author routing card and soul, generate runtime adapters, and verify the package.

Agentlas Call invokes named Agentlas Hub or Cloud agents attached to the current project. Use it when you type /agentlas-call <agents> <context>, /agentlas call, or /hep-call to borrow and execute those agents.

Agentlas Cloud Workforce staffs specialist roles from the owner's private Agentlas Cloud packages. It is triggered by the /agentlas-cloud, /agentlas cloud, or /hep-cloud commands.

Agentlas Connect connects Agentlas channels such as Slack, Discord, and Telegram. Use it when the user types /agentlas-connect <channel>, /agentlas connect, or /hep-connect to manage channel integrations.

Agentlas Graph creates, inspects, schedules, and executes Agentlas DAG automation graphs. Use it when you need to define or run agent workflow automations with /agentlas-graph or /hep-graph.

Agentlas Hub staffs specialist roles from the public Agentlas Hub marketplace when a user invokes /agentlas-hub, /agentlas hub, or /hep-hub. Use it to assemble teams from the public workforce instead of local or private agents.

Agentlas Local Workforce staffs specialist roles from locally registered packages in ~/.agentlas/workforce/local. Use it when the user types /agentlas-local, /agentlas local, or /hep-local to restrict staffing to Local packages.

Agentlas Network staffs durable goals from registered Local, Cloud, and public Hub agents or teams via federated workforce orchestration. Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network.

Agentlas One toggles Hope, a persistent personal agent, on or off using slash commands like /agentlas-one on or /agentlas-one off. Use it when you need to enable or disable continuous mode for the Hope personal agent.

Agentlas Operations defines procedures for operating the Agentlas system: hep-network workforce formation with roster reuse, hep-graph automation, asset handling via cargo and marketplace, and memory contracts.

Agentlas Packaging converts, repairs, or packages an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release. Use it when bringing an existing agent into the Agentlas ecosystem.

Agentlas Search searches across Local, Cloud, and Hub agent repositories when the user types /agentlas-search, /agentlas search, or /hep-search. Use it to find agents available in the Agentlas ecosystem.

Agentlas Security Scan runs a two-stage security check on agent folders before private sync or public publish: a static rule scan and a BYOK LLM judgment for prompt injection, tool poisoning, secret exfiltration, destructive commands, and excessive permissions.

Agentlas Storm drives a goal through Hephaestus' force-robust, verifier-first Stormbreaker loop with real Agentlas specialists. Use when the user types /agentlas-storm, /hep-storm, or asks @Hephaestus storm <goal>.

Agentlas Upload scans, gates, and publishes agent and team packages to Agentlas Cloud (private) or Agentlas Hub (public) when triggered by slash commands such as /agentlas-upload or /hep-upload.

Clarify Question Loop asks one to five targeted questions when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt. It classifies mode, respects budgets, and translates technical choices into plain-language questions.

Hephaestus Cloud routes staffing requests through the signed-in user's own Agentlas cloud packages only, not the public marketplace or local cards. Use /hep-cloud when you need to staff agents from your own cloud scope or validate ownership-gated packages.

Hephaestus Graph creates, lists, inspects, and requests runs of Agentlas automation graphs saved in the local Agentlas database. Use it when the user types /hep-graph or asks to manage an Agentlas graph.

Hephaestus Network staffs a durable goal by searching registered Local, owner Cloud, and public Hub agents or teams. Use it when the user invokes $hephaestus-network, /hep-network, /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a goal.

Hephaestus Storm drives a goal to verified completion through a force-robust Stormbreaker loop. It routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop.

Hephaestus Upload publishes finished Agentlas agent or team packages to a private Cloud or public Agentlas Hub, asking the destination first, collecting Hub pricing, and running a validation gate that repairs and pins the exact artifact before submission.