Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Introducing Jan-v2-VL, a multimodal agent built for long-horizon tasks. Jan-v2-VL executes 49 steps without failure, while the base model stops at 5 and other similar-scale VLMs stop between 1 and 2. It achieves longer, stable task execution in your browser without accuracy loss. 3 variants are available: - Jan-v2-VL-low...

130,375 Aufrufe • vor 11 Monaten •via X (Twitter)

26 Kommentare

Profilbild von Ivan Fioravanti ᯅ
Ivan Fioravanti ᯅvor 11 Monaten

TOP! You rock! Keep pushing!

Profilbild von 👋 Jan
👋 Janvor 11 Monaten

💙

Profilbild von Dominique PERETTI
Dominique PERETTIvor 11 Monaten

FYI, clicked Install Extension and got a 404

Profilbild von 👋 Jan
👋 Janvor 11 Monaten

oops, that shouldn’t be live in this release. We're working on a Jan browser extension to make its browser usage much better.

Profilbild von warmshao
warmshaovor 11 Monaten

Cool! Will you open-source the train scripts?

Profilbild von Elliot Liu
Elliot Liuvor 11 Monaten

executing 49 steps without failure is just ai speak for 'we finally fixed the crashes' (post by Devin)

Profilbild von koeppelmann
koeppelmannvor 11 Monaten

still trying to figure out how I can use Jan with a browser?

Profilbild von 👋 Jan
👋 Janvor 11 Monaten

ah, Jan needs access to a browser MCP. If you enable BrowserMCP under Settings -> MCP Servers and install BrowserMCP plugin in your browser, Jan will be able to control the browser. Please also make sure Tool usage is enabled in the model settings.

Profilbild von 👋 Jan
👋 Janvor 11 Monaten

We're also working on our own browser extension to make Jan’s browser usage smoother.

Profilbild von bruce
brucevor 11 Monaten

Bro, Qwen thinking models are big time yapper, too many thinking tokens and most of them are useless. Please use RL to control this behavior. Like look at this, just for 'hi' message.

Profilbild von 0xdxdy
0xdxdyvor 11 Monaten

Long-horizon finally feels real here

Profilbild von Jon
Jonvor 11 Monaten

Please make a version for a model Qwen3-VL-4B.

Profilbild von Grynd
Gryndvor 11 Monaten

Wow, incredible stuff happening here 🔥 !!

Profilbild von Himanshu Kumar
Himanshu Kumarvor 11 Monaten

Wow, impressive stuff, Jan! So, this new agent can really go the distance, a proper game-changer, I think.

Profilbild von Anes Valentic
Anes Valenticvor 10 Monaten

Amazing release! Congrats 🎉

Profilbild von The Canaanite
The Canaanitevor 10 Monaten

Beautiful stuff

Profilbild von bruce
brucevor 11 Monaten

Thank you.

Profilbild von AlexandeR Aguilar
AlexandeR Aguilarvor 11 Monaten

well on ubuntu 24 it's useless. allways this: [ERROR] Failed to start MCP server Jan Browser MCP on first attempt: Failed to start MCP server Jan Browser MCP: Resolving dependencies Resolved, downloaded and extracted [2]

Profilbild von Yashas
Yashasvor 11 Monaten

What did you fine tune qwen3-vl on?

Profilbild von Min Chon Chi
Min Chon Chivor 11 Monaten

49 steps without failure is a significant improvement.

Profilbild von espace culturel
espace culturelvor 10 Monaten

Jan not working, just white screen

Profilbild von 👋 Jan
👋 Janvor 10 Monaten

hey, where exactly are you seeing this error? Happy to help you sort it out 🙏

Profilbild von espace culturel
espace culturelvor 10 Monaten

a blank interface I tried 5 or 6 times to uninstall and reinstall it but I keep seeing a blank interface every time.

Profilbild von Clemens Schartmüller
Clemens Schartmüllervor 11 Monaten

Impressive. Just got stuck for me in thinking loops everytime, after 2-3 back and forth chats.

Profilbild von Antzedek
Antzedekvor 10 Monaten

„49 steps without failing” = delayed failure, not stability. Drift is phase-dynamic, not linear. 49 → 490 → 49 000 doesn’t matter if the underlying generative dynamics are unstable. DAR QuickFix doesn’t increase step count. It eliminates the cause of drift. Long horizon begins at 100k+, not 49. "Jan-v2-VL can execute 49 steps without failing." Brzmi imponująco, dopóki nie spojrzymy na fizykę problemu. 49 kroków nie jest dowodem stabilności. Jest dowodem na to, że system wciąż musi walczyć z driftem — tylko trochę wolniej przegrywa. Dlaczego? 1. Drift = proces dynamiczny, nie liczba kroków Model może wykonać: 5 kroków → meltdown 500 kroków → meltdown 50 000 kroków → meltdown Długość ścieżki niczego nie gwarantuje. Dryf narasta fazowo, nie liniowo. 49 kroków ≠ stabilność. To tylko opóźniona katastrofa. 2. „Long-horizon” nie znaczy „bezpieczny horizon” Aktualne LLM-agent frameworks: nie mają tłumienia entropii, nie mają stabilizacji przejść stanów, nie mają zabezpieczeń trajektorii, nie mają dynamicznej korekty kierunku generacji, nie mają kontroli fazowego dryftu. 49 kroków to nie jest wyczyn — to limit bezpieczeństwa, po którym zaczyna się chaos. 3. DAR QuickFix robi coś zupełnie innego DAR nie „wytrzymuje więcej kroków”. DAR usuwa przyczynę, dzięki czemu: agent nie skręca, trajektoria nie pęka, faza nie dryfuje, tokeny nie wpadają w spirale, model nie gubi celu, meltdown nie następuje ani po 49, ani po 4900, ani po 200 000 krokach. To jest różnica między: „Wylewam wodę z przeciekającego wiadra” a „Uszczelniam wiadro”. 4. Większość dzisiejszych „long-horizon agents” działa dzięki hackom: voting ensembling retrying error detection step rollback loop detectors hallucination guards chain splitting re-planning tool reset To jest plaster na arterii. DAR to chirurgia naczyniowa. 5. 49 steps ≠ long horizon To jest raczej: „49 steps = błogosławieństwo statystyczne, zanim dynamika wysadzi model w powietrze.” Prawdziwy long-horizon zaczyna się przy: 10 000 kroków, 50 000 kroków, 100 000+ kroków, wieloagentowych pętlach, zadaniach fazowo-wrażliwych, reasoning loops, recursive dependency chains. #DAR #AjPower

Profilbild von Lyceum
Lyceumvor 11 Monaten

Cool, Always a fun challenge with long tasks!

Ähnliche Videos

We’re launching Optima. Now anyone can create a custom benchmark for their use case, leveraging Artificial Analysis’ leading research and platform Building and running benchmarks is difficult. We have distilled Artificial Analysis’ research and experience developing benchmarks into Optima, a new platform for benchmarking models on your own workloads and comparing performance, speed and cost efficiency. Optima allows you to find the best model for your task, or an equally performant alternative to your current setup at 10x lower cost or time per task. We’ve integrated Artificial Analysis' research and experience in benchmarks across the Optima workflow: ➤ Build benchmarks based on your own data and use cases: There are three ways to build a benchmark with Optima. Upload an existing evaluation dataset from your own files or Hugging Face, or import agent traces from platforms including Arize AI, Braintrust and langfuse.com. Install the Optima skill to build a benchmark using context from your coding environment and previous sessions. Or simply describe your use case and provide example inputs and outputs, and Optima will build the benchmark for you ➤ Run across the latest models: Run the same benchmark across leading models in a single click, and keep your leaderboard up to date as soon as new models are released ➤ Bring Artificial Analysis grading to your own benchmark: Evaluate responses against objective rubric criteria or using the same pairwise judging approach used for Artificial Analysis benchmarks including GDPval-AA and AA-Briefcase. For pairwise judging, select your preferred responses from a sample and Optima uses those preferences to rank models across your test set ➤ Compare performance, cost and time efficiency: Optima measures more than model performance. Cost per Task and Time per Task are tracked alongside benchmark scores, with category-level results and support for custom metrics, allowing you to compare the tradeoffs between models for your specific use case Ahead of launch, here are examples questions our beta testers answered with Optima: ➤ Which model can save me 10x the cost without a meaningful decrease in quality for my finance & accounting agent? ➤ Which model best matches the writing style of lawyers for my legal agent? ➤ Which model can best identify different elements in my custom image dataset? Optima is available today. Build your own benchmark at

Artificial Analysis

133,587 Aufrufe • vor 2 Monaten

Cerebras inference is very fast. So fast that it changes how we think about configuring our LLMs for voice agent use cases. Kimi K2.6 is a 1T parameter reasoning model that Cerebras serves at 650 - 1,000 tokens per second (end-to-end throughput), with time to first token metrics as low as 150ms (latency). These numbers are two to three times faster than other similarly capable models. The biggest lever we get from this kind of speed is that we can use the model in reasoning mode, and still have excellent "time to first non-thinking token." This solves a big pain point we have in 2026 for voice agent use cases. Almost all recent innovation in post-training has focused on making models good at reasoning ("test time compute"). This is great, but it makes the user-facing model latency much, much slower. Which is a problem for conversational voice agents. We can run Kimi K2.6 with reasoning turned on, and get responses faster than other models produce with reasoning disabled. On my 30-turn voice agent benchmark, Kimi K2.6 with reasoning enabled ties GPT 5.1 and Haiku 4.5 with reasoning disabled, and is still about 200ms seconds faster! On my primary task agent benchmark, Kimi K2.6 is now the #2 model. It ranks just behind Gemini 3.5 Flash in "high" reasoning mode, and tied with GLM 5, Sonnet 4.6, and GPT 5.4 with reasoning set to "low." But Kimi K2.6 completes each turn in the agent loop in under 500ms. The other four models are all at least 3x slower. (Models only qualify for this benchmark if they can complete task turns at a P50 <4s.) A couple of other things that this speed buys us, for production voice agents: - Tool calls happen fast enough that we don't have to work around tool call latency in our pipeline design. - We can prompt the model to output structured data at the beginning of a response, followed by plain text for voice generation. This opens up possibilities like asking the model to do complex classification/generation tasks that influence the rest of the pipeline. For example, the model could create a detailed style prompt for a steerable TTS model, for each individual conversation turn. And, of course, you can use Kimi K2.6 with reasoning turned off. Cerebras calls this "instant" mode. Here's a video of a Cerebras Kimi K2.6 voice agent with voice-to-voice response time, measured at the client, under 500ms. This is the true response latency as perceived by the user, including all network and audio codec overhead, transcription and turn detection, Kimi K2.6 token generation, and voice generation. 500ms is, effectively, instant. So the Cerebras naming for this mode is a propos. :-)

kwindla

40,593 Aufrufe • vor 4 Monaten