Run the Demo
Clone the OpenBox demo agent, plug in your keys, and see governance capture and evaluate every workflow event, activity, and LLM call.
Prerequisites
- Python 3.11+
- uv — Python package manager
- Node.js — Required for the demo frontend
- OpenBox Account — Sign up at platform.openbox.ai
- LLM API Key — From any LiteLLM-supported provider. The demo uses the format
provider/model-name(e.g.openai/gpt-4o,anthropic/claude-sonnet-4-5-20250929,gemini/gemini-2.0-flash)
You'll also need make and the Temporal CLI. Install both for your platform:
- macOS
- Linux
- Windows
xcode-select --install # provides make
brew install temporal
Or to manually install Temporal, download for your architecture:
Extract the archive and add the temporal binary to your PATH.
# Debian/Ubuntu
sudo apt install make
# Fedora/RHEL
sudo dnf install make
Download the Temporal CLI for your architecture:
Extract the archive and add the temporal binary to your PATH.
winget install GnuWin32.Make
# or
choco install make
winget install Temporal.TemporalCLI
Or download the Temporal CLI for your architecture:
Extract the archive and add temporal.exe to your PATH.
Clone and Configure
git clone https://github.com/OpenBox-AI/poc-temporal-agent
cd poc-temporal-agent
Install dependencies:
make setup
To get your OPENBOX_API_KEY, register an agent in the dashboard: Agents → Add Agent, set the workflow engine to Temporal, and generate an API key.
Copy .env.example to .env and set your values:
# LLM — use the format provider/model-name
LLM_MODEL=openai/gpt-4o
LLM_KEY=your-llm-api-key
# Temporal
TEMPORAL_ADDRESS=localhost:7233
# OpenBox
OPENBOX_URL=https://core.openbox.ai
OPENBOX_API_KEY=your-openbox-api-key
Run the Demo
The demo runs four processes that work together:
| Terminal | Command | What it does |
|---|---|---|
| 1 | temporal server start-dev | Starts a local Temporal server that orchestrates workflows — it schedules activities, manages retries, and maintains workflow state |
| 2 | make run-worker | Runs the Temporal worker that executes your agent's workflow and activity code. The OpenBox SDK is initialized here, intercepting every event for governance |
| 3 | make run-api | Starts the backend API that the frontend calls to trigger workflows and relay messages to the agent |
| 4 | make run-frontend | Serves the chat UI at localhost:5173 where you interact with the agent |
Start each in a separate terminal:
# Terminal 1 — Temporal dev server
temporal server start-dev
# Terminal 2 — OpenBox worker
make run-worker
# Terminal 3 — API server
make run-api
# Terminal 4 — Frontend
make run-frontend
You should see OpenBox SDK initialized successfully in the worker output.
Chat with the Agent
Open http://localhost:5173 — this is the demo frontend. The default scenario is a travel booking assistant.
Send a message (e.g., "I want to book a trip to Australia") and let the agent run through the full workflow. This generates the workflow events, activity executions, and LLM calls that OpenBox captures and governs.
What Just Happened?
When you ran the demo, the OpenBox SDK:
- Intercepted workflow and activity events — every workflow start, activity execution, and signal was captured and sent to OpenBox for governance evaluation
- Captured HTTP calls automatically — OpenTelemetry instrumentation recorded all outbound HTTP requests (LLM calls, external APIs) with full request/response bodies
- Evaluated governance policies — each event was checked against your agent's configured policies in real-time
- Recorded a governance decision for every event — approved, blocked, or flagged — giving you a complete audit trail
See It in the Dashboard
Open the OpenBox Dashboard:
- Navigate to Agents → Click your agent
- On the Overview tab, find the session that corresponds to your workflow run
- Click Details to open the Event Log Timeline
- Scroll through the timeline — you'll see every event the trust layer captured:
- Workflow start/complete events
- Each activity with its inputs and outputs
- HTTP requests to your LLM provider
- The governance decision OpenBox made for each event
- Click Watch Replay to open Session Replay — this plays back the entire session step-by-step
Next Steps
- How the Integration Works — Understand the single code change that connects your agent to OpenBox
- Configure Trust Controls — Set up guardrails, policies, and behavioral rules for LLM interactions