Ahmet Köse

45 posts

Ahmet Köse banner
Ahmet Köse

Ahmet Köse

@kosecom2

Websites und Ads, für mehr Marken-Begeisterung und Umsatz. »Personal Brands und Unternehmen« https://t.co/TqKTg2ehc5

Berlin, Deutschland Katılım Mart 2014
10 Takip Edilen2 Takipçiler
Ahmet Köse
Ahmet Köse@kosecom2·
@steipete I've used Sol and Opus 5. Opus is never 3x better than Sol; that's like a funny joke. In the last 24 hours, I've made about 900 requests with Sol, and sometimes I complete whole projects in one go. That's not so easy with Opus 5. 🤷‍♂️
English
0
0
0
5
Ahmet Köse
Ahmet Köse@kosecom2·
@Teknium The same here, Anthropic says "wow." But the only thing Fable does is hardcode everything with APIs in the frontend and waste Money! I hear the same from many developers. I am more active on LinkedIn.
English
0
0
0
4
Teknium 🪽
Teknium 🪽@Teknium·
I switched back to fable too. Its worse than opus 4.6-8 too. It caused some gnarly issues in hermes agent and i wont be using it again. Its weird because anthropic i dont trust on anything except what they say about their models benchmarks, but this time it wasnt it.
Raoul Pal@RaoulGMI

I don't know what the hell they did with Opus 5 but it's an absolute shitshow of a model. It just endlessly makes mistakes, goes off down rabbit holes, doesn't finish tasks. Creates new tasks you never asked it for and just ends up in an endless loop. It's a mess. @AnthropicAI

English
138
58
1.7K
197.5K
ollama
ollama@ollama·
The demand for GLM-5.2 and other frontier-level open models has been surging on Ollama's cloud. We're adding capacity in anticipation for some very large models next week! To make sure Ollama's infrastructure stays fast we're temporarily pausing new subscriptions on Ollama's Max plan. Existing Max subscribers are not affected and Ollama's Pro plan is still available to subscribe to.
English
81
80
1.8K
216.5K
OSF
OSF@osf_rekt·
made the switch from openclaw to herpes today and after just a few hours of use it’s definitely way better
English
181
12
787
76.4K
Ahmet Köse
Ahmet Köse@kosecom2·
@analogalok I have a laptop with an RTX 5080 16VRAM and 32GB RAM. What should I use? 🤔
English
1
0
1
28
Alok
Alok@analogalok·
Updated Gemma 4 31B QAT (dense) + Multi Token Prediction + a 1.3GB Vision Encoder + 110,000 Context. Running locally at 60 t/s on a single NVIDIA RTX 4090. Here is the exact llama.cpp stack to make multimodal VRAM limits obsolete. Following up on the text only throughputs below, I compiled llama.cpp from source on Ubuntu 22 (CUDA 13) to see how much context we actually lose when loading the 1.3GB mmproj-F16.gguf alongside the main model and the MTP drafter. Fed it a 28k token prompt + 1 image. Here is the breakdown: # 1. The Pure Speed Run (Unquantized KV Cache) The 1.3GB vision projector immediately eats into our VRAM, dropping our max context ceiling from 36k down to 20k (23.93 GB VRAM). llama.cpp flags: ./build/bin/llama-server -m gemma-4-31B-it-qat-UD-Q4_K_XL.gguf --mmproj mmproj-F16.gguf --spec-type draft-mtp --spec-draft-model mtp-gemma-4-31B-it.gguf --spec-draft-n-max 4 --spec-draft-p-min 0.7 -c 20000 -ngl 99 -fa on --port 8080 -v Prefill: 1731.20 t/s | Decode: 78 t/s (Still ridiculously fast, but a 20k context limit is tight for heavy document + image analysis). # 2. The Mid Ground (Q8 KV Quantization) Squeezed the cache to 8-bit. Context ceiling jumps to 58k (23.96 GB VRAM). llama.cpp flags: ./build/bin/llama-server -m gemma-4-31B-it-qat-UD-Q4_K_XL.gguf --mmproj mmproj-F16.gguf --spec-type draft-mtp --spec-draft-model mtp-gemma-4-31B-it.gguf --spec-draft-n-max 4 --spec-draft-p-min 0.7 -c 58000 -ngl 99 -fa on --cache-type-k q8_0 --cache-type-v q8_0 --port 8080 -v Prefill: 2020.85 t/s | Decode: 64 t/s # 3. The Multimodal Tradeoff (Q4 KV Quant) Dropped to 4-bit cache to push the absolute limits (23.97 GB VRAM - literally megabytes to spare). llama.cpp command: ./build/bin/llama-server -m gemma-4-31B-it-qat-UD-Q4_K_XL.gguf --mmproj mmproj-F16.gguf --spec-type draft-mtp --spec-draft-model mtp-gemma-4-31B-it.gguf --spec-draft-n-max 4 --spec-draft-p-min 0.7 -c 110000 -ngl 99 -fa on --cache-type-k q4_0 --cache-type-v q4_0 --port 8080 -v Prefill: 2033.11 t/s | Decode: 60 t/s By using the --mmproj flag to load the F16 vision encoder, we permanently lose about 1.3GB of our 24GB budget. Text only Q4 (from previous post): 140k context @ 65 t/s Multimodal Q4 (this test): 110k context @ 60 t/s We sacrificed 30,000 tokens of context to give a 31B model flawless image recognition. The fact that you can feed an image and a 100k+ codebase into a single RTX 4090 and get 60 t/s back is a paradigm shift for local multimodal agents. Hugging Face links to the updated Unsloth's QAT quants with vision projectors, and performance graph are in the replies below. If you haven't been following my previous posts, google recently patched the chat templates of gemma 4 family of models to improve tool calling. The agentic reasoning gains on the benchmark charts are massive: - TB2 (Agents): +4.5% (to 25.8%) - Tau2 (Telecom): +10.1% (to 62.7%) What are you building with local vision models right now? which models are you running on your single rtx 3090, 4090 or other 24 GB VRAM nodes?
Alok@analogalok

MTP (Multi Token Prediction) with 4 bit KV Cache quantization is the ultimate local AI cheat code. Ran the updated Gemma 4 31B QAT (dense) at 65 tokens/second at 140k context on one a single RTX 4090 (24 GB VRAM). Following up on the baseline numbers in my previous post, I pulled the latest llama.cpp source code on Ubuntu 22 (CUDA 13) to test Gemma 4 31B QAT (dense) Fed it the same 28k token prompt. The throughput scaling is violent. Here are the exact commands and benchmarks: # 1. The Pure Speed Run (Unquantized KV) Maxed out the 24GB VRAM ceiling at a 36k context limit. llama.cpp flags: ./build/bin/llama-server -m gemma-4-31B-it-qat-UD-Q4_K_XL.gguf --spec-type draft-mtp --spec-draft-model mtp-gemma-4-31B-it.gguf --spec-draft-n-max 4 --spec-draft-p-min 0.7 -c 36000 -ngl 99 -fa on --port 8080 -v Prefill: 2093.45 t/s | Decode: 81.22 t/s (A massive 2.5x lossless speedup from the 32 t/s baseline without MTP) # 2. The Mid Ground (Q8 KV Quantization) Squeezed the cache to 8-bit to double the context to 80k (23.94GB VRAM). llama.cpp flags: ./build/bin/llama-server -m gemma-4-31B-it-qat-UD-Q4_K_XL.gguf --spec-type draft-mtp --spec-draft-model mtp-gemma-4-31B-it.gguf --spec-draft-n-max 4 --spec-draft-p-min 0.7 -c 80000 -fa on --port 8080 -ngl 99 --cache-type-k q8_0 --cache-type-v q8_0 -v Prefill: 2050.04 t/s | Decode: 65.09 t/s (decode was 33 t/s without MTP. 2x lossless jump) # 3. The "God Tier" Tradeoff (Q4 KV Quantization) Dropped to 4-bit cache to push an insane 140,000 context (23.85GB VRAM). llama.cpp flags: ./build/bin/llama-server -m gemma-4-31B-it-qat-UD-Q4_K_XL.gguf --spec-type draft-mtp --spec-draft-model mtp-gemma-4-31B-it.gguf --spec-draft-n-max 4 --spec-draft-p-min 0.7 -c 140000 -fa on --port 8080 -ngl 99 --cache-type-k q4_0 --cache-type-v q4_0 -v Prefill: 2150.43 t/s | Decode: 65.85 t/s (decode was 33 t/s without MTP. 2x lossless jump) The Architecture Insight: Notice how quantizing the KV cache drops MTP decode speed from 81 t/s down to 66 t/s? Standard generation is bottlenecked by memory bandwidth, every token requires restreaming the full 18GB of weights off VRAM, and the GPU's compute cores mostly sit idle waiting on that transfer. MTP doesn't remove that bandwidth cost, but it amortizes it. by verifying multiple drafted tokens in a single forward pass, you get several tokens of output per weight load instead of one, which is why the effective throughput jumps so much. That's also why quantizing the cache eats into the gain. The q8_0/q4_0 cache has to be unpacked back into usable values on every attention step before the GPU can run the actual attention math on it. an extra compute step that plain f16 cache doesn't need. Flash Attention's fastest kernels are built around f16 memory, so feeding it a quantized cache adds real compute latency per step, which lines up with what I measured: decode speed barely moved between Q8 and Q4 (65.09 vs 65.85 t/s) even though Q4 moves half the bytes Q8 does. You are effectively trading ~15 tokens/second of throughput to unlock over 100,000 extra tokens of context on consumer hardware. If you’re on a single 3090 or 4090 and benched this model earlier, the new update is your sign to run it again. Hugging Face links to the Unsloth QAT quants and performance graph are in the replies below.

English
19
27
272
88.8K
foo
foo@getroot_sh·
@Teknium No, just no. 1, it modifies your SOUL.md and config.yaml. 2, it replaces Discord hooks. 3, it replaces shell_exec and write_file. 4, you cannot delete your account. Stay away.
foo tweet media
English
3
0
10
965
Ahmet Köse
Ahmet Köse@kosecom2·
@Alibaba_Qwen But the coding plan is dying; only old models remain. 🤷‍♂️
Ahmet Köse tweet media
English
0
0
0
13
Ahmet Köse
Ahmet Köse@kosecom2·
@ollama Kimi K3? I waiting with the Max-Plan! 😂
English
0
0
0
15
ollama
ollama@ollama·
Ollama 0.32.1 includes significant improvements to Gemma 4's tool calling, making it much more reliable in coding agents! To try Gemma 4 26B with Pi, run: ollama launch pi --model gemma4:26b With Ollama's MLX engine for maximum performance, run: ollama launch pi --model gemma4:26b-mlx
Google Gemma@googlegemma

We’re rolling out some big improvements to Gemma 4, fueled by incredible community feedback and contributions! Here is a breakdown of what’s being fixed and updated in this release: 🧵👇

English
47
99
848
98.1K
Zane Chen
Zane Chen@chenzeling4·
744B parameters. On a laptop. With 25GB RAM. Colibri runs GLM-5.2 (744B MoE) in pure C with zero dependencies. The trick: only ~40B params activate per token, so it keeps the dense part resident and streams experts from disk on demand. A single 2,400-line C file. No GPU, no BLAS, no Python at runtime. This shouldn't work. But it does. ⭐ 2.1K #AI #OpenSource github.com/JustVugg/colib… Follow for daily dev finds 🔔
Zane Chen tweet media
English
192
492
4.1K
462.4K
Ahmet Köse
Ahmet Köse@kosecom2·
@Teknium Hey, I've resolved all the multiplexing issues, and you can now run multiple agents through one gateway without any problems. Can I just show you the patch?
English
0
0
0
2
Teknium 🪽
Teknium 🪽@Teknium·
We just released Hermes Agent! In my humble opinion a very good blend between coding agents like Claude Code and generalist agents like Clawdbot. Been working on this for the last month or so now - started as a way for us to have agentic primitives for datagen and RL and got inspired by the agentic revolution of late, so been expanding it's scope and capabilities non-stop! Hope you all enjoy.
Nous Research@NousResearch

Meet Hermes Agent, the open source agent that grows with you. Hermes Agent remembers what it learns and gets more capable over time, with a multi-level memory system and persistent dedicated machine access.

English
178
124
2K
702K
tonbi
tonbi@tonbistudio·
Want to get into Hermes Agent but don't know where to start? Perhaps you're not ready to invest multiple hours of listening to my voice (unthinkable!), so I made a quick 10 minute video to get you up and running and learn some key concepts. Check it out! youtu.be/BeWUUclCin0
YouTube video
YouTube
English
15
26
248
60.4K
Ahmet Köse
Ahmet Köse@kosecom2·
@NousResearch Yes, but I patched it already. Now every agent knows what the others have on their own channel. Before, the agents pressed the message right, but answers came only from the main channel. It was a multiplexing issue; also, the MCP problems with multiplexing were fixed.
English
0
0
0
4
Nous Research
Nous Research@NousResearch·
Hermes Agent v0.17.0 - The Reach Release Changelog below:
English
198
245
3K
1.3M
Teknium 🪽
Teknium 🪽@Teknium·
We have just merged an expanded form of the memory management tool Hermes Agent uses to save/edit/remove memories so that it can do batch operations, saving many turns of tool calls in most scenarios! Run `hermes update` in your CLI or update in your GUI to start saving now.
Teknium 🪽 tweet media
English
67
93
1.1K
104.6K
Luke The Dev
Luke The Dev@iamlukethedev·
Last night my Hermes agent burned through $681 in API credits. 😭 Before anyone blames Hermes: This was 100% my fault. Bad timeout settings. Bad fallback configuration. No spending alerts. The agent did exactly what I told it to do. Just for way longer than I intended. 💸 Hopefully my $681 mistake saves someone else $681.
Luke The Dev tweet mediaLuke The Dev tweet media
English
48
3
103
16.6K