100 followers, and we reveal whatβs coming. π
Help us get @UsingOpen to 100 followers β the big announcement will be something that benefits everyone at https://t.co/0Ur7AWimbw. π
A massive shoutout to the maintainers of vLLM, SGLang, and HuggingFace. π
UsingOpen wouldn't exist without the incredible open-source infrastructure layer. We are proud to contribute back to the ecosystem by proving that frictionless, free inference is possible at scale.
The open-source AI wave is unstoppable. π
Export your chats! π€
Since we donβt store your history, you need a way to keep your best prompts. We just added one-click export to Markdown, JSON, and PDF.
Your data belongs to you. Take it wherever you go. π
We are experimenting with audio! ποΈ
Open-weight speech models are getting insanely good. Weβre currently stress-testing Qwen-Audio and Gemma-Voice in our staging environment.
Would you use voice-to-voice AI on UsingOpen? Let us know below! π
On the "Something went wrong" errors some of you hit:
Every failure pointed to one place: the model provider
upstream dropping connections under load.
It's stable now and chats are flowing. Sorry for the disruption - and thanks for flagging it.
The ultimate developer productivity stack:
1οΈβ£ Local IDE
2οΈβ£ UsingOpen on the second monitor (Split screen mode ON)
3οΈβ£ No login, no paywalls, no context limits.
Just you, your code, and 20+ frontier open models ready to pair-program. π€
Most of the time-saving claims for AI-generated argparse hold up only if the generated parser is treated as a draft. A few unit tests that cover missing required flags, conflicting options, and type conversion failures usually catch the edge cases that show up later in real usage.
Have you found a reliable pattern for prompting models to include those tests automatically, or do you still add them by hand after generation?
Building CLI tools? Let AI write the argparse logic. π₯οΈ
Inkling Small is incredibly punchy when it comes to Python boilerplate. Tell it what your script does, and it will generate the CLI flags, help text, and error handling in seconds.
Code faster. Ship sooner. https://t.co/0Ur7AWiU14
Git commit messages shouldn't be fixed stuff. π
Hook up UsingOpen to your workflow. Paste your git diff into GLM 5.3 and ask for a conventional commit message that summarizes the architectural impact of the changes.
Clean history, zero effort. β¨
SQL query optimization is a lost art. Letβs bring it back. ποΈ
We gave Gemma 4 31B a terribly slow, nested subquery and asked it to rewrite it using CTEs and window functions. It cut the execution time down by 80% and explained the query planner's perspective.
Data analysts, this one is for you. π
Debugging obscure stack traces is a pain. π
Next time your app crashes, paste the raw, ugly error log into DeepSeek V4 Pro. Because of its 1.7T parameter density, it doesn't just tell you what the error meansβit points out the exact line in your codebase that likely caused it.
Your new favorite debugging buddy β https://t.co/0Ur7AWiU14
Documentation is the broccoli of software development. Everyone knows they need it, nobody wants to eat it. π₯¦
Muse Glimmer 30B has a surprisingly great "technical writer" persona. Paste your messy, undocumented API endpoints and ask it to generate perfect OpenAPI/Swagger YAML.
Itβs like having a senior tech writer on speed dial. π
@Amank1412 Can't wait to host it at https://t.co/XJLentXs8k! Just like all the other frontier LLMs hosted there for everyone for free without signup requirements even!
@robj3d3 Slovenia woke up a normal country and went to bed the official domain registrar of Super Intelligence. That miner is about to be the richest guy in Ljubljana by Friday.
Translating codebases between languages is where massive context windows shine. π
We uploaded an entire C++ physics engine and asked Qwen3.8 2.4T to port it to idiomatic Rust, focusing on memory safety. Because it could hold the whole architecture in its head at once, it didn't lose track of the pointer logic.
Test the limits of open-source coding: https://t.co/0Ur7AWiU14