zed-industries/zed · error · ValueError

ZedPierAgent requires EVAL_CLI_CONTAINER_PATH (the eval-cli

Error message

ZedPierAgent requires EVAL_CLI_CONTAINER_PATH (the eval-cli binary on the mounted volume, e.g. /data/builds/<id>/eval-cli)

What it means

Error "ZedPierAgent requires EVAL_CLI_CONTAINER_PATH (the eval-cli binary on the mounted volume, e.g. /data/builds/<id>/eval-cli)" thrown in zed-industries/zed.

Source

Thrown at crates/eval_cli/zed_eval/pier_agent.py:76

    "OPENAI_BASE_URL",
    "OPENAI_API_BASE",
    "GEMINI_API_BASE",
)


class ZedPierAgent(BaseInstalledAgent):
    """Runs Zed's headless eval-cli binary under Pier."""

    SUPPORTS_ATIF: bool = False

    @staticmethod
    def name() -> str:
        return "zed"

    def _container_binary_path(self) -> str:
        path = self._get_env("EVAL_CLI_CONTAINER_PATH")
        if not path:
            raise ValueError(
                "ZedPierAgent requires EVAL_CLI_CONTAINER_PATH (the eval-cli binary "
                "on the mounted volume, e.g. /data/builds/<id>/eval-cli)"
            )
        return path

    def install_spec(self) -> AgentInstallSpec:
        # The binary lives on the runtime-mounted volume, which isn't available at
        # image-build time, so the real placement happens in run() via
        # exec_as_root. install_spec only needs a non-empty, no-egress step.
        return AgentInstallSpec(
            agent_name=self.name(),
            version=self._version,
            steps=[
                InstallStep(
                    user="root",
                    run="true  # eval-cli is copied from the volume at run time",
                )
            ],

View on GitHub (pinned to bc538def45)

When it happens

Trigger: Thrown at crates/eval_cli/zed_eval/pier_agent.py:76 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zed-industries/zed@bc538def45 (2026-08-16). Data as JSON: /api/errors/ae1e351637abf2fd. Report an issue: GitHub.