メインコンテンツへスキップ

ARC 2.0.0-beta.28 · AUP Web-only widget

agent

AUP Web-only widget `agent`: purpose, boundaries, surfaces, fallback, and evidence.

AUP Web-only widget — not a cross-device primitive; not a Web Device layout component.

The name is registered in AUP_WIDGETS (packages/aup/src/aup-types.ts). It can be accepted by structure verification and implemented by a Web runtime (or native target where noted). It is not one of the 18 cross-device AUP_PRIMITIVES, does not enter DeviceCaps.primitives via fillPrimitives, and is not a Web Device theme/site layout component (for example content-card or page-breadcrumb).

Purpose

Interactive agent chat surface scoped by src (tool/read/exec boundaries) with optional dataPath for conversation persistence. Client reuses the chat renderer.

Boundaries

  • Do not document this type as a portable primitive.
  • Do not mix it with Web Device layout-component reference pages under widgets/.
  • A parser-accepted name is not a portability or product-readiness claim.

Author entry

AUP tree / DSL type: "agent". Registry documents mode, welcome, dataPath, and config events.

Surfaces

Interactive Web session. Not a static document renderer entry.

Fallback

No degradation chain as a widget. Requires session, identity, and AFS scope review.

Evidence

SourcePath
Registrationpackages/aup/src/aup-types.ts; packages/aup/src/aup-dsl.ts
Registryproviders/runtime/ui/src/aup-registry.ts (agent)
Interactive switchproviders/runtime/ui/src/web-page/core.ts case "agent"→renderAupChat``
Handlersproviders/runtime/ui/src/agent-handler.ts

Paths are relative to the Arc repository checkout used for this documentation baseline.

Sample

Internal / experimental for public samples. Registration and renderers exist in the interactive Web runtime (and sometimes Web Device widget packages), but this site does not ship a docs-safe live sample. Do not infer product readiness from the type name alone.

Related