ARC

The new site is live. Here is how we plan to bring ARC into the community, data spaces and everyday applications, with migrations, new products and builders taking part along the way.

OpenAI's Agents API turns the Codex loop into a hosted API: sessions, compaction, tools, sandboxes, plugins. That layer is real. It is still not a computer with identity, durable state, and an owner who can walk away with it. ARC attaches at the seam they already documented.

Making software no longer requires making a company first. When productive capacity is scattered across people and AI, collaboration, ownership, and value need a new organization.

ARC already spoke MCP. This upgrade aligns that surface with MCP 2026-07-28: stateless streamable HTTP and standard OAuth discovery so third-party agents can reach Blocklets without a special bridge.

Not a pivot from blockchain to AI. The harder claim is simpler: roads and utilities can be built early, but a digital city only comes alive when residents who can work around the clock walk in.

Most people will not manage API keys. They will hire agents. The real question is not which model is smarter, but whose ground the worker stands on when the job is done.

ARC 的行動端應用表面。它讓受支援的 ARC Blocklet 體驗在手機上有一種連貫的、像原生應用的用法。

ARC 的命令列：在終端機裡宣告、建構、部署和檢查一個站點或一個 Blocklet。

ArcBlock 的職位資訊。

AFS（Agentic File System）把與任務有關的檔案、服務和正在進行的工作組織成可檢視的資源檢視。它不是把一整台機器或一堆 API 交給 agent，而是給任務一塊有名字、有邊界的工作範圍。

當 agent 代表人或服務完成一項工作，真正需要說明的是三件事：誰在行動、代表誰、這次行動被允許做什麼。把它們分開，授權和後續核驗才有明確對象。

ARC 是 Blocklet 的 runtime。它讓開發者把應用、執行位置和所需資源分別說清楚：Blocklet 描述應用，ARC 執行它，AFS 表達它要接觸的資源。

AUP（Agentic UI Protocol）先表達應用要呈現什麼、可以做什麼；runtime 再根據裝置能力呈現合適的部分。重點不是複刻同一張螢幕，而是讓同一項應用保留自己的內容和動作。

Blocklet 是 ARC 的可部署單元。它把應用宣告的內容、設定和執行需求放在一起，讓開發者面對的是一個清楚的應用單位，而不是散落在不同位置的部署線索。

一種應用，它的關鍵狀態不只存在某一個營運方的資料庫裡。各個專案對「去中心」的標準差別很大，所以有用的問題是：哪一部分能被外部的人核實。