TigrimOSR v0.6.2 — Open Loop Engineering: create your own custom agent loop with Rust browser + LINE/Telegram bots

Reddit r/artificial Tools

Summary

TigrimOSR v0.6.2 introduces Open Loop Engineering, allowing users to define custom agent loops via YAML profiles, integrates the Obscura Rust browser for web automation, and adds LINE/Telegram bot control. The release emphasizes transparency and user control over agent behavior.

Hi everyone, I’m building TigrimOSR, a Rust-native multi-agent AI workspace. The core idea is Open Loop Engineering: instead of using a fixed hidden agent loop, users should be able to create, edit, inspect, and control their own custom loop. In TigrimOSR, the agent loop is not locked inside the code. You can define it as a YAML profile: which tools the agent can use which MCP servers are available which skills are loaded which model/provider to use custom system prompts loop limits self-verification context compaction job evaluation rules So the philosophy is: Open Loop Engineering — create your own custom loop. Your agent loop, your rules. The new v0.6.2 release focuses on two major integrations: 1. Obscura Rust Browser integration TigrimOSR can now connect with Obscura, a lightweight Rust browser engine. This lets agents control a real browser for live web tasks without relying only on paid search APIs. It supports browser control for search and web reading, with an opt-in toggle for safety. Because both TigrimOSR and Obscura are Rust-native, the app + embedded browser can idle around ~270 MB RAM. 2. LINE and Telegram bot control You can now chat with and control your agent through messaging apps. Supported commands include: /agents /model /mode /loop /new /stop /status The bot can show live progress, send status updates, and support approve/deny actions for tool approvals. Telegram can also work without exposing a public URL. Other major features: Multi-agent orchestration with 6 modes: hierarchical, mesh, hybrid, pipeline, P2P, and P2P orchestrator Custom YAML agent loops for tools, MCP servers, skills, model override, system prompt, loop limits, self-verification, and context compaction Independent job evaluation: after the job finishes, a separate judge agent verifies the result against the objective and checks whether claimed files/artifacts actually exist Any LLM provider: OpenAI, Anthropic, DeepSeek, Kimi, Gemini, Ollama, and OpenAI-compatible APIs Local CLI agents: Claude Code, Gemini CLI, and Codex, without API keys Full tool calling: web search, Python, file I/O, shell, MCP servers, and skills Plugin system for bundling skills, MCP servers, agents, and connectors Local/remote/headless mode, including private access over Tailscale VPN Built in Rust: single binary, no Node/Python runtime required I don’t want agent systems to be black boxes. TigrimOSR is my attempt to make Loop Engineering open, editable, and reproducible. Repo: [https://github.com/Sompote/TigrimOSR]() I’d be happy to hear feedback, especially from people working on Rust apps, browser automation, local agents, multi-agent systems, or open loop engineering.
Original Article

Similar Articles

Agent libOS: A Library-OS-Inspired Runtime for Long-Running, Capability-Controlled LLM Agents

Hugging Face Daily Papers

Agent libOS introduces a library-OS-inspired runtime substrate for LLM agents, treating agents as schedulable processes with explicit capabilities, lifecycle management, audit records, and human approval queues. The design shifts the trust boundary from tool dispatch to runtime primitives, enabling long-running agents to be scheduled, authorized, resumed, and audited safely.