Skip to content

Agent System Layer

The OS-level execution plane for AI agents

Long-running AI agents cross models, tools, processes, files, and networks. AgentSight observes and explains that execution, ActPlane turns policy into enforcement at operating-system boundaries, and Akeep preserves provider-native session history so days or weeks of work remain inspectable and recoverable.

Works with existing agentsOS-level evidenceEnforcement on the execution pathRecoverable session history
Open-source tractionAgentSightAgentSight stars on GitHubActPlaneActPlane stars on GitHubAkeepAkeep stars on GitHub

01

Observe

Inspect active sessions, processes, model and tool calls, file and network activity, and resource use.

02

Explain

Connect prompts, skills, and tool decisions to system effects, attention shifts, iteration paths, and failures.

03

Enforce

Compile intent and temporal context into allow, block, kill, or notify decisions at operating-system boundaries.

04

Preserve & recover

Version provider-native session files, verify history integrity, and continue after a device or provider changes.

Long-running agents need a system layer beyond application traces

Application-level tools explain prompts, tokens, evals, and latency. The system layer continues the story: what actually executed, whether policy held on the execution path, and whether interrupted work can be recovered from trustworthy history.

Application / SDK / gateway

  • Each application needs an SDK, callback, or gateway integration
  • Closed-source CLIs are limited to the logs they expose
  • Traces often stop at framework or process boundaries
  • Subprocess and local file activity can be missed

Agent system layer

  • AgentSight correlates LLM, process, file, and network events from outside the process
  • ActPlane enforces policy across exec, file, network, and syscall paths
  • Akeep preserves provider-native history with integrity checks and recovery
  • Adopt each component independently or use them as one execution plane

What the system layer should answer

Start from real problems in long-running work, platform integration, and governance.

Days or weeks of autonomous work

Understand the run in 30 seconds

See where attention moved, which files and modules changed, how tests and implementation alternated, and where attempts repeatedly failed.

Platform / SRE

Connect existing observability

Export system behavior from closed-source CLIs and mixed agent frameworks into existing tracing or profiling pipelines without modifying each agent.

Security / governance

Audit, govern, and recover system effects

Use AgentSight for execution evidence, ActPlane for enforced policy, and Akeep for verifiable, recoverable session history.

See what the system layer actually produces

These are existing project interfaces and presentation visuals: AgentSight makes long-running execution observable, ActPlane moves policy onto the execution path, and Akeep preserves native history for inspection and recovery.

AgentSight · Observe and explain

Move from agents running now, to attention moving across a week, to where time and tool calls accumulated.

AgentNebula replay of AI agent file activity
AgentNebula replays file structure and attention using the agent's actual read and write timing.
AgentSight top view showing live AI agent sessions
The live top view summarizes sessions, models, tokens, health, processes, tools, and file activity.
AgentSight semantic flamegraph of AI agent activity
The semantic flamegraph connects prompts and tool paths to weighted system effects.
AgentSight architecture
AgentSight correlates agents, model calls, and execution behavior from system events.

ActPlane · Enforce on the execution path

High-level rules compile into system policy; interpretation stays in userspace while enforcement sits on kernel paths every process must cross.

ActPlane policy DSL compiled into operating-system enforcement
The policy DSL carries intent and temporal context into operating-system enforcement.
ActPlane runtime architecture with policy, compiler, IFC engine, and feedback
The runtime loop connects policy, compilation, authority checks, the IFC engine, and semantic feedback.

Akeep · Preserve and recover native session history

Akeep versions provider-native files directly. Ordinary use can be a commit; diff, integrity checks, and recovery are available when needed.

Day 1   akeep commit -m "first working path"

Day 2   akeep commit -m "after failed migration"

Day 7   akeep diff HEAD~1 HEAD

When a device or provider changes, the history remains inspectable, verifiable, and recoverable.

akeep fsck HEAD

akeep checkout HEAD --to /tmp/recovery

Continue.

Observe & explain

AgentSight

Local-first AI agent profiling and monitoring that connects prompts, models, and tool decisions to process, file, network, and resource activity, with reports, agentpprof, and OpenTelemetry export.

Enforce

ActPlane

Compiles intent and temporal context into policy enforced across syscall, exec, file, and network paths, with concrete feedback when an action is denied.

Preserve & recover

Akeep

Versions provider-native agent session files for integrity checks, diffs, and recovery without converting history into another agent-memory format.

Contact

Talk to Eunomia Labs

Operated and maintained by Eunomia Labs, Inc., with a focus on systems engineering for eBPF, runtime extension, and AI agent infrastructure. Reach out directly for enterprise evaluation, POCs, and production integration.

Email usyusheng@eunomia.devTypically replies within 2 business days