Stealth preview — docs are early and rough. Please don't share publicly.
New Theory
DocsAPIModels

Install newt

Install the newt CLI as a global tool from the private newt-python repo. Takes about five minutes.

View as Markdown

Draft — pending review.

This page hasn't been reviewed yet. Content may change before it's considered ready.

New Theory ships from a private GitHub repo today, not PyPI. Installing requires an SSH key on a GitHub account with access to the new-theory-research organization; access is by invitation from New Theory. A public PyPI release is eventually planned.

Install the CLI with uv tool

uv tool install puts newt on your PATH as a global command — no virtual environment to create or activate:

uv tool install "git+ssh://git@github.com/new-theory-research/newt-python.git"

If uv is not installed: curl -LsSf https://astral.sh/uv/install.sh | sh, then source $HOME/.local/bin/env.

If newt isn't on PATH after install, run uv tool update-shell — this adds ~/.local/bin to your shell profile. uv's own installer handles it automatically for new installs; a manual shell may need it once.

Python 3.11 or newer is required. uv python install 3.12 if you need it.

Add the library to a Python project

The newt Python library installs into a project, not globally. You add it when you have Python code to write:

uv init my-robot
cd my-robot
uv add "newt @ git+ssh://git@github.com/new-theory-research/newt-python.git"

uv run python resolves the project environment regardless of shell state — no activation needed, agent-safe:

uv run python -c "from newt import Robot"

Starter kits run uv sync on first setup and handle the library install automatically.

SSH access

The install fetches over SSH, so ssh -T git@github.com must succeed with a key registered to a GitHub account that has access to the new-theory-research organization. A Permission denied (publickey) or Repository not found error means the key or the account lacks access.

Verify

newt --version

Or continue to Getting started — newt login in step 2 confirms the tool is on PATH and can reach the API.

Next

Getting started → — authenticate with an API key and confirm the API answers. No hardware needed.

On this page