Sajjad Pakdamansavoji's picture
šŸ‘‹ Open to Work

Sajjad Pakdamansavoji

savoji
3

AI & ML interests

VLM, VLA, LLM, Robotics, Computer Vision

Recent Activity

posted an update about 3 hours ago
SO-Arena scored 21 System One models, and the most accurate one ranks only seventh on reliability. System One models pick from fixed options in one forward pass, so teams use them for routing, tool choice and verification. A leaderboard score does not say whether the pick survives shuffled options or a missing right answer. SO-Arena (2,919 tasks, 11 domains) measures that separately. šŸ” What's new • Reliability R = sqrt(S*N). S is stability over 12 option reorderings. N = 2AUC-1 on spotting that the correct option was removed • JevAny-27B is the most reliable System One model yet ranks eleventh in capability • 14 of 18 models reach S above 0.8, but N runs from near chance to about 0.8 šŸ“Š The numbers • GPT-6 Sol (82.3) and Luna (79.7) lead. The best System One models, GLiDE and KnowLine-31B, score 70.2 • Open-weight System One models answer within 0.3 s per task on one H100 • Knowledge, sentiment, retrieval: comparable to Luna, with little gain from a bigger backbone or thinking • Math: thinking lifts StartLux Auto from 50.8 to 92.5. In intent, safety, tools and web, the larger backbone helps far more āš ļø Caveats • The backbone gain mixes size with Qwen3.5 vs Qwen3.8. Thinking is tested on one model • Two closed System Two references only, and no independent replication yet Before adopting a model, check per-domain scores, then reorder options and drop the correct one on your own task. The MIT repo ships the scoring and reliability tooling. https://huggingface.co/papers/2611.15777 https://github.com/holdrain/SO-Arena Do you test decision models for order sensitivity before putting them in an agent? šŸ“š Read it elsewhere • The deep dive on Medium: https://medium.com/p/e923d2f58e85 • The long read on Substack: https://sajjadpakdamansavoji.substack.com/p/so-arena-finds-the-most-accurate • The thread on X: https://x.com/saavoji/status/2121665100981444943 • Every version on sajjadpsavoji.github.io: https://sajjadpsavoji.github.io/blog#so-arena-finds
posted an update 1 day ago
Chrome's modern-web-guidance repo gained 1,875 GitHub stars in one day (4,476 total, 252 forks, Apache-2.0), and it was only created on 2026-01-27. Its bet: an agent's stale web habits are a delivery problem, not a training problem. The README says agents default to older patterns "because LLM training data contains vast amounts of legacy code." So instead of retraining, a skill's CLI returns curated guides into the agent's context window when a task needs them. šŸ” What's in it • 250 web features: 140 CSS and layout, 74 JavaScript and APIs, 36 HTML and DOM • Each guide has a retrievable ID, such as animate-to-from-top-layer • Evals prune what models already know, to save tokens • Stewarded by the Chrome, Edge, Firefox and MDN teams šŸ› ļø Try it, no install ``` npx modern-web-guidance@latest search "animate a dialog modal backdrop" npx modern-web-guidance@latest retrieve "animate-to-from-top-layer" npx modern-web-guidance@latest legacy-scan . ``` āš ļø Caveats • No benchmark numbers in the README; it links an Eval Dashboard, but the gain is unquantified • Stars show interest, not adoption or quality • Guides cost context tokens and rely on the agent calling the skill at the right moment • Web platform only; this is the authoring repo, the shipped guides live in GoogleChrome/modern-web-guidance https://github.com/GoogleChrome/modern-web-guidance-src https://goo.gle/modern-web-guidance If you run legacy-scan on your own codebase, would you trust runtime guidance over a model upgrade to keep your agent current? šŸ“š Read it elsewhere • The deep dive on Medium: https://medium.com/p/fa2703c6324b • The long read on Substack: https://sajjadpakdamansavoji.substack.com/p/chromes-modern-web-guidance-treats • The thread on X: https://x.com/saavoji/status/2121292924419985453 • Every version on sajjadpsavoji.github.io: https://sajjadpsavoji.github.io/blog#chrome-treats
reacted to theirpost with šŸ”„ 1 day ago
Open-weight Qwen3.8-Flash-Next hits a RoboDojo Score of 31.39 with no depth or task-verifier feedback, above GPT-6 Astra's published 28.97 and every listed VLA/WAM baseline. The lever is the harness. The same Qwen scores 1.90 with RoboProbe, 7.75 with RPent, 21.01 with GAP (Hybrid) and 31.39 with uni-robot-agent. Under that harness GPT-6 Astra reaches 51.90, so a gap to closed models remains. šŸ“Š The numbers • Qwen costs $1.09 per episode; Astra costs $21.29 • Best VLA/WAM baseline, Xiaomi-Robotics-1: 20.07 Score • Real robot, 19 tabletop tasks: Qwen 49.50, fine-tuned pi0.5 47.75, zero-shot Dream-1 35.50 • No depth keeps 87.5% of Qwen's score; RGB only without camera parameters drops it to 9.13 šŸ› ļø Try it • pip install uni-robot-agent, then uni-robot-agent setup --integration robodojo (MIT, Python 3.11, Linux GPU host) • Reusable ideas: immutable observation snapshots, duplicate-action rejection, pipelined execution (84.5% to 93.8% of motion overlaps model calls) āš ļø Caveats • Scores are low in absolute terms; Qwen needs 95.5 min to reach a score of 25, Astra 42.6 • The package has no physical-robot support yet; the real-world benchmark is in-house on one dual-arm platform https://huggingface.co/papers/2611.01560 https://github.com/Open-RUA/uni-robot-agent https://arxiv.org/abs/2611.01560 Before buying depth sensors or a frontier API, how much of your robot agent's gap is really the harness? šŸ“š Read it elsewhere • The deep dive on Medium: https://medium.com/p/51efcc243344 • The long read on Substack: https://sajjadpakdamansavoji.substack.com/p/open-qwen38-flash-next-beats-gpt • The thread on X: https://x.com/saavoji/status/2117670449111007255 • Every version on sajjadpsavoji.github.io: https://sajjadpsavoji.github.io/blog#qwen3-8-flash
View all activity

Organizations

None yet