nextcloud / nextcloud/talk_bot_ai
Feature Request: Forward Nextcloud User Identity LLM
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 24
- Forks
- 7
- Avg merge
- 7h 57m
- Merged PRs (30d)
- 3
Description
Summary
Forward the originating Nextcloud Talk user identity (username and/or user ID) to LLM with every request, allowing LLM to maintain user-specific memory, preferences, sessions, tasks, and personalization.
Problem
The current Nextcloud Assistant forwards messages from Nextcloud Talk to LLM, but LLM does not receive a stable user identity that can be used for user-specific memory mapping.
Describe the solution you'd like
Extract the originating user information from the Nextcloud Talk webhook payload and forward it to LLM as a dedicated identity field.
Describe alternatives you've considered
none
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 by tracing the Nextcloud Talk webhook payload and the existing path that forwards messages to the LLM. Confirm which originating username or user ID is available, then verify that a dedicated identity field reaches the LLM with every request and supports user-specific mapping.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100