Agent capabilities & guardrails — found from sitemap — Claude for Work

Cited by

Facts read from this source

• Dynamic workflows Report an error

  “Dynamic workflows is the feature that lets an agent write workflows and start runs. You turn it on or off with the workflows setting in the agent's multiagent block.”

• Background execution Report an error

  “The server runs a workflow in the background. Its agents work in session threads that the server creates as the workflow needs them. You follow runs on the session's event stream.”

• Concurrent agents Report an error

  “Run agents at the same time: The program can run many agents at the same time, which is called fanning out.”

• Failure retry Report an error

  “Handle a failed agent: When one of its agents fails, the server usually runs that agent once more, on a new thread, while the run's other agents keep working.”

• No approval step Report an error

  “There's no approval step before a run starts: the agent starts a run in the same turn that it writes the workflow.”

• Shared sandbox Report an error

  “A run's threads work in the session's sandbox, so every thread works with the same files.”

• Inline vs predefined Report an error

  “An agent in a run can be an inline agent, which the program defines itself, or a predefined agent, which you list in the predefined_agents list of workflows.”

• Run states Report an error

  “A run starts as running or as idle. Reaching the budget, for example, pauses a running run, which makes it idle; raising or removing the budget then makes it run again”

• Run events webhooks Report an error

  “Run events arrive on the session's event stream, which is the primary thread's stream, and listing the session's events returns them too. Run events don't trigger webhooks.”

• Phase behavior Report an error

  “Phases run one at a time, in the order of phases, each at most once, but the API doesn't guarantee it.”

• Budget no own price Report an error

  “A run's model requests count toward the session's budget. A run has no price of its own. The tokens its agents use are billed like the session's other tokens, at each model's rates.”

• Limit concurrent threads Report an error

  “Threads working at once in one run 64”

• Limit agents lifetime Report an error

  “Agents a workflow starts over the run's whole life 1,000”

• Limit run lifetime Report an error

  “Run lifetime 24 hours by default, or the lifetime the agent sets”

• Limit open runs Report an error

  “Runs open at once in a session 10 by default”

• No nested runs Report an error

  “Only the agent on the session's primary thread starts runs. An agent working in a run's thread can't start a run of its own, so runs don't nest.”

• Runs not counted child thread limit Report an error

  “Thread limit: A run's threads are exempt from the session's child-thread limit.”

• Rate limits shared Report an error

  “A run's work counts toward rate limits that your organization already has.”

Scores citing this record

• The Automation Lead Integrations, connectors & knowledge
• The Automation Lead Agent capabilities & guardrails
• The Automation Lead Agent capabilities & guardrails
• The Automation Lead Pricing transparency
• The Customer-Service Director Agent capabilities & guardrails
• The Customer-Service Director Agent capabilities & guardrails
• The Data Protection Officer Agent capabilities & guardrails
• The Data Protection Officer Agent capabilities & guardrails
• The Head of IT Agent capabilities & guardrails
• The Head of IT Agent capabilities & guardrails
• The Skeptic Agent capabilities & guardrails
• The Skeptic Agent capabilities & guardrails
• The Works Council Member Agent capabilities & guardrails
• The Works Council Member Agent capabilities & guardrails
• The Works Council Member Pricing transparency