
looking at data™️ and evals @ProximalHQ https://xitter.cf/t.co/lkrTmrz01F prev studied CS and Linguistics @iiit_hyderabad
Bengaluru, IN
Joined February 2018
- Tweets5.9K
- Following1.4K
- Followers416
- Likes38.5K
Looking at the data™️ was/is the most interesting part about FrontierSWE v2. We're still looking at them and keep finding exciting bits to talk about. Have talked about a few in the blog, and have released all traces, hope this leads to more ppl looking at data™️
readme: fix typo
Co-Authored-By: GNU nano 9.0 (UTF-8, EDITOR and VISUAL, guidestripe=72)
Co-Authored-By: Ghostty 1.3.1 (Metal renderer)
Co-Authored-By: zsh 5.9 (arm64-apple-darwin26.0)
Co-Authored-By: Git 2.56.0 (Homebrew)
Co-Authored-By: Secretive (SSH_AUTH_SOCK)
Co-Authored-By: macOS Text Input (U.S. layout)
Co-Authored-By: Apple Internal Keyboard (built-in)
Co-Authored-By: APFS (sealed system volume, 4096-byte blocks)
Co-Authored-By: MacBook Pro (Mac17,6, MGED4B/A, Apple M5 Max, 18 CPU cores, 36 GB RAM, macOS 27.0.1 build 26A434)
Akshit retweeted
planning is overrated
just take the shortest term action that is in the general direction of your goal
reality is a super high dimensional space, so this basically always works
Akshit retweeted
1/ We discovered something totally unexpected about the neural structure of consciousness that overturns decades of thinking on its biological basis and brings us significantly closer to the recipe for generating conscious awareness.
New preprint: biorxiv.org/content/10.64898… (led by @HesseJanis, with @FrankLanfranchi, @_conor_mcgrory, @Yuelin_Shi, and @EngelTatiana)
Akshit retweeted
My dear friends, I’d like to show you my latest toy project
Introducing Handwired: turn your regular JavaScript code into a neural net!
- no training
- exact outputs vs the JS program
- fully differentiable
All runnable in a browser, without GPU
Our new blog talks about some exciting approaches models took to train racing bots. Agents are getting more creative than I anticipated, couldn’t stop refreshing trajectory pages as we saw them build these out live. As always, there’s so much more lying out there in the traces.
Akshit retweeted
In September, we published the TORCS Racing Bot task as part of FrontierSWE
Agents get 20h to build a bot that drives in a racing simulator as fast as possible, using only visual inputs. We are sharing a more detailed analysis and interesting findings from models' attempts
Akshit retweeted
An new Pleias paper: in collaboration with AI Bridges and @Wikimedia Deutschland we developed a new harness for complex semantic search over the largest knowledge database, @wikidata
Akshit retweeted
16. AI Native gateway that filters your slop on twitter - this itself reduces TTFBT (time to first brain tumor) by 98%
As an AI Infrastructure Engineer, you must build these projects.
1.) High-Throughput Serving Engine Tuning
Build: Deploy vLLM or SGLang, tuning chunked prefill, continuous batching and max-num-seqs for a specific GPU architecture.
Why: Default configs waste 60% of VRAM. Squeezing the hardware is the baseline job.
2.) KV-Cache Prefix Routing Proxy
Build: A load balancer that hashes incoming system prompts and routes requests to the specific replica holding that KV-cache block in memory.
Why: Reused context is free speed. This alone can slash Time-To-First-Token (TTFT) by 80%.
3.) Custom Fused Triton Kernel
Build: Write a fused RMSNorm or RoPE (Rotary Position Embedding) kernel in Triton and benchmark it against the native PyTorch implementation.
Why: Python overhead and memory reads kill inference. Fused kernels save milliseconds that compound at scale.
4.) Speculative Decoding Pipeline
Build: A serving setup where a local 2B "draft" model generates tokens in parallel and a 70B "target" model verifies them in a single forward pass.
Why: 2x decode speed at zero quality loss is the closest thing to a free lunch in inference.
5.) Disaggregated Prefill/Decode Cluster
Build: Separate GPU pools where compute-heavy prefills and memory-bound decodes are routed to different hardware optimized for each phase.
Why: This is the exact architecture frontier labs use to maximize MFU (Model Flops Utilization) in 2026.
6.) FP8 Quantization & Calibration Harness
Build: A pipeline that calibrates a model for FP8 inference, serves it via TensorRT-LLM and measures the exact perplexity drop against throughput gains.
Why: Quantization is the only way to fit frontier models on edge GPUs and protect your cloud margins.
7.) Queue-Based GPU Autoscaler (KEDA)
Build: An autoscaler that spins up spot GPU nodes based on pending token queue depth and gracefully drains them when the queue empties.
Why: Idle H100s burn $3+/hr. FinOps and scheduling are now core infra responsibilities.
8.) Complexity-Routing AI Gateway
Build: A proxy that analyzes prompt entropy and token length to instantly route simple queries to a quantized local 8B model and complex reasoning to a frontier API.
Why: Unit economics decide if your AI product survives the next API price hike.
9.) Multi-Node Tensor Parallelism Setup
Build: Shard a 70B+ parameter model across 4 nodes using NCCL over RDMA/RoCE v2 and profile the exact network bottleneck between GPUs.
Why: Single-node inference is dead for frontier models. You must master the interconnect.
10.) Semantic Cache Layer
Build: A Redis + Vector DB proxy that intercepts requests, checks for >98% embedding similarity, and returns cached outputs without hitting the GPU.
Why: The cheapest and fastest token is the one you never generate.
11.) DCGM Observability & Throttling Dashboard
Build: A Grafana stack tracking GPU temp, SM occupancy, VRAM OOMs and PCIe TX/RX to catch silent hardware throttling.
Why: You cannot fix an SLO violation if your dashboard only shows HTTP 200s while the GPU is melting.
12.) MoE (Mixture of Experts) Load Profiler
Build: An expert-parallel deployment tracking token-to-expert routing to identify and fix expert load imbalance and communication overhead.
Why: Sparse MoE models are the 2026 standard, and naive routing destroys their latency advantage.
13.) Inference Chaos & Fault Tolerance Suite
Build: A harness that injects network partitions, simulated GPU ECC errors, and OOMs to test the cluster's ability to migrate KV-caches and recover.
Why: At scale, hardware fails daily. Your architecture must heal itself.
14.) Checkpointing & Weight Streaming Engine
Build: A system that streams model weights directly from an S3 bucket to GPU VRAM on cold-start, bypassing local disk bottlenecks.
Why: Cold-start latency kills autoscaling. Streaming weights directly to memory is the ultimate optimization.
15.) Public Inference Benchmark Teardown
Build: 3 published deep-dives with Pareto curves (Cost vs TTFT vs Throughput) comparing vLLM vs SGLang vs TensorRT-LLM on your specific hardware.
Why: Public proof of hardware mastery and methodology gets you hired instantly by top AI labs.
Systems that prove you can serve, optimize & scale when silicon meets intelligence.
Bookmark & Repost.
Akshit retweeted
have some lore to share:
the first vibecoding company was not cursor or cognition or anthropic -- it was Season 6 of Silicon Valley
> be me, techbro founder hired as a consultant to the show
Akshit retweeted
At Proximal, we believe that building our own research infrastructure is crucial to design the highest-quality training data
Today, we are sharing more information about our internal post-training stack
Akshit retweeted
💥 New paper: we measure time awareness in LLM agents, which covers duration following, forecasting, and retrospection.
It's striking how much better Astra is at duration following than any other model (see Figure 1 below)! We think it's likely connected to training on strictly time-bounded tasks, including the ones behind the recent agentic incidents (see collusion.wiki/). The much higher time awareness of Astra is likely an instrumental skill learned almost by accident (?) through task time constraints.
Interestingly, the same doesn't apply to Anthropic models. Fable 5.1, for example, doesn't reliably follow any given duration! If you ask it to work for 4h, it will finish working before 1h in most cases!
I think time awareness has been an overlooked capability for a long time. But it really matters for so many tasks, especially for long-running agents!
(Joint work with my MATS mentee @MOfengenden!)
Akshit retweeted
On this note, @ProximalHQ is doing $55M in “month revenue”.
Getting preempted now.
Fastest company ever to $1b annualized revenue
Nope it’s not Higgsfield or Cursor or Cognition.
Met a data company yesterday that did 0 revenue in November 2025 and 80m “in month revenue” in September 2026. They will hit $1b annualized from 11 months of being started. They are still under the radar so I can’t share who they are. Hopefully soon, with their permission.
I don’t make the rules.
Akshit retweeted
We have added Claude Haiku 5.5 and Sonnet 5.5 to the FrontierSWE leaderboard.
Both models are extremely capable despite being smaller than Anthropic's flagship models Opus and Fable - Haiku outperforms GPT-5.6 Sol, GLM-5.3 and other strong models!
Akshit retweeted
THE missing post-training primitive people should be chasing right now is a way to convert written human feedback directly to training signal.
When we shifted to reasoning models and RL, we lost the ability to just refine an input / output pair to a level of quality and then throw it into a training mix.
RL env creation is the go-to way today of converting human expertise to training signal, but it's incredibly roundabout and a lot of things have to go right for it to work. The model has to basically luck into the behaviors you want to see.




























