Nine capability packs, 133 lanes, one model, built entirely by prompting Claude Code and Codex through the runtime’s MCP. A full run read back from its own event trail, and the claim it supports: a process built by an AI is debuggable in this runtime in a way an application is not. …
Watching the Meter: How We Analyze an Agent Team’s Token Cost and Dial It Down An always on agent team is a living thing, and living things eat. The interesting question is never “is it spending tokens” but “which parts,
How AgenticOS Tools Actually Run An agent net can do a lot with its built in transitions, but sooner or later it needs to reach outside itself: call a weather API, render a PDF in a container, run a maintenance
The harness — everything around the model — is the durable asset, and it deserves its own operating system. How Agentic-Nets acts as both the fabric a domain automation is made of and the control room it is observed, measured and extended from: the control loop, the self-building system, and who profits beyond developers. …
A Petri net that nobody can reach is a Petri net that nobody uses. Until now, AgenticOS processes lived behind a browser tab — the Angular GUI was the sole entry point for creating places, starting transitions, and inspecting tokens. That constraint vanished. AgenticOS now … …
A deep dive into AgenticOS’s polling-based executor architecture: how Petri nets can orchestrate work across networks, clouds, and corporate firewalls—without requiring a single inbound port. What if your automation platform could reach anywhere? Not just servers in your cloud VPC, but machines behind corporate firewalls. … …
