Conversation
Contributor
Author
|
Demo against the agent-test-arena project: a legacy cloud-regions.mp4 |
`lk agent create` and `lk agent config` write [agent] name alongside id. The prebuilt-image create path calls CreateAgent directly since the SDK's RegisterAgent wrapper drops the name from the response.
[agent] id becomes [cloud] id, or one [cloud.<region>] id per region for agents deployed to several regions. A legacy [agent] id is still read and migrates to [cloud] on the next save.
lk agent create and lk agent config record the new agent under [cloud] id. Creating with --region into a file that already has an agent adds a [cloud.<region>] entry instead of replacing it. lk agent deploy deploys every region the file lists, or the one passed with --region; the other agent commands prompt for a region when the file lists several.
u9g
force-pushed
the
jason/toml-cloud-regions
branch
from
September 23, 2026 13:57
df44e3e to
ebb16ad
Compare
u9g
changed the title
livekit.toml holds a single [cloud] id. `lk agent create --region` replaces the agent instead of adding a region entry, `lk agent deploy` deploys the one agent, and the other agent commands no longer prompt for a region.
u9g
force-pushed
the
jason/toml-cloud-regions
branch
from
September 23, 2026 14:59
ebb16ad to
b5e1e6b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
livekit.tomlshould say which agent it is and where that agent runs on LiveKit Cloud, as separate things. Right now the Cloud Agents id sits under[agent], and the agent's name isn't recorded anywhere. Proposal: https://app.notion.com/p/livekit/Proposal-livekit-toml-layout-for-agent-name-and-regions-3d83c4901a4281beb3b9f1f3e74de44dWhat
lk agent createandlk agent confignow write the agent's Cloud-assigned name to[agent] nameand its id to a new[cloud]block:Older files that still have
[agent] idkeep working. The id is read into[cloud]on load and saved there the next time the file is written. A self-hosted agent can have[agent] namewith no[cloud]block at all.The prebuilt-image create path now calls
CreateAgentdirectly, because the SDK'sRegisterAgentwrapper drops the name from the response.This PR supports one agent per file only; per-region
[cloud.<region>]tables are out of scope. No server or protocol changes.Verification
go build ./...,go vet ./cmd/lk ./pkg/config, andgo test ./pkg/config ./cmd/lkpass. The newpkg/config/livekit_test.gocovers moving a legacy id into[cloud], loading[cloud] id, and the exact saved layout.