Skip to content

fix: persist agent respond-to edits; quiet partition overlap errors#2505

Open
Chessing234 wants to merge 2 commits into
block:mainfrom
Chessing234:fix/respond-to-partitions
Open

fix: persist agent respond-to edits; quiet partition overlap errors#2505
Chessing234 wants to merge 2 commits into
block:mainfrom
Chessing234:fix/respond-to-partitions

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • Edit a custom agent definition’s respond-to to Anyone, restart the agent, confirm harness log shows respond_to=anyone
  • Same for Allowlist with a member pubkey
  • Fresh migrate + relay start: no Failed to ensure partitions ERROR for current month vs *_p_future

Made with Cursor

Chessing234 and others added 2 commits July 23, 2026 15:04
Who-can-talk edits on a persona only wrote definition_respond_to; the harness reads instance respond_to, so linked agents stayed owner-only.

Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Match on the overlap message alone so missing SQLSTATE 42P17 no longer logs ERROR on every boot against *_p_future.

Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant