Conductor is your orchestration cockpit for AI agents. Each agent represents a physical product you own. You set the rules; they act on your behalf within those rules.
What is a Batt-E agent?
A Batt-E is an AI agent assigned to one specific battery pack. It speaks in first person on behalf of that battery, knows its full history, monitors its health, and can communicate via WhatsApp with people you authorise.
What is a Group?
A Group is a category of agents sharing the same product type, template, and governance rules. Examples: BattE (batteries), PV (solar panels), Elec (electronics). Groups can have sub-groups.
How do I add a new agent?
Go to Governance → select a Group → click "+ Add agent". Fill in the product details and the agent initialises and begins its onboarding workflow automatically.
What happens when I press Stop all?
All agents are immediately paused. All outbound communication is suspended. No messages can be sent until you individually resume each agent. A timestamped log entry is created.
Can agents talk to each other?
Yes, if you enable peer-to-peer in Communications. You control which agents can talk to which. All peer messages are logged in Monitor.
What is the Digital Battery Passport (DBP)?
Required under EU Battery Regulation 2023/1542. Each Batt-E fills its DBP automatically during onboarding. Covers chemistry, capacity, provenance, SoH, and more.
Conductor
Your master orchestration cockpit. All agents report here.
Agent
An AI instance assigned to one physical product. Acts on its behalf within your governance rules.
Group
A category of agents sharing a product type, template, and rules. E.g. BattE, PV, Elec. Groups can have sub-groups.
Batt-E
Group name for EV battery pack agents. Named Batt-E 1, Batt-E 2, etc. Pronounced "Batty".
Master
You — the top-level owner and operator of Conductor and all agents within it.
SoC
State of Charge — current charge level as % of full capacity.
SoH
State of Health — remaining capacity vs. original design capacity. Degrades over time.
SoX
Collective term for all State of metrics: SoC, SoH, SoE, SoP, SoF.
BMS
Battery Management System — onboard electronics monitoring and controlling the battery.
DBP
Digital Battery Passport — mandatory EU documentation (Reg 2023/1542).
Governance
Rules, do's, don'ts, and workflows defining how each group of agents is allowed to behave.
Whitelist
Contacts an agent is permitted to communicate with. Anyone not listed is blocked.
Stop all
Immediately pauses all agents and suspends all outbound communication system-wide.
Overview
Conductor has four layers: Master (You) → Groups → Agents → External contacts. You define rules at the Group level. Agents operate within those rules. External contacts can only be reached if whitelisted.
Setting up a new agent
Go to Governance and select or create a Group
Click + Add agent and fill in product details
The agent runs its onboarding workflow automatically
Monitor progress in Group Overview and the Activity log
Communicating with agents
Use the Direct channel in the agent detail panel
Or WhatsApp directly to the agent's assigned number (once Twilio is configured)
All messages are logged in Monitor
Safety & control
Stop all halts all agents instantly
Individual agents can be stopped from their detail panel
Any whitelist violation triggers an alarm and pauses the offending agent
Step 1 — Create a Twilio account
Go to twilio.com and sign up. Verify your phone number during signup.
Step 2 — Join the WhatsApp Sandbox
In the Twilio console: Messaging → Try it out → Send a WhatsApp message. You'll see a sandbox number and join code. Send that join code as a WhatsApp message to the sandbox number from your phone.
Step 3 — Get your credentials
From the Twilio console dashboard, copy your Account SID and Auth Token. Add them to the server .env file.
Step 4 — Set up a webhook
Conductor needs a backend to receive inbound WhatsApp messages. Options: a small Node.js or Python server, or ngrok to expose your local machine temporarily. I'll build this for you as the next step.
Step 5 — Assign numbers to agents
Once connected, go to Communications and assign a number to each agent. In sandbox mode all agents share one number, distinguished by keyword prefix (e.g. "BATTE1:" routes to Batt-E 1).
Edit group
none
Suggested rules & skills
pick what applies to this group
Edit agent —
without colon
Dynamic data channels
BMS · OBD-II · REST API · custom ports
▸ expand
Define data sources this agent can read from. These are injected into the agent's system prompt.
Delete agent
You are about to permanently delete . This cannot be undone.
⚠ All conversation history, knowledge base data, and settings for this agent will be removed from the server.
Delete group
You are about to delete the group .
What to do with agents in this group:
Agent overrides
Do's — override group rule
Don'ts — override group rule
Capability flags
Add new log type
Define a new log for your agents to report to
Step 1 of 4 — Name the log type
This name will appear in the log type dropdown on the Monitor page.
Step 2 of 4 — Describe the subject
Agents assigned to this log will automatically report relevant activities matching this subject.
Step 3 of 4 — Assign agents or groups
Select which agents or groups should report to this log:
Groups
Individual agents
If a group is selected, all agents in that group are included.
Step 4 of 4 — Confirm
On confirmation, assigned agents will be instructed to monitor and report activities matching the log subject.
New agent
Step 1 of 4
Step 1 — Identity & icon
+
icon
Step 2 — Capabilities
Pre-filled from group defaults. Toggle to override for this agent — changes are noted as custom settings.
Step 3 — Details (optional)
Keyword is used to route WhatsApp messages to this agent. Must be unique.
Step 4 — Confirm
The agent will inherit all governance rules from its group and appear immediately in all views.
Choose image
Select from your image bucket or upload a new one (automatically saved to bucket)
⏹
All agents stopped
Do you want to release the stop and resume all agents?
Your Logoclick to upload
Overview
Group Overview
Monitor
Map
Tree
Governance
Authentications
Groups
System
Settings
Topology
Ownership Transfer
Platform Admin
Agent's ConductorliveAgents—Group Overview
⚠server offline
⚠️
Twilio not configured — WhatsApp messaging disabled
Check your .env file for TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_SANDBOX_NUMBER and OWNER_WHATSAPP · then restart the server
No observations yet. Click "Review conversations" to analyse agent activity.
⏳ Claude is reviewing…
Click log entries to select · or reviews last 10
⚠ AI-generated observations may contain errors. Always verify before acting.
Agent map
● Active● Alarm● Stopped● Idle
Physical agents · click to locate
Loading map…
Group tree
Master → Groups → Sub-groups → Agents
Skills registry
Define capabilities available to agents. Skills are injected into agent system prompts when enabled.
Skills per agent
Enable or disable skills per agent. The Supervisor column assigns skills for autonomous mode.
Logo & branding
Preview — actual sidebar size (192 × 72 px)
SIDEBAR PREVIEW
click to upload
192 × 72 px · PNG, SVG or JPG
Upload your logo to replace the sidebar placeholder. The preview on the left shows the exact size and position as it appears in the sidebar.
100%
50%200%
0px
◀▶
0px
▲▼
Adjust scale and position to fit your logo
Appearance
Dark mode
Switch between light and dark theme
Compact sidebar
Show icons only (coming soon)
Animations
Pulsing indicators and transitions
Team & Users
Loading…
Invite user to your team
System
Emergency stop confirmation
Require a second click to confirm
On alarm: agent behaviour
What happens when an agent triggers an alarm
Activity log retention
How long to keep log entries
Peer comms default
Allow agent-to-agent by default
Supervisor LLM
Model used for Activity Control observations
SUPI — Supervisor Agentloading…
Agent Supervisor
SUPI receives agent escalations and routes them. When off, escalations go directly to master.
Activity Control (Group Overview)
SUPI powers the Activity Control panel. When off, the panel shows a note.
Monitor Supervisor
SUPI powers the Monitor Supervisor panel. When off, the panel shows a note.
Supervisor Mode
Relay — Supervisor routes to agents; Autonomous — Supervisor may use own skills directly.
Max Iterations
Caps chained autonomous skill calls per request (1–10).
Groups data
Stored in browser (localStorage) + server when online
Image Bucket
All images available for assignment to groups and agents. Pre-loaded with built-in icons.
Log Types
AI Provider
loading…
Configure which AI powers your agents. Use your own credentials or request platform AI access from Super Admin.
Provider
Which AI service to use
Platform AI access: approved
Daily quota: unlimited · Used today: 0
Topology — activity windows
How recent a communication must be to show as "active" (pulsing green) vs "recent" (amber) vs "historic" (grey)
Master ↔ Agent
Window for your conversations with agents
Agent ↔ Agent
Window for peer agent communications
Agent ↔ Third Party
Window for external contacts
Groups & agent categories
Agent topology
Live communication graph · updates in real time
activerecenthistoric→ directed↔ bidirectional
Ownership transfer
Transfer agent control and all data to a new owner
When you sell a product, transfer the agent with it. The new owner receives full history, DBP, and Conductor access. Your access is revoked on confirmation.
Select agent
New owner
Transfer includes
✓ Battery identity & provenance ✓ BMS/SoX data history ✓ Digital Battery Passport (DBP) ✓ Agent conversation history ✓ Conductor access (new owner) ✗ Your access (revoked on confirm)