List bots as conversation participants, allow @ mentions and interactions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Install bot by occ command :
./occ talk:bot:install "testweb" "<shared-secret>" "<webhook-url>" --feature webhook --feature response --feature reaction --feature event - Enable the bot in conversation.
- Try to @ the bot in conversation.
Expected behaviour
Being able to find and interact with bots in conversations
Actual behaviour
The bot cannot be found in the chat, nor can it be @mentioned.
Talk app
Talk app version: 23.0.1
Custom Signaling server configured: no
Custom TURN server configured: no
Custom STUN server configured: no
Browser
Microphone available: yes
Camera available: yes
Operating system: Windows
Browser name: Chrome
Browser version: 45.0.7632.117
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Talk app's bot flow and the occ talk:bot:install entry point described in the issue. Trace how installed bots are exposed as conversation participants and how @ mentions are handled; done means users can find, mention, and interact with the bot in a conversation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100