feat(chat): introduce chat functionality to CLI#25
Closed
jsandai wants to merge 1 commit intoanyproto:mainfrom
Closed
feat(chat): introduce chat functionality to CLI#25jsandai wants to merge 1 commit intoanyproto:mainfrom
jsandai wants to merge 1 commit intoanyproto:mainfrom
Conversation
Add chat support to anytype-cli, enabling interaction with Anytype chat objects for the first time. This brings messaging capabilities to the headless CLI that were previously only available in the desktop app. New commands: - chat find <space-id> - Discover chat objects in a space - chat send <chat-id> - Send messages (with --reply-to support) - chat list <chat-id> - List messages with pagination - chat edit <chat-id> - Edit existing messages - chat delete <chat-id> - Delete messages - chat react <chat-id> - Toggle emoji reactions - chat read <chat-id> - Mark messages as read Implementation: - Add core/chat.go with gRPC bindings for chat operations - Add ChatMessage and ChatInfo types for structured data - Increase gRPC timeout to 120s for slower operations - Add unit tests for message parsing Documentation: - Update README with Chat Operations section
|
I just opened anyproto/anytype-heart#2915 which adds chat endpoints to the API. I think that approach is more consistent with how |
3 tasks
9 tasks
Contributor
Author
|
Closing this PR — the Chat REST API in anyproto/anytype-heart#2915 provides a cleaner approach for programmatic chat access. CLI chat commands are no longer needed when the REST API is available. Thanks for considering this! The self-hosted network support PRs (#21, #22) remain relevant and separate from this. |
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
2 participants
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.
Description
This PR introduces chat support to anytype-cli, enabling programmatic interaction with Anytype's messaging feature for the first time.
This brings messaging capabilities to the headless CLI that were previously only available in the desktop app, unlocking automation use cases like chat bots, notification integrations, conversation archiving, and bridging Anytype chats with other platforms.
New commands:
chat find <space-id>chat send <chat-id> <message>--reply-tosupport)chat list <chat-id>chat edit <chat-id> <msg-id> <text>chat delete <chat-id> <msg-id>chat react <chat-id> <msg-id> <emoji>chat read <chat-id>Changes:
cmd/chat/— New command group with 7 subcommandscmd/root.go— Register chat commandcore/chat.go— gRPC bindings for chat operationscore/chat_test.go— Unit tests for message parsingcore/client.go— Increase gRPC timeout to 120sREADME.md— Documentation with usage examplesWhat type of PR is this? (check all applicable)
Related Tickets & Documents
This addresses the need for chat functionality discussed in the community. No existing issue tracked.
Mobile & Desktop Screenshots/Recordings
N/A — CLI feature, no visual changes.
Added tests?
Unit tests added for message parsing (
core/chat_test.go).Added to documentation?
Added "Chat Operations" section with getting started guide and command examples.
[optional] Are there any post-deployment tasks we need to perform?
None.