feat(moltbook): Add follow feature and reply to own post comments#943
Merged
feat(moltbook): Add follow feature and reply to own post comments#943
Conversation
- Add ability for Addie to respond to comments on her own posts - Add follow/unfollow functionality to build community - LLM evaluation for following relevant posters (advertising, ad tech, AI agents) - Daily follow limit of 10 to avoid spam - Database tracking for follow activity - Input validation for agent IDs - Migration for 'follow' activity type Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
bokelley
force-pushed
the
bokelley/moltbook-engagement
branch
from
5d7145f to
3bed314
Compare
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
Apr 25, 2026
Brings in our get_media_buys request-builder fix (adcp-client#987 closing #983), placeholder-ID enricher audit (#991), schema-aware brand/account injection in the storyboard runner (#943), the a2a_context_continuity validator (#962), A2A wire-shape capture (#904), and triage-bot ergonomics closing adcp#3121 (#992/#993). Two compat fixes: - **Hint type widening.** `StoryboardStepHint` widened from `ContextValueRejectedHint` alone to a five-kind union. `renderAllHintFixPlans` now accepts the broader type and filters to the kind it knows how to render. Other kinds drop silently from the fix-plan section but the runner's per-hint `message` field still surfaces them. - **Strict request-schema validation.** 5.18.0's runner rejects unknown fields. `pagination-integrity-property-lists.yaml`'s `list_type` field isn't in `create-property-list-request.json`'s properties (the schema has `additionalProperties: false`). Drop it — no handler reads the field. Multi-page upgrade for get_media_buys_pagination_integrity deferred — the SDK's convention extractor populates context.media_buy_id from the first-page response, then the request-builder injects that ID and turns page 2 into an ID-lookup. Filed adcp-client#998 with the diagnosis. Storyboard stays at single-step until the extractor fix lands. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2 tasks
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
1 participant
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.
Summary
Test plan
🤖 Generated with Claude Code