Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #697] [FEAT]: Improved CSV Chat Exports #402

New Issue
Closed
opened 2026-02-22 18:19:19 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:19:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @timothycarambat on GitHub (Feb 8, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/697

Originally assigned to: @shatfield4 on GitHub.

What would you like to see?

Currently, the CSV export of chats is not very helpful to an admin. The workspace chat export as a csv will likely be used for auditing, review, RLHF, or just general filtering and usage analysis.

The csv currently only exports the message and response, which are important but we should be as verbose as possible when doing the CSV export.

We should have the following columns in the table at a minimum:

  • id
  • username
  • workspace_name
  • prompt
  • response
  • sent_at

This format will be more helpful when we implement metrics on chats like token use, chat_model, and more. So this implementation should be easily extensible to add new metrics without much lift.

Originally created by @timothycarambat on GitHub (Feb 8, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/697 Originally assigned to: @shatfield4 on GitHub. ### What would you like to see? Currently, the CSV export of chats is not very helpful to an admin. The workspace chat export as a csv will likely be used for auditing, review, RLHF, or just general filtering and usage analysis. The csv currently only exports the message and response, which are important but we should be as verbose as possible when doing the CSV export. We should have the following columns in the table at a **minimum**: - `id` - `username` - `workspace_name` - `prompt` - `response` - `sent_at` This format will be more helpful when we implement metrics on chats like token use, chat_model, and more. So this implementation should be easily extensible to add new metrics without much lift.
yindo added the enhancementcore-team-onlyfeature request labels 2026-02-22 18:19:19 -05:00
yindo closed this issue 2026-02-22 18:19:19 -05:00
yindo changed title from [FEAT]: Improved CSV Chat Exports to [GH-ISSUE #697] [FEAT]: Improved CSV Chat Exports 2026-06-05 14:35:07 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label core-team-only enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#402
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?