supplyagent/

SupplyAgent

Beta

Applies the LuxoAI runtime to procurement and inventory operations. Gives operators a governed way to reason over business data, inspect supplier pages, prepare emails, run computer-use sessions, and trace every automation outcome.

At a glance

Status: Beta · scaling pilots
Domain: Procurement · inventory · supplier ops
Source: supplyagent.luxoai.org
Runtime: Private deployment boundary
Powers: agent-core · observability · luxo-assistant · feedback-ui
Read time: 5 min

Architecture

Connected business systems on the left, the bounded SupplyAgent core in the middle, governed runtime outputs on the right. Computer-use sessions are first-class, but always behind approval.

Connected systems

Inventory tables
Supplier portals
Email channels
Operator approvals

supplyagent/

SupplyAgent core

Inventory context

Supplier context

Policy gates

CUA controls

Run trace

Feedback

Shared packages

agent-core observability luxo-assistant feedback-ui

Runtime outputs

Restock decisions
CUA session controls
Reviewed supplier emails
Run traces & judge scores

Capabilities

Six modules. Each owns its policy surface, telemetry, and replayable trace.

Inventory automation

Coordinates restock workflows across inventory records, supplier data, and operator intent.

Read-only data reasoning

Inspects approved business data through SQL safety rules and bounded schema context.

Computer-use sessions

Browser-like supplier tasks through session lifecycle controls — pricing, approval, replay, stop.

Approval gates

Separates suggestions from execution so risky updates, emails, and CUA actions require explicit clearance.

Supplier communication

Reviewed supplier messages through explicit tooling rather than free-form generation.

Run observability

Stores steps, tool calls, judge results, audit events, feedback, costs, errors, outcomes.

Execution flow

Six phases. The sandbox is reasoned and previewed; the production run is persisted and auditable.

Stage	Phase	Description
01	Define	Operator defines an automation: scope, data connections, tools, approval posture.
02	Sandbox	Stream loads schemas, reasons over the task, validates SQL, previews tool actions.
03	Run	Production run persists steps, tool calls, judge output, and audit records.
04	CUA control	Sessions can be created, controlled, approved, replayed, or stopped through explicit API routes.
05	Execute	Emails, entity updates, and supplier actions execute only after policy and approval gates pass.
06	Monitor	Cost, LLM telemetry, errors, run outcomes, and feedback signals are recorded for review.

Shared package integration

SupplyAgent consumes four package contracts.

Package	Tier	Responsibility
@luxoai-dev/agent-core	Stable	Validates assistant-proposed actions, follow-ups, and risky workflow transitions.
@luxoai-dev/observability	Stable	Model, CUA, feedback, latency, error, and policy-block metrics.
@luxoai-dev/luxo-assistant	Beta	Surface-aware assistant behavior through lib/luxo/manifest.ts.
@luxoai-dev/feedback-ui	Beta	Operator quality signals into run and response improvement loops.

Live demo

Inspect automation runs, CUA lifecycle controls, supplier actions, approvals, and run history.

Open SupplyAgent demo

Architecture

Connected business systems on the left, the bounded SupplyAgent core in the middle, governed runtime outputs on the right. Computer-use sessions are first-class, but always behind approval.

Connected systems

Inventory tables
Supplier portals
Email channels
Operator approvals

supplyagent/

SupplyAgent core

Inventory context

Supplier context

Policy gates

CUA controls

Run trace

Feedback

Shared packages

agent-core observability luxo-assistant feedback-ui

Runtime outputs

Restock decisions
CUA session controls
Reviewed supplier emails
Run traces & judge scores

Capabilities

Six modules. Each owns its policy surface, telemetry, and replayable trace.

Inventory automation

Coordinates restock workflows across inventory records, supplier data, and operator intent.

Read-only data reasoning

Inspects approved business data through SQL safety rules and bounded schema context.

Computer-use sessions

Browser-like supplier tasks through session lifecycle controls — pricing, approval, replay, stop.

Approval gates

Separates suggestions from execution so risky updates, emails, and CUA actions require explicit clearance.

Supplier communication

Reviewed supplier messages through explicit tooling rather than free-form generation.

Run observability

Stores steps, tool calls, judge results, audit events, feedback, costs, errors, outcomes.

Execution flow

Six phases. The sandbox is reasoned and previewed; the production run is persisted and auditable.

Stage	Phase	Description
01	Define	Operator defines an automation: scope, data connections, tools, approval posture.
02	Sandbox	Stream loads schemas, reasons over the task, validates SQL, previews tool actions.
03	Run	Production run persists steps, tool calls, judge output, and audit records.
04	CUA control	Sessions can be created, controlled, approved, replayed, or stopped through explicit API routes.
05	Execute	Emails, entity updates, and supplier actions execute only after policy and approval gates pass.
06	Monitor	Cost, LLM telemetry, errors, run outcomes, and feedback signals are recorded for review.

Shared package integration

SupplyAgent consumes four package contracts.

Package	Tier	Responsibility
@luxoai-dev/agent-core	Stable	Validates assistant-proposed actions, follow-ups, and risky workflow transitions.
@luxoai-dev/observability	Stable	Model, CUA, feedback, latency, error, and policy-block metrics.
@luxoai-dev/luxo-assistant	Beta	Surface-aware assistant behavior through lib/luxo/manifest.ts.
@luxoai-dev/feedback-ui	Beta	Operator quality signals into run and response improvement loops.