AUP
Agentic UI Protocol
AUP(Agentic UI Protocol)は、アプリケーションが何を表示し、どの操作を可能にするかを表現します。runtime はデバイス能力に合う部分を render し、一つの画面の pixel をアプリケーションそのものとして扱いません。
- 別称
- Agentic UI Protocol
- さらに読む
- AUP →
関連する解説と実践
学ぶ
- 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.
記事
- 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.
製品
イベント
用語
- AFS
AFS(Agentic File System)は、タスクに関係するファイル、サービス、実行中の作業を確認可能なリソース表示にします。agent に区別のないマシンや API の束を渡すのではなく、名前と境界を持つ作業世界を与えます。
- 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 は Blocklet の runtime です。Blocklet として記述されたアプリケーションを動かす場所を提供し、runtime、アプリケーション、リソース接続を説明のない一つの deployment にしません。
- UI Device
ブラウザをその場で操作できる device として扱い、AUP をブラウザ内で直接描画します。
- Web Device
AFS のどこかに .web/ フォルダを宣言すると、その下のデータと AUP がサーバー側でウェブサイトとして描画されます。
- コンテキスト
役に立つ context は prompt だけではありません。タスクに関係する文書、tool、許可された操作も含まれます。境界が曖昧なら、能力のある model でも何を使ってよいか推測するしかありません。