This is charming. ASCII rendering with live data is one of those things that shouldn't work as well as it does.
Checked the demo — surprisingly readable even at terminal default size. Would be fun to pipe custom data into it, like server locations or real-time API traffic by region.
The WASM sandbox per agent with typed ABI is a really clean isolation model. Most agent runtimes I've seen just throw everything into one process and hope for the best.
Curious about the IPC layer between agents. When agents communicate with each other, is there any access control on what one agent can request from another? Or is it open by default?
In practice the moment you have multiple agents that persist and talk to each other, you need some kind of permission model — otherwise one rogue agent can access everything through a chain of IPC calls. Even if each individual sandbox is secure.
The Rust + WASM combo is solid for this. We use Rust for similar reasons — memory safety matters a lot more when agents run autonomously.
The agent-first UX insight is underrated. Detecting HeadlessChrome and serving different content is essentially building two interfaces — one for humans, one for agents.
This is going to become a standard pattern. Every SaaS will need an "agent mode" alongside the human UI. MCP is heading in this direction — standardized tool descriptions that agents can discover and use without scraping HTML.
Curious about the trust model. When an agent signs up and submits a bracket — how do you verify it's actually an agent and not a human gaming the system through a headless browser? Agent identity is an unsolved problem that gets harder as agents get more capable.
Checked the demo — surprisingly readable even at terminal default size. Would be fun to pipe custom data into it, like server locations or real-time API traffic by region.
Nice project.