Skip to content

Use threaded replies for comments on own posts#24

Merged
jackparnell merged 1 commit intomainfrom
feature/threaded-comment-replies
Apr 7, 2026
Merged

Use threaded replies for comments on own posts#24
jackparnell merged 1 commit intomainfrom
feature/threaded-comment-replies

Conversation

@ColonistOne
Copy link
Copy Markdown
Collaborator

Summary

When the agent replies to a comment on its own post, it now creates a threaded reply (using parent_id) instead of a top-level comment. This makes conversations appear as actual nested threads in the Colony UI.

Before: Alice comments on the agent's post, the agent replies as a new top-level comment — looks disconnected.

After: Alice comments, the agent's reply appears directly under Alice's comment as a thread.

Changes

  • _check_replies_to_own_post passes parent_id=comment_id to create_comment
  • Browse-and-engage comments remain top-level (commenting on the post itself, not replying to anyone)
  • Bumped colony-sdk dependency to >=1.3.0 (added parent_id support in colony-sdk-python#6)

Depends on

  • colony-sdk 1.3.0 (just released to PyPI)

Test plan

  • Reply to own post comment uses parent_id
  • Browse comments stay top-level (no parent_id)
  • 171 tests pass, ruff + mypy clean

🤖 Generated with Claude Code

Replies to comments on the agent's own posts now use parent_id
to create proper threaded replies instead of top-level comments.
This makes conversations appear as actual back-and-forth threads
in the UI rather than a flat list of disconnected comments.

- Bump colony-sdk dependency to >=1.3.0 (parent_id support)
- _check_replies_to_own_post passes parent_id=comment_id
- Browse-and-engage comments remain top-level (no parent_id)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jackparnell jackparnell merged commit 7251a01 into main Apr 7, 2026
4 of 8 checks passed
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.

2 participants