Fix(runtime): Ensure agent creation handles missing agent gracefully #6007
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.
Fixes #6003
Relates to
Fixes runtime crash when getAgent() fails due to missing agents table or undefined character.id.
Risks
Low – affects only agent initialization during startup.
Background
AgentRuntime previously crashed if the agents table was missing or if no agent record was found. This PR ensures runtime startup by handling errors gracefully and creating the agent when necessary.
What does this PR do?
Wraps getAgent() in try/catch.
Falls back to createAgent() if no agent exists.
Logs clear error if character.id is missing.
Type of change
Bug fix – non-breaking, improves startup resilience.
Testing
Start runtime with a new Postgres DB (no agents table).
Start runtime with character config missing id.
Verify runtime does not crash and agent is created or error is logged clearly.
Note
Wrap ensureAgentExists lookup/update in try/catch with error logging; on failure or absence, proceed to create the agent.
packages/core/src/runtime.ts)Written by Cursor Bugbot for commit 0aaaf69. This will update automatically on new commits. Configure here.