Agent libOS: A Library-OS-Inspired Runtime for Long-Running, Capability-Controlled LLM Agents
Summary
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.
Similar Articles
We open-sourced an agent runtime built for the part everyone skips: running agents on real hardware, offline
An open-source agent runtime designed for running AI agents on real hardware, offline, with hardware I/O support and a visual builder, supporting multi-provider LLMs and on-device RAG.
@ishaan_jaff: We're open sourcing LiteLLM Agent Platform Run Claude Code, Codex, Hermes or any coding agent in isolated K8s sandboxes…
LiteLLM is open-sourcing its Agent Platform, allowing developers to run coding agents like Claude Code, Codex, and Hermes in isolated Kubernetes sandboxes without exposing real API keys.
@MaxJunestrand: Today we're announcing the Legora aOS™. It's something we've been building toward for three years, and I think it's the…
Legora has announced the Legora aOS, an agentic operating system designed to autonomously orchestrate entire legal workflows, from intake to delivery, using the new Legora Agent.
Formal Skill: Programmable Runtime Skills for Efficient and Accurate LLM Agents
This paper introduces Formal Skill, a runtime-native abstraction for LLM agents that encodes reusable procedures as executable state machines with JSON metadata, Python executors, and hook-governed control logic. An open-source implementation called FairyClaw is presented, showing competitive performance on Harness-Bench with reduced token usage.
Do coding agents need an OS-like control plane? I built a prototype and want critique.
The author introduces 'KnowledgeOS', a prototype control plane designed to govern local coding agents by managing task lifecycles, preventing state drift, and ensuring execution evidence. They are seeking architectural critique on whether this OS-like abstraction is necessary or if it constitutes over-engineering for agent workflows.