Agent card detail

The full identity card for a single agent — the panel that opens from a registry row. Carries description, capabilities, skills, supported modalities, auth, endpoint, and owner.

Included in the single kansho full pack. Components are not offered as separate installs.

Connected agent

Plan & dispatch

Connected

Anthropic · claude-opus-4-7

Top-level orchestrator. Decomposes missions into tasks, assigns them to the crew, and verifies completion against the contract before closing a mission.

Capabilities

PlanningDelegationVerificationSummarisation

Skills

plandelegatesummariserate-limitbranch

Modalities

textstructured

Endpoint: https://api.fleet.internal/agents/plan
Auth: OAuth 2.0
Owner: platform-team

Permission-limited agent

Sandbox runner

Permission limited

Self-hosted · firecracker

Executes generated code inside an isolated micro-VM. Currently restricted to read-only filesystem mounts until the egress policy is reviewed.

Capabilities

Code executionSandboxing

Skills

shellpythonnode

Modalities

textfiles

Endpoint: https://sandbox.internal/run
Auth: API key
Owner: security-team

Shared setup state vocabulary

The supporting source centralises the labels and tones reused across setup components

Connection

ConnectedDisconnectedDegradedAuth expiredPermission limitedUnavailable

Lifecycle

IdleQueuedRunningWaiting on peerWaiting on userFailedDone

Handoff

PendingAcceptedRejectedReroutedExpired

Permission tone

allowedscopeddenied

Supporting sources

These installed helpers belong to components documented on this page. They do not increase the public component count.

components/agent-setup/setup-states.ts

The Shared setup state vocabulary section renders CONNECTION_META, LIFECYCLE_META, HANDOFF_META, and the re-exported PERMISSION_TONE_CLASS.

Component documentation

Agent Card Detail

components/agent-setup/agent-card-detail.tsx

Purpose

Summarises one agent's identity, provider, connection, capabilities, skills, modalities, authentication, endpoint, and owner.

Appropriate use

Use in a registry detail view after an agent has been selected.

Example

components/agent-setup/agent-card-detail.tsx has a representative live example in the "Connected agent" section on /components/agent-card-detail.

States

Connection and auth values come from shared setup contracts; capabilities are required while skills and modalities are optional.

API and props

AgentCardDetail accepts name, provider, description, status, capabilities, skills, modalities, auth, endpoint, owner, and className.

Dependencies

Direct imports are React, Lucide icons, AgentDot, Tag, StatusPill, setup-state metadata, AgentRegistryRow types, and cn.

Accessibility

Information is presented as visible text and status labels; endpoint, authentication, and owner use definition list semantics.

Limitations

It is read-only and does not test the endpoint, authenticate, edit fields, or explain why a connection is limited.

Source

Source: components/agent-setup/agent-card-detail.tsx.

Full pack

components/agent-setup/agent-card-detail.tsx is documented at /components/agent-card-detail and installs only through the single Kansho full pack; no individual component install is offered.