Start a run

Before starting, connect a LiveKit or Retell agent and add at least one test to your suite. When the run is created, Egma saves the test and persona versions, persona settings, and grader selection, versions, settings, and thresholds. Queued simulations and retries use that saved selection. A new persona clone or a grading policy change applies only to future runs.

Start the run

Open Runs and select Create a run.
Choose your test suite.
Choose the agent and one of its connections. Review the run settings. To change concurrency, open Advanced Settings.
Select Start run.
Open the run to follow its simulations. Starting successfully does not mean the tests passed.

Run egma pull to refresh the agent and connection IDs in egma/config.yaml. Use the IDs for the agent and connection you want to test:

egma run create appointment-booking \
  --agent "$EGMA_AGENT_ID" \
  --connection "$EGMA_CONNECTION_ID" \
  --name "Appointment booking check"

appointment-booking names a direct directory under egma/tests/. EGMA_AGENT_ID and EGMA_CONNECTION_ID are shell variables you set to the IDs from your configuration.The command pushes your local Egma project changes, starts the run, prints its ID and results URL, and returns. A zero exit code means the run started. It does not mean that simulation execution or grading passed.Voice runs use concurrency 4 by default. Chat runs use 10. Add --concurrency <number> when this run needs a different limit. Deployment and provider limits still apply.If the pre-run push is refused, no run starts. Resolve the reported test change or invalid content first.To read the full run as JSON:

egma run get "$EGMA_RUN_ID" > run.json

The result includes every simulation and run event. Run the command again to refresh an active run. Recording files are not downloaded.

Next steps

Review a run to inspect conversations and grades.

Get started

Core Philosophies

Platform

Integrations

Support

Start a run

Start the run

Next steps

​Start the run

​Next steps

Start the run

Next steps