Are MCP and AI preferences completely broken?
For the past six months i’ve been using BoltAI, MCP and AI preferences have not worked for me. Yes, I have read all the posts and the web. New project chats do not inherit MCP server or default AI settings. New Projects do do not inherit MCP server or default AI settings. Preferences seem useless. I have to set all MCP server settings and the AI with every chat spawned to a project row. I have to set set all MCP server settings and the AI with every new Project. Also, there are three separate places to enter AI settings. Settings are a hot mess.

Nigel Protter 1 day ago
Bug Reports
Are MCP and AI preferences completely broken?
For the past six months i’ve been using BoltAI, MCP and AI preferences have not worked for me. Yes, I have read all the posts and the web. New project chats do not inherit MCP server or default AI settings. New Projects do do not inherit MCP server or default AI settings. Preferences seem useless. I have to set all MCP server settings and the AI with every chat spawned to a project row. I have to set set all MCP server settings and the AI with every new Project. Also, there are three separate places to enter AI settings. Settings are a hot mess.

Nigel Protter 1 day ago
Bug Reports
Support for Claude subscriptions (via Claude Code/CLI)
It would be great to have an option to use an Anthropic subscription for Claude models instead of requiring API access. Right now we can already connect a Chatgpt subscription via Codex CLI and a Gemini subscription via Gemini CLI, so it feels like a natural next step to support Claude subscriptions via Claude Code/CLI as well. I’m curious why there isn’t a similar option to use a Claude subscription through Claude Code/CLI. Honestly, this is the one missing feature that keeps BoltAI from being perfect for me, and it's the only thing holding me back from purchasing a Team Perpetual license for my department. It's also the main reason I've been tempted to switch to ChatWise, since it supports all three subscriptions (Claude, Chatgpt, and Gemini). But BoltAI is by far the better app, and I'd much rather stick with it. Is there a technical limitation that prevents BoltAI from using Claude Code/CLI in the same way it uses Codex CLI and Gemini CLI? Since Chatwise appears to support Claude subscriptions, I assume this should be technically possible, right? @Daniel Nguyen, is this something you would consider adding to BoltAI? I think it would be an extremely valuable feature, especially for users who already pay for Claude subscription. I would love to get your opinion on this.

Anıl Yuvalı 5 days ago
Feature Requests
Support for Claude subscriptions (via Claude Code/CLI)
It would be great to have an option to use an Anthropic subscription for Claude models instead of requiring API access. Right now we can already connect a Chatgpt subscription via Codex CLI and a Gemini subscription via Gemini CLI, so it feels like a natural next step to support Claude subscriptions via Claude Code/CLI as well. I’m curious why there isn’t a similar option to use a Claude subscription through Claude Code/CLI. Honestly, this is the one missing feature that keeps BoltAI from being perfect for me, and it's the only thing holding me back from purchasing a Team Perpetual license for my department. It's also the main reason I've been tempted to switch to ChatWise, since it supports all three subscriptions (Claude, Chatgpt, and Gemini). But BoltAI is by far the better app, and I'd much rather stick with it. Is there a technical limitation that prevents BoltAI from using Claude Code/CLI in the same way it uses Codex CLI and Gemini CLI? Since Chatwise appears to support Claude subscriptions, I assume this should be technically possible, right? @Daniel Nguyen, is this something you would consider adding to BoltAI? I think it would be an extremely valuable feature, especially for users who already pay for Claude subscription. I would love to get your opinion on this.

Anıl Yuvalı 5 days ago
Feature Requests
Custom Icon for Project in Toolbar
Maybe it’s silly but I’d love to be able to change the folder icon for each of my projects to an emoji of my choice. Then I can keep my projects apart visually. 🧠

Mandy Steinhardt 7 days ago
Feature Requests
Custom Icon for Project in Toolbar
Maybe it’s silly but I’d love to be able to change the folder icon for each of my projects to an emoji of my choice. Then I can keep my projects apart visually. 🧠

Mandy Steinhardt 7 days ago
Feature Requests
xAI Grok needs client side schema validation updated to support xhigh reasoning
Trying to use xhigh reasoning with Grok configured fails client side schema validation, it works when using an OpenAI compatible endpoint though with Grok configured.

Ben Kraus 11 days ago
Feature Requests
xAI Grok needs client side schema validation updated to support xhigh reasoning
Trying to use xhigh reasoning with Grok configured fails client side schema validation, it works when using an OpenAI compatible endpoint though with Grok configured.

Ben Kraus 11 days ago
Feature Requests
In Progress
Silent failures with Opus 5
Hi, I keep finding that Opus 5 requests fail silently. I put in a fairly long prompt, hit enter, it goes away thinking for awhile, then just stops. No response, no error, no nothing. Refreshing the prompt tends to create the same effect. If I switch to an OpenAi model, it then works. v 2.15.0 (build 84) on macOS 26.5.2

Eric Bowman 13 days ago
Bug Reports
In Progress
Silent failures with Opus 5
Hi, I keep finding that Opus 5 requests fail silently. I put in a fairly long prompt, hit enter, it goes away thinking for awhile, then just stops. No response, no error, no nothing. Refreshing the prompt tends to create the same effect. If I switch to an OpenAi model, it then works. v 2.15.0 (build 84) on macOS 26.5.2

Eric Bowman 13 days ago
Bug Reports
In QA
License immediately "forgotten"
Just purchased a Pro license for the latest-and-greatest BoltAI, entered the code, everything looked good: cute confetti animation, congrats, etc. However, I’m soon pestered to “Link Cloud Account” to recognize the license, but that keeps failing with “This license is not active”. Sure enough, when I click Settings went to the License tab, it claims that my license is revoked/deactivated. Restarting BoltAI doesn’t help. I just visited the License Manager web page, and everything looks fine / matches-up over there. Bizarre and (obviously) frustrating.

matti 18 days ago
Bug Reports
In QA
License immediately "forgotten"
Just purchased a Pro license for the latest-and-greatest BoltAI, entered the code, everything looked good: cute confetti animation, congrats, etc. However, I’m soon pestered to “Link Cloud Account” to recognize the license, but that keeps failing with “This license is not active”. Sure enough, when I click Settings went to the License tab, it claims that my license is revoked/deactivated. Restarting BoltAI doesn’t help. I just visited the License Manager web page, and everything looks fine / matches-up over there. Bizarre and (obviously) frustrating.

matti 18 days ago
Bug Reports
In Progress
web_fetch server_tool_use block sent without its tool_result → Anthropic 400 on next turn
OS version: macOS 26.6 BoltAI app version: 2.15.0 Setapp user: No AI provider & model: Anthropic, Claude (extended thinking on, web_fetch tool enabled) Steps to reproduce: Start an Anthropic chat with the web_fetch server tool enabled. Ask something that makes the model call web_fetch, and let it also emit regular tool_use blocks in the same assistant turn. Continue the conversation for at least one more turn. Error message: messages.1: web_fetch tool use with id srvtoolu_01RYeaAtRGtJzhpnvMWP8ys7 was found without a corresponding web_fetch_tool_result block What's actually wrong: When BoltAI rebuilds the messages array for the follow-up request, the web_fetch_tool_result block belonging to the MOST RECENT server_tool_use is dropped. Earlier web_fetch calls in the same thread are paired correctly — only the latest one loses its result. Once another turn is appended after it, that server_tool_use is a permanent orphan in the history and every subsequent request 400s. The chat is unrecoverable without editing history. Note on the error text: Anthropic reports the wrong index. It says "messages.1" but the id it quotes belongs to a much later assistant message. Match by block id, not by the index in the message. Expected: the web_fetch_tool_result is persisted alongside its server_tool_use and replayed in every subsequent request. Note: the 2.15.0 changelog entry about "Anthropic-powered chats occasionally failing after tool calls when using extended thinking" does not fix this — I'm on 2.15.0 and still hitting it.

Brendan DeBeasi 18 days ago
Bug Reports
In Progress
web_fetch server_tool_use block sent without its tool_result → Anthropic 400 on next turn
OS version: macOS 26.6 BoltAI app version: 2.15.0 Setapp user: No AI provider & model: Anthropic, Claude (extended thinking on, web_fetch tool enabled) Steps to reproduce: Start an Anthropic chat with the web_fetch server tool enabled. Ask something that makes the model call web_fetch, and let it also emit regular tool_use blocks in the same assistant turn. Continue the conversation for at least one more turn. Error message: messages.1: web_fetch tool use with id srvtoolu_01RYeaAtRGtJzhpnvMWP8ys7 was found without a corresponding web_fetch_tool_result block What's actually wrong: When BoltAI rebuilds the messages array for the follow-up request, the web_fetch_tool_result block belonging to the MOST RECENT server_tool_use is dropped. Earlier web_fetch calls in the same thread are paired correctly — only the latest one loses its result. Once another turn is appended after it, that server_tool_use is a permanent orphan in the history and every subsequent request 400s. The chat is unrecoverable without editing history. Note on the error text: Anthropic reports the wrong index. It says "messages.1" but the id it quotes belongs to a much later assistant message. Match by block id, not by the index in the message. Expected: the web_fetch_tool_result is persisted alongside its server_tool_use and replayed in every subsequent request. Note: the 2.15.0 changelog entry about "Anthropic-powered chats occasionally failing after tool calls when using extended thinking" does not fix this — I'm on 2.15.0 and still hitting it.

Brendan DeBeasi 18 days ago
Bug Reports
In Progress
Azure foundry models comms are broken
I have to disable streaming responses when using Azure foundry and mistral medium 3.5. Ideally it shouldn’t be required. The sequence that is occurring is that the stream delivers the reply normally across 7 chunks The endpoint sends a final chunk: {"choices":[], "usage":{...}} BoltAI reads choices[0].delta without checking the array is non-empty → undefined is not an object (evaluating 'g.delta') That trailing usage-only chunk is standard OpenAI streaming behaviour, and I confirmed the Foundry Mistral deployment emits it unconditionally on all three endpoint shapes — /openai/v1/, and the deployment path on both 2024-10-21 and 2025-01-01-preview. So there's no URL or api-version that avoids it; disabling streaming is the only client-side workaround. The means replies appear all at once rather than typing out. Everything else is unaffected.

Nick Dabner 22 days ago
Bug Reports
In Progress
Azure foundry models comms are broken
I have to disable streaming responses when using Azure foundry and mistral medium 3.5. Ideally it shouldn’t be required. The sequence that is occurring is that the stream delivers the reply normally across 7 chunks The endpoint sends a final chunk: {"choices":[], "usage":{...}} BoltAI reads choices[0].delta without checking the array is non-empty → undefined is not an object (evaluating 'g.delta') That trailing usage-only chunk is standard OpenAI streaming behaviour, and I confirmed the Foundry Mistral deployment emits it unconditionally on all three endpoint shapes — /openai/v1/, and the deployment path on both 2024-10-21 and 2025-01-01-preview. So there's no URL or api-version that avoids it; disabling streaming is the only client-side workaround. The means replies appear all at once rather than typing out. Everything else is unaffected.

Nick Dabner 22 days ago
Bug Reports
In Progress
Add "Reveal in Sidebar" or Folder Info for Search Results
Hi Daniel & the BoltAI team, First of all, thank you for making such a fantastic app! I’m currently organizing my threads using folders, but I frequently run into a small UX obstacle when searching for past chats: When I type a keyword into the search bar, the sidebar filters and correctly reveals the chat thread I am looking for. However, it is difficult to tell which folder/project the thread belongs to, as search results isolate the chat without showing its folder context. Clearing the search query doesn't automatically reveal or expand the chat’s parent folder in the sidebar, either. (Currently, the only way I can figure out its location is by triggering the "Move to..." menu and checking which folder is grayed out.) Additionally, the Chat Inspector (ⓘ) displays metadata like links and token usage, but doesn't mention the assigned folder/profile. Suggested Solutions: "Reveal in Sidebar" Option: Allow right-clicking a search result (or active chat) to jump directly to its location in the sidebar and highlight its parent folder. Folder Info in Inspector (ⓘ): Display the current folder/group name inside the Chat Inspector panel. Breadcrumbs: Show a small path indicator in the top header (e.g., Folder Name > Chat Title). This would make navigating large folder structures much smoother and significantly improve spatial context when managing multiple projects. Thanks for considering this!

Info 24 days ago
Feature Requests
In Progress
Add "Reveal in Sidebar" or Folder Info for Search Results
Hi Daniel & the BoltAI team, First of all, thank you for making such a fantastic app! I’m currently organizing my threads using folders, but I frequently run into a small UX obstacle when searching for past chats: When I type a keyword into the search bar, the sidebar filters and correctly reveals the chat thread I am looking for. However, it is difficult to tell which folder/project the thread belongs to, as search results isolate the chat without showing its folder context. Clearing the search query doesn't automatically reveal or expand the chat’s parent folder in the sidebar, either. (Currently, the only way I can figure out its location is by triggering the "Move to..." menu and checking which folder is grayed out.) Additionally, the Chat Inspector (ⓘ) displays metadata like links and token usage, but doesn't mention the assigned folder/profile. Suggested Solutions: "Reveal in Sidebar" Option: Allow right-clicking a search result (or active chat) to jump directly to its location in the sidebar and highlight its parent folder. Folder Info in Inspector (ⓘ): Display the current folder/group name inside the Chat Inspector panel. Breadcrumbs: Show a small path indicator in the top header (e.g., Folder Name > Chat Title). This would make navigating large folder structures much smoother and significantly improve spatial context when managing multiple projects. Thanks for considering this!

Info 24 days ago
Feature Requests
Constant halts using MCP file/directory reads/writes/searches per this:
BoltAI2's MCP file tools are thin wrappers around POSIX file APIs. They're designed for simplicity, not scale. The serializer bottleneck (JSON validation before payload size check) is architectural—it affects ANY tool in this MCP server that uses JSON parameter arrays. The serializer limit is a BoltAI2 server constraint, not a file-tool defect. Even if you swapped the underlying tool, you'd hit the same JSON validation ceiling on the MCP protocol layer. Better Strategy Than Tool Swapping: Instead of replacing BoltAI2's tools, adopt a hybrid workflow: For reads >100 kB: Use ripgrep-based search tools (no size limit on results). For writes >1,500 chars: Pre-split into chunks BEFORE calling edit_file (we're already doing this). For bulk file ops: Use the mcp__directory_tree_17ba7w to get the structure first, then target individual small edits. For escape-sensitive paths with spaces: NEVER use bash; always use the file tool wrappers.

Nigel Protter about 1 month ago
Bug Reports
Constant halts using MCP file/directory reads/writes/searches per this:
BoltAI2's MCP file tools are thin wrappers around POSIX file APIs. They're designed for simplicity, not scale. The serializer bottleneck (JSON validation before payload size check) is architectural—it affects ANY tool in this MCP server that uses JSON parameter arrays. The serializer limit is a BoltAI2 server constraint, not a file-tool defect. Even if you swapped the underlying tool, you'd hit the same JSON validation ceiling on the MCP protocol layer. Better Strategy Than Tool Swapping: Instead of replacing BoltAI2's tools, adopt a hybrid workflow: For reads >100 kB: Use ripgrep-based search tools (no size limit on results). For writes >1,500 chars: Pre-split into chunks BEFORE calling edit_file (we're already doing this). For bulk file ops: Use the mcp__directory_tree_17ba7w to get the structure first, then target individual small edits. For escape-sensitive paths with spaces: NEVER use bash; always use the file tool wrappers.

Nigel Protter about 1 month ago
Bug Reports
In Progress
Bug: Instant chat bar on Mac app enters endlessly looping spasm of thinking and responses
Your OS version. Tahoe 26.4.1 Your BoltAI app version. 2.14.0 (build 77) Are you a Setapp user. No. The AI provider & model you’re using. OpenRouter. DeepSeek V4 Flash. Steps to reproduce the issue. Start a chat with the instant chat bar. See the video below to see what happens maybe ~20% of the time. The error message. NA.

Matt about 1 month ago
Bug Reports
In Progress
Bug: Instant chat bar on Mac app enters endlessly looping spasm of thinking and responses
Your OS version. Tahoe 26.4.1 Your BoltAI app version. 2.14.0 (build 77) Are you a Setapp user. No. The AI provider & model you’re using. OpenRouter. DeepSeek V4 Flash. Steps to reproduce the issue. Start a chat with the instant chat bar. See the video below to see what happens maybe ~20% of the time. The error message. NA.

Matt about 1 month ago
Bug Reports
In QA
Error messages about API keys being encrypted
Tahoe 26.6 BoltAl 2 Version 2.14.0 (build 77) Not on setup I get random error messages about wanting a master password because my APIkeys are encrypted. 1) I have not encrypted them 2) Sometimes the same model is working and after restaing Bolt it is not ¯|(ツ)/¯

Christian Hofer about 2 months ago
Bug Reports
In QA
Error messages about API keys being encrypted
Tahoe 26.6 BoltAl 2 Version 2.14.0 (build 77) Not on setup I get random error messages about wanting a master password because my APIkeys are encrypted. 1) I have not encrypted them 2) Sometimes the same model is working and after restaing Bolt it is not ¯|(ツ)/¯

Christian Hofer about 2 months ago
Bug Reports
iOS App doesn't send image properly to llama-server
I share the same extract text from image prompt for gemma4 from macOS and iOS, but iOS never “gets” the file.

FossilizedCarlos about 2 months ago
Feature Requests
iOS App doesn't send image properly to llama-server
I share the same extract text from image prompt for gemma4 from macOS and iOS, but iOS never “gets” the file.

FossilizedCarlos about 2 months ago
Feature Requests
Allow Ollama provider to support Ollama Cloud directly
Currently I have added Ollama Cloud to BoltAI 2 as a custom OpenAI provider, howevr it would be nice (cosmetically) if the endpoint https://ollama.com could be added to the Ollama provider, along with an API key so that the Ollama icon is used.

paulgit about 2 months ago
Feature Requests
Allow Ollama provider to support Ollama Cloud directly
Currently I have added Ollama Cloud to BoltAI 2 as a custom OpenAI provider, howevr it would be nice (cosmetically) if the endpoint https://ollama.com could be added to the Ollama provider, along with an API key so that the Ollama icon is used.

paulgit about 2 months ago
Feature Requests
Add support for Cursor API
https://cursor.com/en-US/docs/cloud-agent/api/endpoints#create-an-agent describes how to access the Cursor via API-Key. Yet we’re not able to access their models, e.g. composer 2.5. Please add Cursor in the list of AI-Providers

Johannes H about 2 months ago
Feature Requests
Add support for Cursor API
https://cursor.com/en-US/docs/cloud-agent/api/endpoints#create-an-agent describes how to access the Cursor via API-Key. Yet we’re not able to access their models, e.g. composer 2.5. Please add Cursor in the list of AI-Providers

Johannes H about 2 months ago
Feature Requests
Unable to connect to my providers on MacOS Golden Gate
I installed MacOS Golden Gate and I am now unable to connect to Fireworks or Sakana Fugu. I get an invalid API key error message although the key is absolutely correct. MacOS Golden Gate (27 - Developer Beta) BoltAI 2.13.7 build 76 Not a SetApp User Fireworks or Sakana Fugu (Deep Infra works for some reason)

Matthew Hamilton about 2 months ago
Bug Reports
Unable to connect to my providers on MacOS Golden Gate
I installed MacOS Golden Gate and I am now unable to connect to Fireworks or Sakana Fugu. I get an invalid API key error message although the key is absolutely correct. MacOS Golden Gate (27 - Developer Beta) BoltAI 2.13.7 build 76 Not a SetApp User Fireworks or Sakana Fugu (Deep Infra works for some reason)

Matthew Hamilton about 2 months ago
Bug Reports
Local MCP server 𝐓𝐨𝐨𝐥-𝐂𝐚𝐥𝐥 𝐋𝐨𝐨𝐩 𝐁𝐮𝐠
The hanging behavior is a known technical issue in the integration between the local client application (the chat interface or terminal wrapper) and the LLM API. It is called a Tool-Call Loop Hang. Here is the step-by-step sequence that causes the freeze: AI Initiates Tool: The user requests a file modification or read. The AI generates a tool call (e.g., mcp_edit_file_6lpu9l) and stops generating text, as required by the API protocol. MCP Server Executes: The local MCP server successfully executes the file edit and returns the result (the diff or file contents) to the client application. The Integration Gap (The Hang): In a fully automated integration, the client application is supposed to immediately feed the tool's output back to the LLM to trigger the next text generation turn. However, in this specific client setup, the application fails to auto-trigger the next turn. It pauses and waits. The Wake-Up: Because the client is waiting for the AI, and the AI is waiting for the client to send the tool results, the interface hangs. When the user types any message (e.g., "are you stuck again?"), it forces the client application to package the entire conversation history—including the pending tool results—and send it to the LLM. This instantly wakes the AI up, resulting in the immediate "AI-OK" response. 𝐇𝐨𝐰 𝐭𝐨 𝐅𝐢𝐱 𝐨𝐫 𝐌𝐢𝐭𝐢𝐠𝐚𝐭𝐞 𝐭𝐡𝐞 𝐈𝐬𝐬𝐮𝐞 Client-Side Configuration (Permanent Fix): The developer of the client application or terminal wrapper must update the execution logic. The client must automatically post the tool output back to the LLM API endpoint to request the next completion turn without waiting for manual user input. User Workaround (Immediate Fix): Whenever a tool call completes (you will see the green tool response block in the interface) and the interface pauses for more than 3 seconds, type a single character (such as a period . or go) and press Enter. This forces the client to send the tool results to the LLM and resumes execution instantly. AI Mitigation (Combining Steps): The AI will minimize sequential tool calls where possible, combining reads or edits into single multi-file operations to reduce the number of turn transitions.

Nigel Protter about 2 months ago
Bug Reports
Local MCP server 𝐓𝐨𝐨𝐥-𝐂𝐚𝐥𝐥 𝐋𝐨𝐨𝐩 𝐁𝐮𝐠
The hanging behavior is a known technical issue in the integration between the local client application (the chat interface or terminal wrapper) and the LLM API. It is called a Tool-Call Loop Hang. Here is the step-by-step sequence that causes the freeze: AI Initiates Tool: The user requests a file modification or read. The AI generates a tool call (e.g., mcp_edit_file_6lpu9l) and stops generating text, as required by the API protocol. MCP Server Executes: The local MCP server successfully executes the file edit and returns the result (the diff or file contents) to the client application. The Integration Gap (The Hang): In a fully automated integration, the client application is supposed to immediately feed the tool's output back to the LLM to trigger the next text generation turn. However, in this specific client setup, the application fails to auto-trigger the next turn. It pauses and waits. The Wake-Up: Because the client is waiting for the AI, and the AI is waiting for the client to send the tool results, the interface hangs. When the user types any message (e.g., "are you stuck again?"), it forces the client application to package the entire conversation history—including the pending tool results—and send it to the LLM. This instantly wakes the AI up, resulting in the immediate "AI-OK" response. 𝐇𝐨𝐰 𝐭𝐨 𝐅𝐢𝐱 𝐨𝐫 𝐌𝐢𝐭𝐢𝐠𝐚𝐭𝐞 𝐭𝐡𝐞 𝐈𝐬𝐬𝐮𝐞 Client-Side Configuration (Permanent Fix): The developer of the client application or terminal wrapper must update the execution logic. The client must automatically post the tool output back to the LLM API endpoint to request the next completion turn without waiting for manual user input. User Workaround (Immediate Fix): Whenever a tool call completes (you will see the green tool response block in the interface) and the interface pauses for more than 3 seconds, type a single character (such as a period . or go) and press Enter. This forces the client to send the tool results to the LLM and resumes execution instantly. AI Mitigation (Combining Steps): The AI will minimize sequential tool calls where possible, combining reads or edits into single multi-file operations to reduce the number of turn transitions.

Nigel Protter about 2 months ago
Bug Reports
In Progress
Main window not visible on launch
I have reopen windows when logging in checked during shutdown. But most times, after a restart, the main window doesn’t show when I switch to the app via Cmd+Tab. I believe its the same behavior if I tap on the dock icon. While restarting the app works, it’s starting to get to me since I don’t quit it. Hopefully its a quick fix?

resting 2 months ago
Bug Reports
In Progress
Main window not visible on launch
I have reopen windows when logging in checked during shutdown. But most times, after a restart, the main window doesn’t show when I switch to the app via Cmd+Tab. I believe its the same behavior if I tap on the dock icon. While restarting the app works, it’s starting to get to me since I don’t quit it. Hopefully its a quick fix?

resting 2 months ago
Bug Reports
View Thoughts
I love to review the reasoning behind the output for any given post. I really like the way you have the reasoning/thoughts displayed while the model is processing, but upon completion, I see that the “View Thoughts” section is then constricted to a very small popup window. I’d love to be able to expand the “View Thoughts” section and read it in the main window along with the output. Maintaining the same formatting as it has while streaming would be really cool.

david.sheley 2 months ago
Feature Requests
View Thoughts
I love to review the reasoning behind the output for any given post. I really like the way you have the reasoning/thoughts displayed while the model is processing, but upon completion, I see that the “View Thoughts” section is then constricted to a very small popup window. I’d love to be able to expand the “View Thoughts” section and read it in the main window along with the output. Maintaining the same formatting as it has while streaming would be really cool.

david.sheley 2 months ago
Feature Requests