# Outdated Claude or Codex Version

Polyscope doesn't bundle the coding agents — it launches whatever `claude` or `codex` binary is installed on your machine. If a new agent version shipped but Polyscope still reports an old one, the binaries on your machine are stale. Updating Polyscope itself won't help; that updates the app, not the agents.

## Update the agent CLIs

Update each agent however you installed it:

```bash
claude update                      # Claude CLI
npm install -g @openai/codex       # Codex CLI (adjust for your install method)
```

Then confirm the new versions are on your `PATH`:

### macOS

```bash
which claude && claude --version
which codex && codex --version
```

### Windows

```powershell
where claude; claude --version
where codex; codex --version
```

## Restart Polyscope

Polyscope resolves the agent binaries when it starts, so after updating you need to fully restart the app — quit it completely (not just close the window) and reopen it. New sessions will then launch the updated binaries.

## Running a standalone server?

If the outdated agent is on a remote Linux server rather than your desktop, the same root cause applies but you restart the service instead. See [Standalone Server → Polyscope shows an outdated Claude or Codex version](/getting-started/standalone-server#polyscope-shows-an-outdated-claude-or-codex-version).