Running from a repo or a file

A git URL, a local file, or a pasted script — opsen works out how to install and run it.

A file

opsen run agent.py

A repository

opsen run https://github.com/you/your-agent

opsen reads the repo, works out the install step from what it finds — requirements.txt, pyproject.toml, package.json — and runs the obvious entry point. What it decided is recorded on the run, so a wrong guess is visible rather than mysterious.

Private repositories

Lend a GitHub credential to the run. The token is attached on the way out to GitHub's hosts and never enters the sandbox — see Agent credentials.

Pinning the install

When the guess is wrong or you want it deterministic, say so explicitly rather than letting detection decide. A run that installs something different each time is a run whose cost and behaviour you cannot compare across models.