Repository navigation
Concepts: AI assistant bridge (ask_assistant) #619
Description
Branch: Open your PR against dev. PRs targeting main are closed automatically.
Description:
Write apps/backend/docs/concepts-ai-assistant-bridge.md: how the gateway's ask_assistant handler calls the AI agent and posts the reply into a conversation as a server-authored message via the shared fan-out helpers in lib/messageFanout.ts. This sits on the boundary of the E2EE model and needs a clear written statement of what it exposes.
Acceptance criteria:
- Traces the full request path: client event → rate-limit bucket
socket_ask_assistant→ HTTP call to the AI agent's/chat→ reply persisted and fanned out - Documents that the agent URL is currently hardcoded to
http://localhost:8000/chatinsocket/messaging.tsrather than read from configuration, and what that means for any non-local deployment - States plainly what plaintext leaves the client and reaches the backend and the AI agent when a user asks the assistant, and how a client should present that to the user
- Documents failure behaviour when the agent is unreachable or slow, and links to the AI agent API (Linked-devices management UI #302) and privacy boundary (File encryption/decryption wired into a real file-attach UI #355) docs
Activity
tyson-mill commentedon Oct 19, 2026
@tyson-mill has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @tyson-mill to this issue.
pratyushadk commentedon Oct 20, 2026
@pratyushadk has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @pratyushadk to this issue.
kosisochukwu1234 commentedon Oct 20, 2026
@kosisochukwu1234 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @kosisochukwu1234 to this issue.
Themancalledpg commentedon Oct 20, 2026
@Themancalledpg has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Themancalledpg to this issue.
drips-wave commentedon Oct 20, 2026
Congratulations, @Themancalledpg! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Themancalledpg: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
docs: message edit/delete semantics, AI assistant bridge, push decisi…
github-actions commentedon Oct 22, 2026
Closed by #680, merged into
dev.drips-wave commentedon Oct 22, 2026
This issue has been completed by @Themancalledpg as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Themancalledpg: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.