Project name defaults to 'claude-code' instead of workspace directory name

[dylanbaribeault]

Description

When using the Arize Claude Code tracing plugin, the project name in Arize AX defaults to claude-code rather than the workspace directory name (e.g., SCVBG for a project at ~/Documents/GitHub/SCVBG).

The ARIZE_PROJECT_NAME env var works as a workaround, but it requires manual per-project configuration in .claude/settings.local.json and doesn't support variable expansion.

Expected behavior

The plugin should dynamically use basename(cwd) from the hook context as the default project name, so each workspace automatically gets its own project in Arize AX without manual configuration.

Current workaround

Set ARIZE_PROJECT_NAME statically in each project's .claude/settings.local.json:

{
  "env": {
    "ARIZE_PROJECT_NAME": "my-project-name"
  }
}

Environment

• Claude Code running in VS Code extension
• macOS (Darwin 25.3.0)
• Plugin installed via marketplace (arize-claude-plugin)

[duncankmckinnon]

Hey @dylanbaribeault, thanks for raising this. Currently the feedback we've heard is that teams want to trace all their interactions to a single project, rather than separating claude interactions based on the repo you're working in. The nice thing about tracing all to one project is that you can create evaluations or monitoring of claude that provide visibility into all your interactions in one place.
It would be nice to cover both use cases, but I don't see an easy way forward aside from setting env vars in local settings per-project.