package livekit-agents not found in any project files

Thanks for reaching out, Billy. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

when i run lk agent create

Thanks — I’m helping with the error you see when running

lk agent create

about "package livekit-agents not found." To diagnose quickly, please share: • Your OS and shell (e.g., macOS zsh, Ubuntu bash, Windows PowerShell) • Your

lk

CLI version (

lk version

output) • The exact command you ran and the full terminal output/errors • Whether you have a Python environment active and its version (

python --version

) • Whether you installed

livekit-agents

via pip and how (the exact pip command) • If you’re in a project repo, is there a local

livekit-agents

folder (monorepo) or do you expect to use the PyPI package? If you prefer, run these and paste the outputs: 1. lk version 2. python --version 3. pip show livekit-agents || echo "livekit-agents not installed" 4. ls -la (or

dir

) in your project root With those details I’ll give the exact steps to fix the

lk agent create

failure.

doesnt make much sense... i can run dev mode and no errors.. but i cant lk agent create

Thanks — I understand you can run in dev mode but

lk agent create

fails with the "package livekit-agents not found" error. That's most commonly because the build step uses your project’s declared dependencies (pyproject.toml), while dev mode uses your local env. Quick checks for me to diagnose and fix this: • Do you have a

pyproject.toml

in your project root? If yes, paste the

dependencies = [...]

section. • Run and paste outputs of: a.

lk version

b.

python --version

c.

cat pyproject.toml

(or

type pyproject.toml

on Windows) d.

lk agent create --log-type build

(full output if it fails) Immediate fix to try: 1. Add

livekit-agents

to

pyproject.toml

dependencies, for example:

[project]
dependencies = [
  "livekit-agents",
  # other deps...
]

1. Then run

lk agent create

again. If you prefer, paste your

pyproject.toml

and

lk agent create

error output and I’ll point out the exact change. Sources: Agents (Python) | livekit/livekit_composite | DeepWiki | Examples | livekit/livekit_composite | DeepWiki | Server-side | livekit/livekit_composite | DeepWiki

i dont have a pyporject.toml file... doesnt that get created automaticaally?

Good question —

pyproject.toml

is not created automatically by the CLI in every case. Dev mode uses your local environment (where livekit-agents may already be installed), but

lk agent create

builds a container and requires dependencies declared in

pyproject.toml

. You have two quick options: 1) Bootstrap a correct project (recommended) • Run:

lk agent init my-agent --lang python

This creates a starter project including

pyproject.toml

with

livekit-agents

listed. 2) Add

pyproject.toml

manually • Create a

pyproject.toml

in your project root with at least:

[build-system]
requires = ["setuptools","wheel"]
build-backend = "setuptools.build_meta"

[project]
name = "my-agent"
version = "0.1.0"
dependencies = [
  "livekit-agents",
  # add any other plugins you need, e.g. "livekit-plugins-silero"
]

• Then run:

lk agent create

If you want, paste your project folder listing or tell me whether you prefer bootstrapping or manual creation and I’ll give the exact file content tailored to your agent.

is that new? i have other agents that did require this

Short answer: Yes — the CLI’s build/deploy step requires dependencies declared in

pyproject.toml

(or an equivalent lock) because

lk agent create

builds a container and installs deps from your project files, while

dev

mode uses your local environment. That difference can make this feel new even if your older agents worked without the file. Why it changed / why you saw a difference: • Dev mode runs against your local Python environment (so global/venv installs work). •

lk agent create

performs a clean build and needs explicit dependency metadata in

pyproject.toml

so the container can install

livekit-agents

and plugins. • Some older CLI versions or starter templates may have implicitly handled deps; newer tooling enforces the manifest to ensure reproducible builds. What you can do now (quick options): • Bootstrap a proper project:

lk agent init my-agent --lang python

(creates

pyproject.toml

). • Or add this minimal

pyproject.toml

to your project root:

[build-system]
requires = ["setuptools","wheel"]
build-backend = "setuptools.build_meta"

[project]
name = "my-agent"
version = "0.1.0"
dependencies = [
  "livekit-agents",
  # add plugins like "livekit-plugins-silero" or others you use
]

Want me to generate a tailored

pyproject.toml

for one of your existing agents? If so, tell me the agent name and which plugins (silero, openai, deepgram, etc.) you need.

did not require*

Thanks — got it. You're right to correct that wording. Short answer: Older agents/CLI versions sometimes worked without a

pyproject.toml

because dev mode used your local environment or older tooling implicitly handled deps. The current

lk agent create

build enforces an explicit dependency manifest so the containerized build can install

livekit-agents

reliably. That’s why you can run in dev but creation fails. I can help in two ways — tell me which you prefer: • I can generate a minimal

pyproject.toml

for your existing agent (tell me agent name and which plugins you need: silero, openai, deepgram, etc.). • Or I can show the exact commands to bootstrap a new starter project:

lk agent init my-agent --lang python

. Which would you like?

Seems to be working now. thanks

Short answer: Not directly — two agents can share a room only if they use credentials (access tokens) from the same LiveKit project. Details: • Rooms are scoped to a LiveKit project (API key + server). To join a room an agent must present a token issued by that project. • If each agent is using different account credentials, they cannot join the same room unless one side uses a token from the other project (or a shared project). • Cross-account setups require a workaround such as a bridge/proxy that relays media between rooms in different projects. • Also note: agents ignore other agents by default for audio; enable agent-to-agent audio with

RoomInputOptions(allow_agent_input=True)

when you want them to hear each other. If you want, tell me: • Whether the agents are in separate LiveKit projects or can share a project, • And whether you want them to exchange audio/video or just data — I’ll suggest the best setup. Sources: How to Enable Agent-to-Agent Speech Detection in LiveKit