> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ospribrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Packages and Development

> Use the managed general toolchain and create project-local dependency environments.

## Managed general tools

Full Workstation defines Node, npm and npx, CPython 3.12, uv, portable Git, FFmpeg, ripgrep, jq, archive tools, CA certificates, and Chromium on the managed execution path.

These tools are separate from software already installed on the computer.

## Science packs

Full Workstation verifies six separate pack roots for core science, documents, chemistry, structures, genomics, and machine learning. OSPRI builds a trusted Python import path from those activated roots for agent shell, visible terminal, and local coding commands.

User-supplied `PYTHONPATH` values are rejected rather than inherited.

<Warning>
  Managed science-pack roots currently appear before project-environment `site-packages` when the same package exists in both places. A project lockfile alone does not prove which overlapping version Python imported. Before relying on an exact version, ask OSPRI to print the package version and imported file path inside that project's environment.
</Warning>

## JavaScript and TypeScript dependencies

For a coding project, ask OSPRI to use the package manager already present in that repository. A safe flow is:

<Steps>
  <Step title="Inspect the project">
    Check its lockfile, package manager, scripts, and repository instructions.
  </Step>

  <Step title="Approve the exact install">
    Package installs require a fresh approval and cannot become an Always allow grant.
  </Step>

  <Step title="Install in the project">
    The dependency is recorded in that project's manifest and lockfile rather than a global environment.
  </Step>

  <Step title="Run the repository checks">
    Run its own typecheck, tests, lint, build, or validator and read the real output.
  </Step>

  <Step title="Review or roll back">
    Review the dependency diff. Remove the package with the same project package manager if it is no longer wanted.
  </Step>
</Steps>

## Python dependencies

Use a project-local uv environment where possible. Record the dependency in the project's `pyproject.toml` and lockfile. If installation fails, inspect the wheel and compiler error before retrying or changing versions.

## Vendor compilers

Source-only native Node add-ons and Python packages may require a compiler. Xcode and Microsoft build tools are not bundled. OSPRI can detect a missing vendor tool and guide the user to the official installer.

## Durable coding work

Use **+ Coding project** for a device folder and **Deep build** for a longer local software task. Watch its progress in the Code panel. The cloud Generations tray is a different execution surface.