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

[GH-ISSUE #3381] [FEAT]: Small UI enhancements #2177

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

Originally created by @SeaDude on GitHub (Mar 2, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3381

Originally assigned to: @shatfield4 on GitHub.

What would you like to see?

Hello,

Here are some small UI enhancements that would make AnythingLLM easier to use (for me at least!):

  1. CREATING NEW WORKSPACES:
    a. When clicking New Workspace, make the popup active (cursor placed in the name textbox) so I can just start typing the Workspace name.
  2. EDITING WORKSPACE SETTINGS:
    a. Suggestion: Group the Back and the Update Workspace buttons on the Edit Workspace Screen.
    b. When returning from editing the main AnythingLLM settings (wrench icon), the workspace that I was working with is not active.
    - I have to scroll all the way down and select the workspace again.
    - IDEALLY: Both the Workspace and the thread I had previously been working with are active upon returning from the Edit Settings Screen.
    - BONUS!: The above + the Workspace nav is scrolled to the Workspace and Thread.
  3. o-MODEL RENDERING:
    a. I notice that output from the o* models does not render code between triple backticks.
    - If I use a different model (gpt-4o), the code is rendered within triple backticks.
    - Not sure if this is something AnythingLLM can control...
    - Example output from o3-mini:
    - Image
    - Example output from gpt-4o:
    - Image

These may be OS-specific not sure. I'm on the Linux version of AnythingLLM.

Originally created by @SeaDude on GitHub (Mar 2, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3381 Originally assigned to: @shatfield4 on GitHub. ### What would you like to see? Hello, Here are some **small** UI enhancements that would make AnythingLLM easier to use (for me at least!): 1. **CREATING NEW WORKSPACES**: a. When clicking `New Workspace`, make the popup active (cursor placed in the name textbox) so I can just start typing the Workspace name. 2. **EDITING WORKSPACE SETTINGS**: a. Suggestion: Group the `Back` and the `Update Workspace` buttons on the Edit Workspace Screen. b. When returning from editing the main AnythingLLM settings (wrench icon), the workspace that I was working with is not active. - I have to scroll all the way down and select the workspace again. - IDEALLY: Both the Workspace **and** the thread I had previously been working with are active upon returning from the Edit Settings Screen. - BONUS!: The above + the Workspace nav is scrolled to the Workspace and Thread. 3. **o-MODEL RENDERING**: a. I notice that output from the o* models does not render code between triple backticks. - If I use a different model (gpt-4o), the code is rendered within triple backticks. - Not sure if this is something AnythingLLM can control... - Example output from `o3-mini`: - ![Image](https://github.com/user-attachments/assets/89126af2-225e-4345-ab6b-5b32f7b7abbe) - Example output from `gpt-4o`: - ![Image](https://github.com/user-attachments/assets/52ec3437-fc30-44e5-b2ec-cf0fcc2d01a7) These may be OS-specific not sure. I'm on the Linux version of AnythingLLM.
yindo added the enhancementfeature request labels 2026-02-22 18:28:29 -05:00
yindo closed this issue 2026-02-22 18:28:29 -05:00
yindo commented 2026-02-22 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@ericthomas1 commented on GitHub (Mar 18, 2025):

Thank you for addressing this little things!

I didn't see the o* model rendering issue in the UI/UX Improvements.

For some reason whenever selecting an o* model, the output markdown is not respected. Here you can see the bulleted lists are rendered in-line rather than in bullet format.

Image

Same thing with output that should be rendered as formatted text (surrounded by triple backticks). Non o* models render output just fine, but the reasoning models output is not rendered correctly in AnythingLLM.

@ericthomas1 commented on GitHub (Mar 18, 2025): Thank you for addressing this little things! I didn't see the o* model rendering issue in the UI/UX Improvements. For some reason whenever selecting an `o*` model, the output markdown is not respected. Here you can see the bulleted lists are rendered in-line rather than in bullet format. ![Image](https://github.com/user-attachments/assets/f039ba2b-b141-4542-aa35-14daa2c574e5) Same thing with output that should be rendered as formatted text (surrounded by triple backticks). Non `o*` models render output just fine, but the reasoning models output is not rendered correctly in AnythingLLM.
yindo commented 2026-02-22 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 18, 2025):

Click on the edit (pencil) icon below the response. The O* model might just not be returning markdown in an expected format and I'm curious as to what format it did return

@timothycarambat commented on GitHub (Mar 18, 2025): Click on the edit (pencil) icon below the response. The O* model might just not be returning markdown in an expected format and I'm curious as to what format it _did_ return
yindo commented 2026-02-22 18:28:29 -05:00
Author
Owner
Copy Link
Copy Source

@ericthomas1 commented on GitHub (Mar 18, 2025):

For o* models, when I click the pencil icon, the text has no triple backticks anywhere. The code blocks are not rendered correctly.

As rendered:

Image

Clicking the pencil icon:

Image

The raw response is formatted correctly, but again, no triple backticks anywhere.

If I change the model to gpt-4o:

As rendered:

Image

Clicking the pencil icon:

Image

I'd be surprised if the reasoning models didn't provide triple backticks...hm

@ericthomas1 commented on GitHub (Mar 18, 2025): For `o*` models, when I click the pencil icon, the text has no triple backticks anywhere. The code blocks are not rendered correctly. **As rendered**: ![Image](https://github.com/user-attachments/assets/2705ffb0-b1cd-419b-ae77-7e43e7e7bb38) **Clicking the pencil icon:** ![Image](https://github.com/user-attachments/assets/c292f74f-ca93-4e0f-8047-c7c22e50a595) The raw response is formatted correctly, but again, no triple backticks anywhere. If I change the model to `gpt-4o`: **As rendered:** ![Image](https://github.com/user-attachments/assets/bf3d88b8-4e3a-45c5-a72b-62ee5d6fec83) **Clicking the pencil icon:** ![Image](https://github.com/user-attachments/assets/01e50175-5da0-4509-83f5-fe7636903864) I'd be surprised if the reasoning models didn't provide triple backticks...hm
yindo commented 2026-02-22 18:28:30 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 19, 2025):

That is something we have been seeing only with o* models. I have no idea why, by default, a code block is not markdown escaped. I can say though that if you specifically tell the model to use markdown rendering it will work.

So weird every GPT generation prior would do markdown blocks by default and now O* models decide to not go that route.

@timothycarambat commented on GitHub (Mar 19, 2025): That is something we have been seeing _only_ with `o*` models. I have no idea why, by default, a code block is not markdown escaped. I can say though that if you specifically _tell the model_ to use markdown rendering it will work. So weird every GPT generation prior would do markdown blocks by default and now O* models decide to not go that route.
yindo changed title from [FEAT]: Small UI enhancements to [GH-ISSUE #3381] [FEAT]: Small UI enhancements 2026-06-05 14:45:01 -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 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#2177
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?