Former OpenAI CTO Mira Murati Launches Thinking Machines' Inkling: Open-Weights Multimodal AI Model with 975 Billion Parameters and Self-Training Demo
Releasing yet another powerful language model is no longer enough to stand out. Thinking Machines, the startup founded by former OpenAI technical director Mira Murati, has chosen a different approach to attract developers. The company unveiled Inkling, its first open-weights model that can be freely used and adapted for specific tasks.
Inkling is a multimodal model capable of processing text, images, and audio without separate processing modules for each modality. It is built on a mixture-of-experts architecture containing 975 billion parameters, of which only 41 billion are active at any given time. This design significantly reduces computational costs. The model supports a maximum context length of 1 million tokens and was trained on a dataset of 45 trillion tokens that included text, images, audio, and video. Alongside the main model, the company released a preliminary Inkling Small version with 12 billion active parameters optimized for lower-cost and faster deployment.
One of Inkling’s standout features is the ability to regulate reasoning depth. Developers can choose how many computational resources the model should allocate to solving a problem. For simple queries the system responds faster and consumes fewer tokens, while for complex tasks it can increase internal computation. According to the company, in certain programming scenarios Inkling uses approximately three times fewer tokens than several other open models while maintaining comparable quality.
Thinking Machines acknowledges that Inkling does not yet aim to be the strongest model on the market. Closed models from OpenAI, Anthropic, and Google continue to lead most comprehensive benchmarks, while Chinese models remain ahead in certain disciplines. Instead of competing for top rankings, the company focused on creating a versatile foundation for subsequent training and customization for enterprise use cases.
To support further development, Thinking Machines offers its own Tinker platform. Through this platform, developers can fine-tune Inkling on their own data without building complex infrastructure themselves. To demonstrate the platform’s capabilities, the company conducted an unusual experiment: Inkling was tasked with training itself. The model autonomously created a training task, executed the process via Tinker, evaluated the results, and switched to the updated version. In the demonstration, it was given the unusual objective of learning to answer questions while completely avoiding the use of one letter of the English alphabet.
The company has also made the model weights available on Hugging Face and added support for popular inference frameworks including Transformers, vLLM, SGLang, and llama.cpp. Inkling is designed not only for cloud services but also for continued training, creation of specialized assistants, and development of autonomous agents capable of executing complex sequences of actions.
The release of Inkling represents an important development for the Western open-weights AI community. After Meta reduced its activity in this area and many organizations began turning to Chinese models, developers now have another major Western-origin solution that can be freely run, modified, and adapted to their own tasks thanks to its open weights.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.