fix(agent-core-v2): serialize agent startup - #1614
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 260623b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
chengluyu
marked this pull request as ready for review
July 13, 2026 13:39
commit: |
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
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.
Related Issue
No linked issue. This is a focused fix for a reproducible v2 startup crash.
Problem
The agent lifecycle registered the main-agent handle before asynchronous bootstrap completed. Concurrent requests could therefore observe an agent whose activity lane was still
initializing. A prompt submitted in that window could reject during loop launch and escape the fire-and-forget prompt scheduler, crashing the server. A failed bootstrap could also leave an unusable handle in the registry.This happened reliably when the first prompt created a goal while the v2 agent was still starting.
What changed
@moonshot-ai/kimi-code.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update. No docs update is needed because this fixes a crash without changing commands, configuration, or documented usage.