github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #5355] Groq's "name" option within "messages" parameter of the chat endpoint payload #65390

New Issue
Open
opened 2026-05-03 21:08:36 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-03 21:08:36 -05:00
Owner
Copy Link

Originally created by @pmgh2345 on GitHub (Jun 28, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5355

Groq has a really helpful option within the "messages" parameter that one would provide in the payload to their chat completion API that helps the model distinguish between multiple users of the same role. This is helpful for situations in which a multi-agent conversation is taking place and there is more than one agent in a given role--for example, a roleplay in which we want to differentiate between an assistant representing one personality with its own system prompt talking to another assistant representing another agent with its own system prompt, all chatting with the user role.

For more on this, please see the following link to the Groq docs https://console.groq.com/docs/text-chat under the "messages" parameter.

Originally created by @pmgh2345 on GitHub (Jun 28, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5355 Groq has a really helpful option within the "messages" parameter that one would provide in the payload to their chat completion API that helps the model distinguish between multiple users of the same role. This is helpful for situations in which a multi-agent conversation is taking place and there is more than one agent in a given role--for example, a roleplay in which we want to differentiate between an assistant representing one personality with its own system prompt talking to another assistant representing another agent with its own system prompt, all chatting with the user role. For more on this, please see the following link to the Groq docs https://console.groq.com/docs/text-chat under the "messages" parameter.
GiteaMirror added the feature requestapi labels 2026-05-03 21:08:36 -05:00
GiteaMirror commented 2026-05-03 21:08:37 -05:00
Author
Owner
Copy Link

@marklysze commented on GitHub (Jun 28, 2024):

@pmgh2345, would you know what that actually does? If you asked the question "What is my name" would Groq respond with what was in that field?

<!-- gh-comment-id:2197301806 --> @marklysze commented on GitHub (Jun 28, 2024): @pmgh2345, would you know what that actually does? If you asked the question "What is my name" would Groq respond with what was in that field?
GiteaMirror commented 2026-05-03 21:08:38 -05:00
Author
Owner
Copy Link

@pmgh2345 commented on GitHub (Jun 28, 2024):

@marklysze I believe that is the intention provided that the last message of the payload makes use of this parameter with the "user" role, however, I don't have Groq to confirm whether or not the model will actually discern a conventional "name" as such, or whether it simply uses the different names to discern one point of view vis a vis another in those situations where this is relevant.

<!-- gh-comment-id:2197637797 --> @pmgh2345 commented on GitHub (Jun 28, 2024): @marklysze I believe that is the intention provided that the last message of the payload makes use of this parameter with the "user" role, however, I don't have Groq to confirm whether or not the model will actually discern a conventional "name" as such, or whether it simply uses the different names to discern one point of view vis a vis another in those situations where this is relevant.
GiteaMirror commented 2026-05-03 21:08:38 -05:00
Author
Owner
Copy Link

@marklysze commented on GitHub (Jun 28, 2024):

Thanks @pmgh2345, sounds interesting...

<!-- gh-comment-id:2197762949 --> @marklysze commented on GitHub (Jun 28, 2024): Thanks @pmgh2345, sounds interesting...
GiteaMirror commented 2026-05-03 21:08:39 -05:00
Author
Owner
Copy Link

@acerix commented on GitHub (Dec 13, 2025):

As an example, llmcord supports name to make messages in a conversation "user identity aware" so the users can be mentioned in replies, specified by this system prompt:

User's names are their Discord IDs and should be typed as '<@ID>'

0a29e100ef/llmcord.py (L251)

<!-- gh-comment-id:3649794224 --> @acerix commented on GitHub (Dec 13, 2025): As an example, [llmcord](https://github.com/jakobdylanc/llmcord) supports `name` to make messages in a conversation "user identity aware" so the users can be mentioned in replies, specified by this system prompt: `User's names are their Discord IDs and should be typed as '<@ID>'` https://github.com/jakobdylanc/llmcord/blob/0a29e100efccb806539793016e72951e273756ad/llmcord.py#L251
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label api feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#65390
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?