Loading video...

Video Failed to Load

Go Home

Can an agent explore a new environment, learn its causal structure, and keep improving without updating its model weights? We introduce RSIAgent, a framework for recursive self-improvement through autonomous exploration. Using Kimi-K3 and GLM-5.3 as base models, RSIAgent outperforms GPT-6 Astra on both OSWorld 2.0 and Agents’ Last Exam....

63,271 views • 1 month ago •via X (Twitter)

23 Comments

Biwei Huang's profile picture
Biwei Huang1 month ago

Learn more about RSIAgent - Blog: - Code: - Project: - Paper:

sekai's profile picture
sekai1 month ago

it’s called scaling test time interaction

Ritwik's profile picture
Ritwik1 month ago

Weight-frozen RSI is just a harness that keeps score. The env map is the learning signal, not another finetune.

Kevin 's profile picture
Kevin 1 month ago

Memory or knowledge is an extension of the encoding in model weights. If we treat them as one system it’s not surprising to keep one subsystem static and update other parts of system through rl

Colleen Yu's profile picture
Colleen Yu1 month ago

Huge leap! Happy to apply!

Raven Protocol 🐦‍⬛'s profile picture
Raven Protocol 🐦‍⬛1 month ago

Scaling experience is a really interesting direction. Fixed weights mean the same model can keep getting better as it gets access to more environments and compute.

Kevin Vicent's profile picture
Kevin Vicent1 month ago

To be honest, I understood 22% of what have been said here but I love the concept, and how every new agent framework is distilling and evolving from previous ideas, pushing RSI to a new frontier and dueling to battle all known concepts of how to approach to what SDLC used to be.

Robin | Poker x AI's profile picture
Robin | Poker x AI1 month ago

Impressive that fixed-weight agents can still boost performance, curious how stable the learned action‑condition‑outcome memory is across domain shifts

David Starmac Ai's profile picture
David Starmac Ai1 month ago

Self-improvement without touching weights feels like the practical path — cheaper than retraining and you keep the base model swappable. Does the causal structure it learns transfer to a fresh environment or does it start from zero?

Subramani R's profile picture
Subramani R1 month ago

Excellent info

Fajar M Reza's profile picture
Fajar M Reza1 month ago

Can recursive exploration improve agents without making evaluation drift across environments?

Andi Monroe's profile picture
Andi Monroe1 month ago

I think an agentic evolution keeps in possibility to change the model weights based on approved hypotheses. It is great two gated architecture, where model evolve slowly, but changes in runtime and this change possibly is core feature.

Liviu's profile picture
Liviu1 month ago

Is time to quit my GPT subscription and switch to Kimi k3

Makato Whatever's profile picture
Makato Whatever1 month ago

"Scaling Experience" is a great framing, but let's be honest about what it actually is: structured in-context retrieval with a fancy name. The real question isn't whether memory helps — of course it does — it's whether this scales past the context window. A 200k-token memory dump isn't "experience," it's a haystack with good PR. Show me RSIAgent at month 6, not day 1.

Varik Verilion's profile picture
Varik Verilion1 month ago

The interesting part is the evaluation loop. How does RSIAgent distinguish causal learning from a policy that simply gets better at exploration?

Y11's profile picture
Y111 month ago

@grok 这是个啥东西,有啥用?解决社会问题。

Siddhant Dubey's profile picture
Siddhant Dubey1 month ago

Super interesting, How does this method compare to continual learning where weights do get updated?

Money Intellectual's profile picture
Money Intellectual1 month ago

Computer-use that needs a human every step is labor with extra latency. Who owns silent failure on day 3?

Lejin's profile picture
Lejin1 month ago

Good, now when do we try fine tuning on these traces?

90S KID's profile picture
90S KID1 month ago

A landing page for recorded memory history containing one (1) circle. Bold. 🙄

Team Reagent's profile picture
Team Reagent1 month ago

This is awesome! I can't wait to try it out. I have tokens to burn with Qwen 3.8, we'll see how it does there

Bali as a Colony of Jakarta's profile picture
Bali as a Colony of Jakarta1 month ago

demo to try?

Nathan Shearer's profile picture
Nathan Shearer1 month ago

Perfectly timed. Incredible

Related Videos

Official OpenAI tip for Codex: stop burning GPT-6.1 Sol context on tasks GPT-6 Luna can swarm, while GPT-6 Astra sits idle put Astra on call as a dedicated adversary codex --model gpt-6.1-sol --agent adversary GPT-6.1 Sol acts as the lead architect, scoping architecture and validating pull requests GPT-6 Luna teammates take isolated git worktrees and hammer out implementations at medium effort GPT-6 Astra monitors the peer-to-peer bus as a dedicated adversary, only stepping in at three critical moments: → before a contract locks: does the frontend payload match the backend schema? → when a test breaks twice: are we patching the bug or just hiding the symptom? → before calling done: what attack surface or edge case did everyone overlook? GPT-6 Luna builds. GPT-6 Astra challenges. GPT-6.1 Sol merges and ships Jev engineering runs the identical pattern one layer down: mechanical decisions that need no reasoning (which file to open, which tool to invoke, retry or abort) execute in 16ms, so the frontier models only wake up when execution paths actually diverge Plan on high. Delegate on medium. Keep the adversary on peer-to-peer call. - the full team setup > GPT-6.1 Sol on high coordinates the session and synthesizes PRs > teammate-ux builds client state inside a separate git worktree > teammate-back writes endpoints and handles Redis atomic locks > teammate-adv runs invariant fuzzing and catches replay vulnerabilities > all teammates communicate directly over peer-to-peer messaging without coordinator drag > tasks.json manages file-level mutex locks so nobody steps on another worktree paste the setup and this prompt into Codex CLI below: "Configure my Codex workspace for autonomous agent teams: 1. Audit ~/.codex/agents and .codex/agents for teammate profiles fitting ux, backend, and adversary > Generate definitions only for missing roles > Pin model: gpt-6-luna, model_reasoning_effort: medium for workers, and model: gpt-6-astra for adversary > Assign each worker an isolated git worktree branch to eliminate file conflicts 2. Enable agent teams in ~/.codex/config.toml: > Set [agents] max_concurrent_threads_per_session = 8 > Lock main session model to gpt-6.1-sol with model_reasoning_effort = 'high' > Set approvals_reviewer = 'auto_review' 3. Initialize tasks.json in repo root with atomic file locking, allowing teammates to claim subtasks and resolve contracts directly over inter-agent messaging without coordinator intervention 4. Add a team rule to AGENTS.md: teammates must request an adversary security review before opening a pull request for the lead session Show every configuration diff first. Do not apply edits until confirmed" ↳

mirku

31,338 views • 1 month ago

36 GROK AGENTS. ASTRA ON FREE CREDITS. DUAL-MODEL ROUTING IS THE EDGE. not one chat window burning a paid invoice all day a swarm that routes cheap work to grok and only wakes gpt-6 astra when the task is actually hard ▹ the stack 36 agents on grok bot with flexible settings per role monitor, plan, write, code, QA, ship, each with its own lane part of the fleet is wired to gpt-6 astra through a china free-credit service layer free credits are not a toy promo here they are the fuel for frontier spikes without a monthly bleed ▹ dual-model routing easy jobs stay on grok: speed, volume, always-on loops hard jobs jump to astra: reasoning, long builds, sharp code the router decides by task type, not by ego if astra is not needed, astra does not spend free-credit bursts buy the expensive brain grok agents keep the factory running between bursts that is how the system feels unlimited not by breaking quotas, by refusing to waste them ▹ why it hits different most people pay frontier prices for every mid task operators split the brain and protect the credits 36 agents = parallel throughput dual routing = cost control with quality when it matters free credits = astra access without living on the invoice the constraint moved from "can i afford the model" to "did i route the job to the right model" ▹ the take single-model stacks die on bills and on boredom multi-agent + dual routing is the new default factory grok for the grind astra for the cut free credits for the spikes that used to empty the wallet bookmark this before everyone copies the route map comments: what % of your tasks actually deserve astra

cryptopsihoz

44,187 views • 2 months ago