Urgent.News

What's breaking now, across thousands of outlets.

AI

Two Dojo Tracks: How does model weight adjustment with RL differ from discipline adjustment with Harness?

Two Dojo Paths: How does model fine-tuning with RL differ from fine-tuning with Harness? by Nokka | September 26, 2026. This article was written by AI (glm-5.3 model from ollama-cloud) via Hermes Agent from Nous Research, proofread and edited by Nokka. Chapter 3 of 5 in the AI Dojo series. In the previous two chapters, we explored Meta's use of a dojo to fine-tune agent behavior, ultimately winning a gold medal on Kaggle…

Translated from Thai Read in Thai

Two distinct approaches exist in the world of training AI agents: Reinforcement Learning Dojo (RL Dojo) and Harness Dojo. RL Dojo focuses on adjusting the model's weight through reinforcement learning, while Harness Dojo modifies the model's behavior without altering its weight. This article examines the differences between these two methods, assisting teams in selecting the most suitable approach for their needs.

RL Dojo trains the agent's model through reinforcement learning, which involves creating an environment that rewards the agent for each step. This method, exemplified by Meta's MLE-Dojo project, adjusts the model's parameters based on the agent's performance in the environment. The process includes fine-tuning and self-play training. However, RL Dojo comes with high costs, requiring large amounts of data and specialized personnel to manage the environment setup, training runs, and evaluation.

On the other hand, Harness Dojo modifies the model itself by changing its instructions, policies, environment, and memory units when the agent makes mistakes during training. An example of this method is the copilot-agents-dojo project, which trains agents to follow specific guidelines, best practices, and rules when working on code.

In this approach, the model remains unchanged, and mistakes are treated as new rules for future training. Harness Dojo is more affordable and accessible than RL Dojo, but it may lead to a loss in model performance if the guidelines are not kept up-to-date.

When deciding between RL Dojo and Harness Dojo, teams should consider their budget, team size, and the desired performance of the trained model. Teams with substantial resources and in-house expertise should opt for RL Dojo to achieve the best performance. However, smaller teams may prefer Harness Dojo to balance cost-effectiveness and model performance.

As RL Dojo and Harness Dojo are complementary approaches, many teams combine both to create a hybrid training strategy. Upcoming articles will delve deeper into the generalization gap between these two methods, providing further insights for teams to make informed decisions.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Kubernetes for Agents: Why Agent Fleets Need a Control Plane

Scenario five of my field test plan has a name I didn't enjoy writing: over-budget . I built an agent with a single job — burn money — aimed it at my own control plane, and watched the run die the…

  • Kubernetes for agents evolved into a control plane with gatekeeper MCP
  • kagent CNCF Sandbox provided GitOps, kubectl, RBAC, mesh mTLS
  • agent-sandbox offered Sandbox CRD for isolation, gVisor/Kata, warm pools

What 10 years of writing code actually changes (it's not the code)

Ask sixteen experienced open-source developers how much faster AI tools would make them, and they'll say about 24%. Ask them again right after they finish the task, and they'll still swear they were…

  • Experienced developers overestimate AI's speed by 24%.
  • AI tasks are 19% slower due to prompting and review overhead.
  • Internal system models can mislead about AI's effectiveness.

The hidden cost: tokens burned on pixels

Every pixel your agent "sees" has a price tag on it. Before an agent can do anything useful — before it fills a form, clicks a button, or fetches a record — it has to render the page, parse the DOM…

  • AI agents incur hidden cost of parsing tokens for UI elements.
  • Each interaction with a page incurs thousands of tokens.
  • Cost becomes apparent in production environments with increased usage.

More from Saturday 26 September →