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 about 5 hours ago

1

💻

Feature Requests

Is there any way to do that, whether on a local model or via API to other providers?

resting 5 days ago

1

💻

Feature Requests

Since a few weeks, I cannot export pdf: markdown works, but pdf prints title and pictures, but no text. Deleting App and fresh install didn’t helped. P lease fix this important feature for me, thanks.

boltai@eberle.pro 9 days ago

2

🐛

Bug Reports

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 16 days ago

2

🐛

Bug Reports

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 18 days ago

5

🐛

Bug Reports

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 22 days ago

4

🐛

Bug Reports

I share the same extract text from image prompt for gemma4 from macOS and iOS, but iOS never “gets” the file.

FossilizedCarlos 25 days ago

💻

Feature Requests

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 26 days ago

💻

Feature Requests

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 28 days ago

💻

Feature Requests

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 29 days ago

2

🐛

Bug Reports

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 1 month ago

1

🐛

Bug Reports

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 about 1 month ago

🐛

Bug Reports

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 about 1 month ago

💻

Feature Requests

I’d like a shortcut-triggered palette with type-ahead title search for opening one of my chats. Examples can be found in most IDEs/code editors, e.g. ⌘⇧O in Xcode.

tight.clown about 1 month ago

💻

Feature Requests

On initial app open, Bolt opens to an empty/new chat but this chat doesn’t follow the settings (model or tool) saved in Settings. The New Chat settings ARE applied if you tap the trailing new chat icon in the navigation bar and create a new chat. But this makes it sluggish to open Bolt and immediately start typing.

chris about 2 months ago

📱

BoltAI Mobile

Lots of more capable agents like coding agents have a compact conversation feature that takes the conversation above it and condenses it down to something that reduces context use. I’ve found that context overflow / poisoning can be a problem in long dialogues. I usually kind of do this manually, have it summarize and then make a new discussion, but a way to compact and then a feature to include the previous N up to and including the most recent compacting would be nice.

Adam Ierymenko about 2 months ago

1

💻

Feature Requests

Gemma4 is supposed to be able to read images. But I’m getting Bad request error. Tried in LM studio it is able to generate the markdown of the table with this model.

resting about 2 months ago

1

🐛

Bug Reports

I have tried to input my Kagi API key in Settings>Plugins>Kagi Search and it will not accept. I have the latest version and have tested on MacOS, both Paid and Setapp, and on the mobile Beta. The error says that Kagi Search API is in Beta but this is no longer true, it is now Public per Kagi support. Desktop screenshot: Mobile screenshot

Prof about 2 months ago

2

🐛

Bug Reports

Bug report: OS version: macOS 26.5, build 25F71 BoltAI app version: BoltAI 2.13.3, build 72 Setapp user: No. I’m using the standalone app installed at /Applications/BoltAI 2.app. AI provider & model: N/A. This is a window/Dock behavior issue and is not related to an AI provider or model. Steps to reproduce: Open BoltAI 2. Go to Settings > General. Enable “Hide Dock icon when last window closes”. Disable “Show menu bar” because I do not want the menu bar icon either. Close all BoltAI windows, including the Settings window. Do not quit the app. BoltAI continues running in the background, but its Dock icon remains visible. I also tried turning “Show menu bar” back on, toggling “Hide Dock icon when last window closes” off and on again, then restarting BoltAI. The Dock icon still remains visible. Expected behavior: After the last BoltAI window is closed, BoltAI should continue running in the background and the Dock icon should disappear. Actual behavior: BoltAI keeps running in the background, no BoltAI windows are open, but the Dock icon still stays visible. Additional diagnostics: The preference appears to be saved correctly: app.hideDockWhenNoWindows = true System Events reports no open BoltAI windows, but NSRunningApplication still reports BoltAI’s activationPolicy as regular, so macOS keeps showing it in the Dock. Error message: No error message.

Rui 2 months ago

1

🐛

Bug Reports