Twitxy Saved

Alex

Verified account This account is verified. Learn more

@Alex_tra_memory

Joined July 2025
333 Following 1.2K Followers 464 Posts

Latest posts 5

Alex Verified account @Alex_tra_memory
I've 12 PRs merged into oh-my-pi, an open-source terminal coding agent with 39K⭐ putting me @ top ~5% committers.

i learned alot about 🤖 multi-agent orchestration, 🔌 Agent ↔ editor ↔ tool protocols, 🧠 Model routing across providers & ⚙️ Agent runtime performance.

1. LSP reload left a stale language server running: github.com/can1357/oh-my-…
2. Browser tool lost non-Error page rejections: github.com/can1357/oh-my-…
3. omp stats re-parsed every session on ZFS: github.com/can1357/oh-my-…
4. worktree add failed on read-only files: github.com/can1357/oh-my-…
5. SVG text vanished with a missing font: github.com/can1357/oh-my-…
6. History search matched a/b wrongly: github.com/can1357/oh-my-…
7. ACP under-reported subagent cost: github.com/can1357/oh-my-…
8. Isolated tasks reverted the baseline commit: github.com/can1357/oh-my-…
9. One ambiguous model ID hid a provider: github.com/can1357/oh-my-…
10. Shell visualization ~1 GB per card: github.com/can1357/oh-my-…
11. ACP ignored the MCP startup timeout: github.com/can1357/oh-my-…
12. Mistral effort options fixed: github.com/can1357/oh-my-…

github.com/can1357/oh-my-…
github.com fix(lsp): stop a superseded shared server on reload by Alex-Wengg · Pull Request #18254 · can1357... What lsp reload now stops the old language server when a config change replaces a client that runs through the shared LSP mux. Before, shutdown/exit only detached the mux link. The mux kept the ser...
Alex Verified account @Alex_tra_memory
i finally got 10 PRs merged into @vllm_project 🎉

by commit count on vLLM's main, i am ranked #307–#335 of 3,756 contributors, top 8.9% (306 people have more commits, 29 of us are tied at 10)

what shipped:

🎙️ NVIDIA Canary: speech recognition + translation to and from English in 25 European languages, token-identical to the reference implementation
github.com/vllm-project/v…
github.com/vllm-project/v…

🔌 Parakeet TDT + Nemotron-3-Diarization: both run in vLLM through plugins i built, now listed in its supported models
github.com/vllm-project/v…
github.com/vllm-project/v…

🖼️ Gemma 4: image normalization moved from the CPU to the GPU, including the Gemma 4 Unified 12B models
github.com/vllm-project/v…
github.com/vllm-project/v…

🧭 CLIP, SigLIP & SigLIP2: chat-style requests now return the same embeddings as plain input. also opened the matching fix on the @huggingface Hub
github.com/vllm-project/v…
github.com/vllm-project/v…
huggingface.co/google/siglip2…

🛠️ + fixes: answers no longer get mislabeled as reasoning, and main's pre-commit check is green again
github.com/vllm-project/v…
github.com/vllm-project/v…

video walking through each the commits 👇
0:44
Alex Verified account @Alex_tra_memory
some new system design stuff i learned today.

- write heavy is often due to many clients writing to a central server
- to offload server load . we partition the database , this makes it difficult to do a global query for a lighten write load per server.
- read heavy is often servers having to send many requests to different clients
- read vs write heavy doesn't mean one can do one and not the other . write heavy can do a few query search like one individual row or multiple local rows.
- Discord is write heavy but , it's alot of local data reading. So it's not like you need to search across various Discord servers. You just need to update the nearby data
- blob data is best in cloud file / S3 . its just a simple store once and forget. unlike a ready system where its often vast amount of data fed back to the users.
- generally speaking, when it comes to blobs & write heavies, people aren't searching a massive file. It's just a simple few.
Alex Verified account @Alex_tra_memory
trying to watch youtube videos about how transformer and these models won't don't click for me at all\. i have to spend hours just talking to claude voice mode to get them to really click . frankly even then i still feel like i don't know shit.

Agent harness
- tool: a function used by the model to write JSON requests. with usually Ask vs Act modes .
- Context management: often times the harnse just manages large files stored somewhere and not feed it to the model to prevent traffic lag. using RAG systems to find the needed info
- reasoning tokens: decoder outputs between think tags. trained to do analysis mode before answering user requests.

inference-engine:
- scheduler and kv cach managers are the key relationship questions . kv cach manager holds the blocktable, evictor and prefix tree
- Prefill vs decode . batching each token requests to prevent traffic spiking
- slow or garbage outputs.

as mentioned theres still alot i need to learn about each concept and each can into deep layers about them .