nooa-cli
CLI for nemo-oo-agents. Ships the nooa command with subcommands for running evaluations, browsing traces, and managing config.
Install
uv add nooa-cli
# ...with numpy/pandas/plotly/scipy/sklearn pre-loaded into the LLM REPL
uv add "nooa-cli[datascience]"
nooa-cli automatically pulls in matching nemo-oo-agents (the core framework). The [datascience] extra adds libraries the LLM can use in REPL-generated code.
Usage
nooa --help
nooa start-dev # launch the trace viewer
nooa eval ... # eval pipeline runner
nooa traces ... # inspect/manage trace files
Install the separate nooa-acp package to add the nooa acp plugin command and
run the NOOA coding agent from an ACP-compatible client:
uv add nooa-acp
export NOOA_MODEL=nvidia_nim/nvidia/nemotron-3-super-120b-a12b
export NVIDIA_API_KEY=nvapi-...
uv run nooa-acp
See the main repo README for the framework documentation.
Interactive coding sessions
nooa_cli.sessions owns durable coding-agent session identity, metadata, and
conversation replay shared by CLI hosts such as the native TUI and ACP. The
process running an agent owns the writable session handle; other hosts attach
through their transport or use read-only discovery. Generic event and SQLite
storage primitives remain in the core nooa package.
3 maintainers
Metadata
3 maintainers
Release files for nooa-cli 0.0.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nooa_cli-0.0.10.tar.gz | 89.9 kB | Without provenance | Details for nooa_cli-0.0.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nooa_cli-0.0.10-py3-none-any.whl | Python 3 | none | any | Details for nooa_cli-0.0.10-py3-none-any.whl |
Total release size: 176.2 kB
Release files / nooa_cli-0.0.10.tar.gz
| Download URL | nooa_cli-0.0.10.tar.gz |
|---|---|
| Size | 89.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
845d029afaed26166ca16ed15bfa69308703aac7aefc6afece5cddfa47ecbf6e
|
|
BLAKE2b-256 checksum How to use checksums |
36c6d1e555b461b508cf43b9c8ba55f3359dc94fbcbda231013c101ef5543297
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.4 {"installer":{"name":"uv","version":"0.11.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / nooa_cli-0.0.10-py3-none-any.whl
| Download URL | nooa_cli-0.0.10-py3-none-any.whl |
|---|---|
| Size | 86.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a9414898f12c51797b0ba2cf8ece97899dcf30e684690d72b54cceac6afdb4e
|
|
BLAKE2b-256 checksum How to use checksums |
4acdc9a53e62e08394b30f0f2de466f6d61b2ab66b32de0be1e23be2ff9ffbfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.4 {"installer":{"name":"uv","version":"0.11.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for nooa-cli 0.0.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
