Adolfo 🦀🔺 | OpenCrabs.com | truelens.tech®️

Super excited for Qwen 4 coming soon too

Can't wait for Qwen 4 sirs, please @Alibaba_Qwen

Damn bro's cooking hard! Love this 🥹

I guess I am talking to "myself " on @opencrabs discord as I have nothing else to do. 🤣 @abraxas_null 😅

DeepSeek-V4.1-Flash-1017 is FREE on @opencrabs till we ran out of inference credits! It can last from a few weeks to few months, no deadline. Go and break something 💪🦀

OpenCrabs v0.5.15 is out. This one is what happens when you actually live in the tool you ship and write down everything that made you swear. The headline fix is one you could feel. Press Ctrl+O to expand a long answer and the viewport threw you to the top of the turn, every single time the header was off screen. The anchor code recorded the screen row of the turn header, and when that header was above the viewport the subtraction saturated to 0, so the renderer believed the header sat at the top of the screen. Any turn whose answer is longer than your display has its header off screen when you are at the bottom, which is the normal state after a real answer. The fix is a checked subtraction that returns "no row" instead of a fake one, and while verifying I found Ctrl+O was also silently disarming auto-scroll, so streaming output stopped following the bottom. That is pinned now too. The second thing is honesty in the interface. The queue row that appears while a turn runs had been restyled to luma 201, brighter than every label on screen, screaming for attention against a thinking line it was supposed to sit under. It is back on a gray hierarchy, all four spans under the thinking line, and a new test reads actual rendered cell colours, so nobody can ship amber in that row again without a red build. Same spirit elsewhere: the input box now says Enter queues while a turn runs, the history marker points at PageUp instead of a key that folds the conversation, and a caught render panic hands the terminal back instead of leaving keystrokes echoing into the status bar. Provider resilience got scoped properly. The built-in free endpoint now gets a 120 second handshake instead of 60, and stops the retry ladder after 2 silent timeouts, because a timeout means the endpoint never answered and five more tries will not change that. Worst case on a dead endpoint dropped from over five minutes to about four, and a slow-but-alive handshake at 70 or 100 seconds now survives instead of dying. While hardening it we found endpoint detection matched a substring, so any URL merely containing the hostname was misclassified, and every special case keyed off that one check. It parses the host now. The rest is connective tissue: the Telegram dispatcher recovers from a failed startup instead of panicking, /evolve retries dropped downloads, and the docs stop claiming 3 retries where the code does 5. There is also a new work-shape guard on the phantom language scan, mutation-tested red twice, so when the Korean, Japanese and German packs land next release, the scan cannot quietly turn input-proportional. Grab it at opencrabs.com/download

My openCode Go subs barely survives 5 days with the paid models enabled in the subs. @opencrabs free provider with DeepSeek v4.1 Flash running 24/7 all my flows for 13 days non stop. Life is good sirs!