Bridge Application
Command Line
Started with arguments, the bridge executes one run and exits — no web server, no MongoDB, no Elasticsearch. Nothing is persisted, so the CLI is for interactive work: reproducing a failing conversation, watching a device while it is driven, or trying a configuration before saving it.
./gradlew :promethist-bridge:bootJar
java -jar bridge/build/libs/promethist-bridge-*.jar \
--key=agent:tester \
--device-uri="https://eu.promethist.ai?key=agent:acme-support" \
--timeout=300 \
--playback
Options
| Option | Default | Meaning |
|---|---|---|
|
required |
Pipeline key of the tester agent. |
|
required |
What the tested application runs on — see Devices. |
|
Engine the tester connects to. |
|
|
— |
URL the device should open, typically an agent link. |
|
— |
Relay service, for device types that need it. |
|
— |
Extra query string appended to the device URI. Repeat the option to produce several runs. |
|
|
Device ref reported to the engine. |
|
|
Conversation locale. |
|
platform default |
Audio sample rate. |
|
|
Pacing multiplier for audio sent to the device. |
|
|
Run the conversation as text only. |
|
|
Suppress the engine’s system prompt for the tester. |
|
|
Enable server-side speech processing. |
|
|
Overall run timeout in seconds. |
|
— |
Turn cap per session. |
|
|
Consecutive conversations per run. |
|
|
Devices to run in parallel. |
|
— |
Device provider credentials, required for |
|
|
Milliseconds between starting devices. |
|
|
Concurrent runs. |
|
|
Show the device screen in a window and play the audio locally. CLI mode only — the web service runs headless. |
|
— |
Write the recording to this local path; |
Variable substitution is not applied in CLI mode — pass literal values.
Reading the Outcome
Run IDs and progress go to standard output, and each run logs its final status and reason on completion. Since nothing is stored, note the tester’s session ID from the log if the conversation needs to be inspected in the engine afterwards.
For repeatable, recorded and evaluated runs use the REST API instead — that is the mode which stores results and fetches evaluations.