# How to prevent automatic agent jobs in human-only LiveKit Cloud rooms?

**URL:** <https://community.livekit.io/t/how-to-prevent-automatic-agent-jobs-in-human-only-livekit-cloud-rooms/2457>\
**Category:** Agents\
**Tags:** agent-development, livekit-cloud\
**Created:** [November 6, 2026, 5:48am UTC](https://community.livekit.io/t/how-to-prevent-automatic-agent-jobs-in-human-only-livekit-cloud-rooms/2457 "2026-11-06T05:48:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [November 6, 2026, 9:26am UTC](https://community.livekit.io/t/how-to-prevent-automatic-agent-jobs-in-human-only-livekit-cloud-rooms/2457/2 "2026-11-06T09:26:38Z")

</div>

[Build-plan deployed agent stays Sleeping after CreateDispatch; never joins room (outbound SIP)](https://community.livekit.io/t/build-plan-deployed-agent-stays-sleeping-after-createdispatch-never-joins-room-outbound-sip/2269) is almost the opposite problem, isn’t it - in that case an agent would not wake up and join a room, whereas you re asking about how to PREVENT agents joining a room.

Dispatches refer to agent dispatches, whether they are explicitly dispatched or dispatched automatically, the process is an agent in the project will join the specified room. Your project does not have any agents in it, so it would not be possible for an agent to join any room.

I’m basing that on your description of your project as “without AI agents”, and I also do not see any agents deployed to the project associated with your account.

To answer your specific questions though:

> [@erick\_ortiz](#):
>
> 1. Is there an officially supported way to prevent **all automatic agent jobs** in human-only LiveKit Cloud rooms, including when a room is created, a participant joins, or the first media track is published?

Yes, always provide your agents with an `agent_name`.

> [@erick\_ortiz](#):
>
> 1. If a project has no unnamed agent workers registered, can an automatically created dispatch ever result in a job later?

No, automatic dispatches require unnamed agents (and are not recommended)

> [@erick\_ortiz](#):
>
> 1. How can we verify all workers currently registered with our project, including externally hosted workers, rather than just LiveKit-managed agent deployments?

Assuming you are referring to a malicious actor creating an externally hosted worker, they would need your API key in order to connect to your LiveKit instance. Your LiveKit cloud dashboard will list ALL agents (including externally hosted ones) at [https://cloud.livekit.io/projects/p\_/agents](https://cloud.livekit.io/projects/p_/agents)

> [@erick\_ortiz](#):
>
> 1. Would you recommend any additional preventive controls for rooms that should never admit an AI agent?

You have complete control over whether agents get dispatched to your rooms, name all your agents and check your code base for agents being dispatched via API, agents being dispatched via token, or agents being dispatched by a SIP dispatch rule. The docs page at [Agent dispatch | LiveKit Documentation](https://docs.livekit.io/agents/server/agent-dispatch/#deployments) is a good place to start.

---

_[View the full topic](https://community.livekit.io/t/how-to-prevent-automatic-agent-jobs-in-human-only-livekit-cloud-rooms/2457)._
