Skip to content

Include parent_chat_id in subagent postRequest hooks#511

Closed
itkonen wants to merge 1 commit into
editor-code-assistant:masterfrom
itkonen:fix/subagent-postrequest-parent-chat-id
Closed

Include parent_chat_id in subagent postRequest hooks#511
itkonen wants to merge 1 commit into
editor-code-assistant:masterfrom
itkonen:fix/subagent-postrequest-parent-chat-id

Conversation

@itkonen

@itkonen itkonen commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Include parent_chat_id in subagent postRequest hook payloads.
  • Document the subagent-specific field and cover it in hook lifecycle tests.
  • Keeps postRequest valid for both primary and subagent chats while allowing hooks to distinguish them.

Follow-up to #505.

  • I added a entry in changelog under unreleased section.
  • This is not an AI slop.

🤖 Generated with ECA (openai/gpt-5.5 - high)

Expose parent_chat_id in subagent postRequest payloads so hooks can distinguish primary chat completions from subagent completions without changing postRequest semantics.

🤖 Generated with [ECA](https://eca.dev) (openai/gpt-5.5 - high)

Co-Authored-By: eca-agent <git@eca.dev>
@itkonen

itkonen commented Jun 20, 2026

Copy link
Copy Markdown
Contributor Author

Closing this because #508 was merged after the follow-up discussion clarified the intended behavior: postRequest should be primary-chat only, and subagents should use subagentPostRequest.

This PR was based on the earlier interpretation that postRequest should remain shared and expose parent_chat_id, so it now conflicts with the accepted direction.

@itkonen itkonen closed this Jun 20, 2026
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