hire

To onboard an agent from the library, you configure its identity, role, budget, and scope, then use /budget for budget management and /spawn for provisioning. This pipeline ensures the agent is correctly set up in the workspace before executing initial tasks.

The agent hiring process enforces an approval gate using the /approve command to prevent uncontrolled agent sprawl and budget creep. This board approval step must be completed before the onboarding pipeline can provision the new agent.

Yes, you can override default configurations when selecting an agent from the library. The skill allows you to customize the agent's name, role, budget, adapter, and scope during the workspace assembly process to fit your specific requirements.

The onboarding pipeline includes creating the agent's identity, setting up an inbox, granting scope, and spawning the agent with initial tasks. It coordinates these steps automatically after board approval is obtained via the /approve gate.

Board approval is required before spawning an agent to prevent uncontrolled agent sprawl and budget creep. This guardrail ensures that all new agents added to the workspace are validated and their budgets are properly managed.

Yes, the onboarding process supports custom adapter and scope setup. When assembling teams in the workspace, you can configure these specific agent settings along with identity and budget before provisioning the agent through the approval pipeline.