white-sugar-85462
09/12/2025, 12:07 AMtall-airline-16756
09/12/2025, 12:08 AMtall-airline-16756
09/12/2025, 12:08 AMrun_app()
function in your script is being called with an unexpected keyword argument, download_files_fnc
. This usually means there's a mismatch between how the CLI command is set up and what run_app()
expects.
To help you get the download-files
command working smoothly in the LiveKit CLI, here are some friendly steps to follow:
1. First, make sure all your plugins are properly registered so their downloadFiles()
method gets called. For instance, you can register each plugin like this: Plugin.registerPlugin(new EOUPlugin())
.
2. Next, define the download-files
command in your CLI. If you're using Python, here's a simple way to do it:
@cli.command(help="Download plugin dependency files")
@click.option("--log-level", default="DEBUG", ...)
def download_files(log_level: str) -> None:
setup_logging(log_level, True, False)
for plugin in Plugin.registered_plugins:
<http://logger.info|logger.info>(f"Downloading files for {plugin}")
plugin.download_files()
If you're working with Node.js, you can set it up like this:
program
.command('download-files')
.description('Download plugin dependency files')
.action(() => {
const options = program.optsWithGlobals();
initializeLogger({ pretty: true, level: options.logLevel });
const logger = log();
const downloadFiles = async () => {
for (const plugin of Plugin.registeredPlugins) {
await plugin.downloadFiles();
}
};
downloadFiles().finally(() => process.exit(0));
});
1. Finally, remember to run the download-files
command during your Docker image build phase to pre-download all dependencies. For example:
RUN python my_agent.py download-files
This step helps cache all the needed assets locally inside the container, which can really speed up startup time and make things more reliable.
If youâd like, Iâm here to help you debug this further or walk you through the implementationâjust let me know!
Sources: rag/README.md | livekit-plugins/livekit-plugins-turn-detector/README.md | plugins/livekit/src/index.ts | Builds and Dockerfiles | LiveKit Docs | pkg/agentfs/examples/python.uv.Dockerfilewhite-sugar-85462
09/12/2025, 12:10 AMtall-airline-16756
09/12/2025, 12:10 AMlk agent update-secrets CA_YNVhVUT7nKHg --secrets-file secrets.env --overwrite
. This command updates the secrets (environment variables) for your LiveKit agent with the ID CA_YNVhVUT7nKHg
. Here's a little breakdown to make it clearer:
⢠`--secrets-file secrets.env`: This tells the command to use a file named secrets.env
that contains your secrets as key-value pairs in the format KEY=VALUE
, one on each line.
⢠`--overwrite`: This flag means that all existing secrets for the agent will be deleted and replaced by the ones in your file. If you didnât use this, the new secrets would simply be added or updated without removing the old ones.
Once you run this command, the agent will restart automatically to apply these updated secrets. Rest assured, LiveKit Cloud securely encrypts and stores your secrets, and they are safely injected into the agent containers as environment variables when they run.
If anything feels unclear or if you need a hand with this process, please donât hesitate to reach outâIâm here to help!
Sources: Agent deployment CLI reference | LiveKit Docs | Secrets management | LiveKit Docs | Secrets management | LiveKit Docs