Performance
Tune rendering limits, virtualization, and extension loading to keep AgentOne fast.
The Performance section in Settings gives you controls for managing AgentOne's behavior when working with large chats or many extensions. Most users will never need to change these defaults, but they are useful when you notice slow rendering or high memory use.
Rendering Limits
AgentOne switches to a more performance-friendly rendering mode for content that exceeds these limits. Reducing the limits makes the app faster in long conversations with large outputs; increasing them lets you see more content before truncation.
Max Message Length
The maximum number of characters AgentOne renders in a single message before applying truncation or lazy loading. Very long assistant responses (for example, generated code files) can cause layout slowdowns without this limit.
Max Codeblock Characters
The maximum number of characters rendered inside a single code block. Large code outputs in long chats are the most common cause of sluggishness, and this setting is the most impactful for rendering performance.
Max Tool Result Characters
The maximum number of characters rendered in a tool result (the output of an extension tool call). Tool calls that return large data - for example, a file view or a web page fetch - can produce very long outputs. Reducing this limit keeps those inline without affecting the model's actual context.
Chat Virtualization
Virtualize Chat Messages
AgentOne can render only the messages around the visible viewport instead of keeping every message mounted. This dramatically reduces memory use and improves scroll performance in long chats.
The default mode enables virtualization after a message-count threshold. You can change the mode if you prefer to always or never virtualize chats.
Message Count Threshold
The number of messages a chat must have before virtualization activates in threshold mode. The default is 20, so shorter chats render normally while longer chats switch automatically.
Extension Runtime
MCP Parallel Load Limit
Controls how many MCP servers AgentOne starts simultaneously at launch. If you have many extensions installed, a higher limit means faster overall startup but more CPU and memory usage during the load phase. A lower limit staggers the startup at the cost of some extensions taking longer to become available.
The default is a moderate value suitable for most setups with a handful of extensions. Raise it if you have many extensions and your hardware can handle the burst; lower it if you notice high CPU spikes when the app opens.
Related
- Extensions - manage installed MCP servers.
- Chat Settings - streaming throttle and other chat behavior tuning.