Help us make TypingMind better!

Tell us how we could make TypingMind more useful to you by upvoting an existing post or creating a new post below. Thank you!

[Важно] Feature Request: Critical document management & integration features (DOCX, Google Drive, enhanced Interactive Canvas for Premium users)

Dear TypingMind Team, Thank you for your prompt response regarding the platform’s current capabilities for working with documents. I appreciate your honesty in acknowledging that direct export to DOCX, integration with Google Drive, file downloads, and a separate document registry are not yet supported. However, I want to emphasize that the ability to work effectively with documents and integrate them was a key factor in my decision to purchase a Premium license for TypingMind. In particular, I was very drawn to a concept similar to “Artifacts” in Claude, where the AI doesn’t just generate text but also creates fully-fledged, interactive, editable documents. I saw enormous potential in this for professional use. I ran into a problem while trying to implement basic functionality that I assumed should be available for interactive plugins: Reliable downloading of HTML files: Even simple JavaScript logic for downloading a file (via Blob and ` ` with the `download ` attribute) and opening a new tab (`window.open()`) doesn’t work consistently in Interactive Canvas or gets blocked. This severely limits the ability to create interactive results. "Open in Google Docs" functionality: I tried to replicate the convenience of being able to transfer an AI-generated document to Google Docs with a single click for further editing. Currently, this is impossible without third-party tools or complex backend integration, which makes the process disjointed and inconvenient. My suggestions for improvement, which I ask you to consider as critical for Premium users and the platform’s development: Improving the JavaScript runtime in Interactive Canvas: Provide a reliable and documented way to programmatically download files (for example, via a dedicated API accessible to plugins). Allow controlled opening of new tabs/windows (e.g., for external links or services) without being blocked by the browser, possibly with user confirmation. Native or simplified integration with Google Docs/Drive: The ability to export AI-generated HTML directly to Google Docs/Drive (via the Google API) with user authorization. This will significantly increase the value of AI-generated documents. Consider supporting export to DOCX (at least via an integrated conversion service). Registry/document management functionality: Provide an API or tools for plugins to index and store generated documents (e.g., in a database, local storage, or integrated cloud storage), as well as to search for and reuse them. These features are not just “nice-to-have” extras, but fundamental capabilities that make TypingMind a truly powerful tool for productive work with AI-generated content, especially for those who actively work with documents. Having OpenRouter as a provider with a wide selection of models is a huge advantage, but without the appropriate tools to work with the results, that advantage loses some of its value. I am convinced that implementing these features will make TypingMind a much more competitive and attractive platform, justifying the investment in a Premium license. I hope for your understanding and that you will give my suggestions serious consideration. Best regards!

💡

Feature Request

4 days ago

Simplify Local LLM Integration with Automatic Discovery and Native Support

I’d like to suggest a feature that could make TypingMind even better for users who run local LLMs. While TypingMind already supports custom OpenAI-compatible endpoints, configuring local inference servers such as Ollama, LM Studio, LocalAI, vLLM, llama.cpp, and similar solutions still requires manual setup. It would be fantastic to have a dedicated Local Models section that makes connecting to local LLMs much easier and more user-friendly. Some ideas that could improve the experience include: Automatic detection of local inference servers running on localhost (especially Ollama and LM Studio). One-click connection to supported local backends. Built-in presets for Ollama, LM Studio, LocalAI, vLLM, llama.cpp server, and other OpenAI-compatible APIs. Automatic discovery and listing of available models instead of requiring users to manually enter model names. A connection test with clear diagnostics when a server isn’t reachable. An optional setup wizard to guide new users through the configuration process. A streamlined setup process would significantly improve the user experience while making TypingMind an even more compelling choice for anyone who wants to combine cloud models with locally hosted models. Thank you for taking the time to read this suggestion and for continuously improving such an excellent product. I hope you’ll consider adding these enhancements in a future release.

💡

Feature Request

about 1 month ago

Feature Request - Add OneProvider API Endpoint Support

Hello TypingMind Team, I would like to submit a feature request to add support for the OneProvider API endpoint in TypingMind Proxy. Current Issue When attempting to use OneProvider (https://api.oneprovider.dev/v1/messages ) as a custom model endpoint, TypingMind Proxy displays the following error: "Sorry, TypingMind Proxy does not support the endpoint 'https://api.oneprovider.dev/v1/messages' yet. Please contact support if you think we should add it." This prevents users from accessing Claude models through OneProvider, which is a viable alternative to the official Anthropic API. About OneProvider OneProvider is an Anthropic-compatible API gateway that provides access to Claude models with the following characteristics: •Website: https://oneprovider.dev •API Endpoint: https://api.oneprovider.dev/v1/messages •Supported Models: Claude Opus 4.8, Claude Sonnet 4.6, Claude Haiku 4.5 •API Compatibility: Fully compatible with Anthropic Messages API •Authentication: API key via HTTP header (x-api-key ) •Payment Method: Cryptocurrency-based (no credit card required) •Key Features: •No account signup required (key-based authentication) •Pay-as-you-go pricing •No prompt logging or training on user data •EU-based infrastructure (Frankfurt) Why This Matters Adding OneProvider support would provide TypingMind users with: 1.Alternative Payment Options: Users who prefer or can only use cryptocurrency payments now have a viable option 2.No Account Requirement: Users who don't want to create an Anthropic account can still access Claude models 3.Increased Flexibility: More provider options give users greater control over their AI infrastructure 4.Competitive Advantage: TypingMind would be one of the few frontends supporting multiple Claude API providers Technical Details OneProvider's endpoint is fully compatible with the Anthropic Messages API specification. The required headers are: Plain Text x-api-key: anthropic-version: 2023-06-01 content-type: application/json The request/response format is identical to the official Anthropic API, making integration straightforward. Reference Documentation •OneProvider Official Docs: https://oneprovider.dev/docs •OneProvider Status Page: https://oneprovider.dev/status •OneProvider API Overview: https://oneprovider.dev/docs#overview •Anthropic API Documentation: https://docs.anthropic.com/ Additional Context I currently use OpenRouter with TypingMind without issues, which shows that TypingMind's infrastructure can support multiple third-party API providers. Adding OneProvider would be a natural extension of this capability. Suggested Implementation Since OneProvider uses the Anthropic Messages API format, the implementation could potentially be as simple as adding the endpo

💡

Feature Request

about 2 months ago

Show Model Details in a Sortable Table

I'd like to see a table view on the provider model name screen that shows model details (release date, pricing, etc) with the ability to sort by any column. To see this information today, I have to select each model individually. To accommodate that view, I'd redo this block. It takes up way too much space currently: I'd suggest you move this cntent block into a 'Model Details' tab and put it next to the models | api keys | global settings navigation above the model list, and use this space for a sortable table. Or just shift it further over to the right. it's using up a lot of space currently. It's useful, but uses more space then necessary. writingmate.ai does a really good job at this; see screenshot below. This is what I’d like to see when I select a model provider; a table-based layout of all the models therein along w/ relevant information on each LLM the provider offers: I can sort by model, author, date dated, context, input and output, and i can enable/disable models directly from this screen. Since so many models are added each week, giving me the flexibility to sort > enable/disbable based on needs makes it faster, quicker and easier to choose a model based on credit usage. Sometimes I want the cheapest model, sometimes middle of the pack, sometimes high-tiered ones. but right now, I have to choose the provider, select the model, look in that right pane to see token cost, etc. Maybe this table view is where the 'more model details' shows up? add a 'view details' link next to the model name? If i select that, a modal slides in from the right with the model overview/parameters shown? This would streamline things greatly!

💡

Feature Request

about 2 months ago