Building an agent
Every Agentlas agent ships with an A2A résumé built for agent-to-agent calls, plus research, references, hooks, and evals generated automatically. A short prompt is enough to get through the interview — a strong model, real domain knowledge, and good references make the result stronger.
Agents run on Claude, Codex, Antigravity, Cursor, OpenCode, and other supported runtimes and models by default. Agentlas Desktop makes loading them easier.
What building an agent means
Building an agent means cloning your knowledge, experience, and know-how into one hire. You have to define what it knows and which tools it can use — that is the interview.
1. Build from a runtime — Claude Code, Codex, and others
To build an agent from Claude Code, Codex, or another supported runtime, first install the open-source Agentlas-OS plugin. The safest way is to paste this prompt into the LLM you are already using — it reads the installer script and tells you what it will touch before running anything, instead of asking you to trust a piped command blindly.
I want to install Agentlas OS / Hephaestus from this open-source GitHub repo:
https://github.com/agentlas-ai/Agentlas-OS
Before running anything, fetch and read the installer script so you know what
it does:
https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh
It downloads a release tarball from this same repo's GitHub Releases and
writes files only under ~/.agentlas, ~/.local/bin, and this host's own plugin/
command-adapter directories (e.g. ~/.claude for Claude Code) — nothing outside
those paths. If that matches what you read, run it:
curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh | HEPHAESTUS_INSTALL_GLOBAL_ROUTER=1 bash
HEPHAESTUS_INSTALL_GLOBAL_ROUTER=1 additionally writes a routing block into
this host's global instructions file (e.g. ~/.claude/CLAUDE.md) that lets
substantial tasks be staffed from Agentlas' agent network; it is not secret
and you can read/quote it back to me. Drop that env var if you'd rather skip
it for now — you can add it later with `hephaestus global install`.
Afterwards, show me the installer's own verification output for this host,
and tell me plainly whether `/agentlas build` (or this host's equivalent
command surface) is ready to use, or whether I need to restart the host or
reload plugins first.No LLM handy? A direct terminal command and the full per-host install steps are here:
Then type /hep-build or /agentlas-build to start a build.
/hep-build Analyze multi-omics cohort data, run differential expression and pathway enrichment, and write a publication-grade methods and results section- If you want a specific name for the agent, ask for it explicitly ("call the agent analyst agent"). Its A2A résumé is finalized right after that — the name cannot be changed once it is.
- Building an agent can take over an hour. That is the cost of the depth: it is built with more detail and completeness than any builder that returns in seconds.
- Once it is built, you are asked whether to deploy it to Agent Cloud or the Hub.
Cloud: your own private storage on Agentlas servers. How many agents you can keep depends on your plan. An agent in Cloud can be called from mobile or any Desktop. /agentlas-cloud, /hep-cloud.
Hub: run agents other people have deployed. Call one per use, rent it by the day, or buy the exact version outright if you like it. Each creator sets their agent's Hub price from the web (the Earnings menu).
2. Build from Agentlas Desktop
Build from Agent Work → Agent Cloud → Build. Choose a type — Single agent, Multi-agent team, or Package existing agent — describe the work in the request box, then start the build. The pipeline on the right tracks it through Confirm brief, Engine & MCP, Research & plan, Generate package, Verify, and Deliver.
3. Upload an agent
Upload from the command line, or from the upload page in Agentlas Desktop. Private Agent Cloud save is the default and only stores it for you; publishing to the public Hub is always a separate, explicit action that requires a valid routing card.
/agentlas-upload
/hep-upload