cuddly-kite-65599
09/19/2025, 9:33 AMtall-airline-16756
09/19/2025, 9:33 AMtall-airline-16756
09/19/2025, 9:33 AMlk project set-default PROJECT_NAME
Just replace PROJECT_NAME with the name of the project you'd like to set as your default.
If you're adding a project and want to set it as default right away, you can include the --default flag like this:
lk project add PROJECT_NAME --url LIVEKIT_URL --api-key API_KEY --api-secret API_SECRET --default
And if you ever want to double-check which project is currently set as default, just list all your projects with:
lk project list
You'll see an asterisk (*) next to the default project in the list. If you have any questions or need further assistance, feel free to ask!
Sources: LiveKit CLI project management | LiveKit Docscuddly-kite-65599
09/19/2025, 9:34 AMtall-airline-16756
09/19/2025, 9:34 AMlk agent logs
• And if you're looking to view build logs, this command will do the trick:
lk agent logs --log-type=build
Just a quick note: LiveKit Cloud doesn’t store runtime logs, so you’ll only be able to see them while tailing in real-time.
For keeping logs longer or diving deeper with analysis, you can forward them to external services like Datadog, CloudWatch, Sentry, or New Relic. You can set this up by configuring the right secrets with:
lk agent update-secrets
If you’d like a hand setting up log forwarding to any specific service, please don’t hesitate to ask—I’m here to help!
Sources: Log collection | LiveKit Docs | Agent deployment CLI reference | LiveKit Docs | Logs, metrics, and telemetry | LiveKit Docs | Deploying to production | LiveKit Docs | Log collection | LiveKit Docs