Interface: CrewAgentConfig
Defined in: packages/orchestration/src/crew/types.ts:8
Properties
budgetPerTicket?
optionalbudgetPerTicket?:number
Defined in: packages/orchestration/src/crew/types.ts:37
Maximum spend in USD per ticket (optional)
budgetTotal?
optionalbudgetTotal?:number
Defined in: packages/orchestration/src/crew/types.ts:39
Maximum total spend (optional)
capabilities
capabilities:
string[]
Defined in: packages/orchestration/src/crew/types.ts:14
Capabilities this agent has (used for auto-assignment)
maxConcurrent?
optionalmaxConcurrent?:number
Defined in: packages/orchestration/src/crew/types.ts:41
Maximum concurrent runs
name
name:
string
Defined in: packages/orchestration/src/crew/types.ts:10
Unique name for this agent
owned?
optionalowned?:boolean
Defined in: packages/orchestration/src/crew/types.ts:35
Whether the crew owns this agent's lifetime, and so releases its host
resources (sandbox container, tool-bridge port) in Crew.dispose().
Default false — an agent you constructed and handed in is yours, and a
crew closing it would tear down a bot you may still be running elsewhere.
Ownership is something the producer knows and no consumer can work out
from the agent itself, so it is stated here rather than sniffed. The
producers that set it are the ones that build a bot nobody else ever gets
a reference to: template.toCrew(), and the CLI and UI crew tools,
which construct their agents per tool call. For all of them dispose()
is the only place those bots can be released.
Set it yourself for a bot you build for one crew and want torn down with it. It is per-agent, so a roster can mix both.
Default
false
processable
processable:
Processable
Defined in: packages/orchestration/src/crew/types.ts:16
The actual Baleybot or Processable instance
role
role:
string
Defined in: packages/orchestration/src/crew/types.ts:12
Human-readable role description