TigrimOSR v0.7.1 splits Judge from the agent loop and adds YAML-configurable multi-agent workflows
Unique_Champion4327 · reddit · 2026-07-28
What changed in TigrimOSR v0.7.1
The main architectural change is that the Judge is now separated from the primary Agent Loop and runs as an independent loop. After the agent finishes a task, its output is sent to the judge for quality and correctness checks; if it fails the rubric, feedback is sent back for another revision before the final result is returned.
What the platform supports
TigrimOSR is positioned as an open agentic engineering platform. Both loops can be configured separately via YAML, including:
- models and system prompts
- tools, MCP servers, and skills
- evaluation criteria and rubrics
- max revision rounds
- verification and feedback rules
It is written entirely in Rust, ships as a self-contained binary, and is released under Apache 2.0. Other features include custom YAML tools, built-in paper search via OpenAlex, six multi-agent architectures, browser control through Playwright MCP or Obscura, CLI agents, multi-provider API models, desktop and web UIs, mobile remote access, Telegram/LINE bots, and prebuilt macOS/Windows apps.
More from coding & agent
- Eve adds shadcn registry support for browser agent extensions — shadcn · 2026-07-28
- Agent Mini packs a usable local AI agent into about 3,000 lines of Python — Lordrovks · 2026-07-28
- A simple tool-call fingerprint can stop many LLM agent loops, but not all of them — Future_AGI · 2026-07-28
- AI Tool Robin Reduces Dark Web Research to 30 Minutes — tom_doerr · 2026-07-28
- The real bottleneck in an Excel + LLM system is preserving business knowledge — Tired40s · 2026-07-28
- Four models tried the same game-building prompt, and Opus 5 looked finished — victor_explore · 2026-07-28