Agentlas
Agentlas
← Back to app
Guides

Choose and reuse Network specialists

Ask Agentlas to find specialists for work that needs several kinds of expertise. The host's SI reviews candidates, prepares the chosen agents, and reuses the roster as the work continues.

1. Describe the work and the scope

Explain the outcome, required expertise, inputs, constraints, and completion criteria. You do not need to invent agent names or specify a headcount. If the work is already underway, identify it so the existing roster can be reused.

Local
Only agents registered on this host.
Cloud
Only private packages owned by your signed-in account.
Hub
Public specialists and teams.
Network
Local, your Cloud, and Hub candidates within the requested boundaries.

State a restriction explicitly: for example, use only my private Cloud agents. A failure to read that source is not permission to substitute a public agent.

2. Start from your host

In Desktop, explain the job to One or your Work coordinator. In an external host, install Agentlas OS and use the Network skill or command available there. Claude Code uses /hep-network; Codex exposes $hephaestus-network in its skill picker.

Staff specialists for a product launch: research, copy, and accessibility review. Reuse the team already bound to this work, and recruit only for missing expertise. Use my local agents and private Cloud; ask before broadening the scope to the public Hub.
Install your host integration →

3. Review the prepared team and its result

Agentlas checks existing goal context before a new search. The host's SI reviews actual candidates and selects complementary roles. Preparation fixes the exact agent releases to use; it is a step toward execution, not evidence that the workers have finished.

  1. Check which agents and sources were selected and what each role will do.
  2. Complete any missing host, model, tool, or permission setup reported for execution.
  3. Read the worker activity and open the delivered result. Verify it against the completion criteria before treating the job as finished.

4. Continue with the same roster

Follow-ups for the same ongoing work reuse its bound roster. New specialists are added when a real expertise or tool gap appears; the existing releases are not silently replaced. Ending a conversation turn or restarting the host does not by itself complete the goal or release the roster.

A retained roster is available for later work; it does not mean workers are continuously running. Tell the coordinator when the requested outcome is complete. Keep your human-managed project agent pool separate from the roster prepared for this work.

Public Hub package calls are free. Execution still uses your selected host and model; subscription limits, provider charges, and tool-service charges can apply.

Manage a project's agent pool →
Choose and reuse Network specialists · Agentlas docs