Skip to main content

​
sovara: command not found

Open a new terminal after installing the CLI so the shell reloads PATH. If it still fails, reinstall and verify:

​
Sovara is not reachable

Check the currently configured app environment:
For a local desktop environment, open the desktop app and retry. For remote deployments, set SOVARA_APP_SERVER_URL for app commands. Configure the exec server URL and agent token directly in the Python or TypeScript SDK for headless agent hosts.

​
record says no SDK-created run was observed

The child command ran, but it did not complete an SDK top-level run. Confirm that the executed path reaches:
record does not add this boundary automatically.

​
A run appears in the wrong project

Change the project name in the SDK integration:
  • Python: SovaraClient(project_name="...")
  • TypeScript: new SovaraClient({ projectName: "..." })
The current directory and record command do not select a project. Project names are immutable; a new name selects or creates a different project.

​
A module is missing during record

Use the same environment that normally runs the application:

​
A project-scoped command requires --project-id

List accessible projects, then pass a full ID, unambiguous ID prefix, or exact project name:

​
rerun says the replay API key is not configured

Set a replay key for the provider shown in the error, then retry. See Replay Keys.

​
rerun says the step is not replayable

Only recorded LLM calls can be rerun. Inspect tool calls and custom traced functions with probe, then rerun the complete application normally.

​
Restricted shell or sandbox writes fail

Allow writes to the global Sovara state directory, or install the assistant skill so it can configure that access. For Python package caches, use writable temporary locations when necessary: