Definition
AUP
Agentic UI Protocol
AUP (Agentic UI Protocol) lets an application express what is shown and what actions are available. A runtime then renders the parts that fit its device capabilities, instead of treating one screen's pixels as the application itself.
Our term
- Also called
- Agentic UI Protocol
- Read more
- AUP →
Explore this topic
Learning
- From protocol to site
Understand an interface tree, its protocol and how a website presents it.
- What is AUP?
Agentic UI Protocol describes interface structure and its connections to state and actions.
- What is in an AUP tree?
Read identities, types, properties and children through one task card.
- How do src, bind and propBind differ?
Reading resources, writing input and updating properties are distinct connections.
- What happens after a click?
Trace an interface event to an explicit operation target.
- How do AUP and Web Device divide responsibilities?
One describes interface contracts; the other organizes a Web site implementation.
Articles
- Ontology, Explained Through Our Own Website
From Palantir's Ontology to the events, articles and learning materials on ArcBlock's website: how objects, relationships and runtime capabilities give people and AI agents shared material to work with.
- Why Aside Is Built for Working with Agents
Aside was designed around both the human experience and agent access. AFS lets both work with the same library, while structured interactions give people a way to make decisions and keep the work moving.
- Recreate My ASE 2026 AFS-UI Demo with ChatGPT
Follow the prompts from my ASE demonstration to make a website, interactive examples and slides, and see why a working environment makes short instructions useful.
- What Endures When Everything Evolves?
From Lode Runner on an Apple II to Unix, X Window and the early internet, Robert Mao traces the experiences behind AFS-UI and a shared interface system for people and agents.
- Introducing AFS-UI: one interface for people and agents
AFS-UI lets people use a rendered interface while agents reach its corresponding structure through paths. An introduction to AFS, AUP, Web Device and the surrounding UI landscape.
- When the interface changes, the work should remain
AI can generate a fresh interface at any moment. How do people and agents keep working on the same thing? A journey from OpenAI Intelligent UI and UI protocols to X Window and a working AFS-UI experiment.
Products
- ARC active
The runtime for Blocklets. It gives a developer a place to run an application described as a Blocklet, together with the resources that Blocklet declares it needs.
Events
Terms
- AFS
AFS (Agentic File System) turns the files, services, and active work relevant to a task into an inspectable resource view. Instead of handing an agent an undifferentiated machine or a pile of APIs, it gives the task a world with names and boundaries.
- AFS UI
AFS-UI builds interfaces over the addressable resources of AFS. People use a rendered interface; agents can inspect and operate its exposed structure through paths. AUP describes the interface and its interactions, while a UI device such as Web Device renders it.
- ARC
ARC is the runtime for Blocklets. It gives a developer a place to run an application described as a Blocklet, instead of making the runtime, the application, and its resource connections one unexplained deployment.
- Context
Useful context is more than a prompt. It includes the documents, tools, and permitted actions that are relevant to the task. If those boundaries are vague, a capable model still has to guess what it may use.
- UI Device
Treats the browser as a device you can operate live, rendering AUP right there in the browser.
- Web Device
Declare a .web/ folder anywhere in AFS, and the data and AUP under it get rendered server-side into a website.