nooa-cli 0.0.8__tar.gz → 0.0.10__tar.gz

{nooa_cli-0.0.8 → nooa_cli-0.0.10}/.gitignore

@@ -1,4 +1,4 @@
-# Rust toolchain (installed for nemo_flow PyO3 build)
+# Rust toolchain (installed for nemo_relay PyO3 build)
 .cargo/
 .rustup/
 
@@ -296,7 +296,7 @@ agents/**/traces/
 .config/
 .local/
 
-# Rust toolchain (installed by rustup for nemo-flow build)
+# Rust toolchain (installed by rustup for nemo-relay build)
 .cargo/
 .rustup/
 
@@ -366,7 +366,6 @@ sft_data/**/*.jsonl
 
 # Git credentials (must not be committed)
 .git-credentials
--e
 # Bridge watchpoint file — per-worktree, never committed
 .bridge_watch.json
 

{nooa_cli-0.0.8 → nooa_cli-0.0.10}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: nooa-cli
-Version: 0.0.8
+Version: 0.0.10
 Summary: CLI for nemo-oo-agents (`nooa` command: eval runner, trace viewer, config)
 Project-URL: Homepage, https://github.com/NVIDIA-NeMo/labs-OO-Agents
 Project-URL: Repository, https://github.com/NVIDIA-NeMo/labs-OO-Agents
@@ -44,9 +44,27 @@ uv add "nooa-cli[datascience]"
 
 ```bash
 nooa --help
-nooa start-dev            # launch the trace viewer
-nooa eval ...             # eval pipeline runner
-nooa traces ...           # inspect/manage trace files
+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:
+
+```bash
+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](https://github.com/NVIDIA-NeMo/labs-OO-Agents/blob/main/README.md) 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.

nooa_cli-0.0.10/README.md

@@ -0,0 +1,43 @@
+# nooa-cli
+
+CLI for [nemo-oo-agents](https://github.com/NVIDIA-NeMo/labs-OO-Agents). Ships the `nooa` command with subcommands for running evaluations, browsing traces, and managing config.
+
+## Install
+
+```bash
+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
+
+```bash
+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:
+
+```bash
+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](https://github.com/NVIDIA-NeMo/labs-OO-Agents/blob/main/README.md) 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.

{nooa_cli-0.0.8 → nooa_cli-0.0.10}/src/nooa_cli/AGENTS.md

@@ -101,6 +101,35 @@ def command(args: tuple[str, ...]):
     subprocess.run([sys.executable, "-m", "some_other_tool", *args])
 ```
 
+## Commands From Another Package
+
+If your command lives in a *different* installed package (not in this repo),
+register it in the `nooa_cli.commands` entry-point group instead of dropping a
+file here. The entry-point name becomes the subcommand name:
+
+```toml
+# pyproject.toml of your package
+[project.entry-points."nooa_cli.commands"]
+tui  = "my_package.cli.tui:command"
+term = "my_package.cli.term:command"
+```
+
+`my_package.cli.tui:command` must be a `click.Command` or `click.Group` — the
+same contract as an in-repo command module.
+
+- **Built-ins win name collisions.** A plugin can't shadow `eval`, `config`,
+  or anything else shipped here; it's logged and skipped.
+- **A broken plugin is skipped, not fatal.** An entry point that fails to
+  import, or that resolves to a non-`click.Command`, logs a warning and is
+  left out. `nooa` keeps working.
+- Plugins register in entry-point-name order, so `nooa --help` is stable
+  regardless of install order.
+- The **Performance Rule** below applies with extra force: every registered
+  entry point is loaded on *every* `nooa` invocation, including `nooa --help`.
+  Keep heavy imports inside the handler.
+
+This mirrors the existing `nooa.skills` and `nooa.bundled_configs` groups.
+
 ## Shared Utilities
 
 Common helpers live in `src/nooa_cli/_common.py`:

{nooa_cli-0.0.8 → nooa_cli-0.0.10}/src/nooa_cli/__init__.py

@@ -9,7 +9,10 @@ Usage:
     nooa completion install         # Set up shell completions
 
 Adding new commands:
-    Drop a .py file in nooa_cli/commands/ — see commands/_template.py
+    In this package: drop a .py file in nooa_cli/commands/ — see
+    commands/_template.py
+    From another package: register an entry point in the
+    "nooa_cli.commands" group — see nooa_cli/commands/__init__.py
 
 Shell completion:
     eval "$(_NOOA_COMPLETE=bash_source nooa)"    # bash
@@ -36,7 +39,8 @@ def oo(ctx):
     """OO Agents — agent toolkit.
 
     Extensible CLI for running agents, evaluations, and trace management.
-    Add new commands by dropping a .py file in nooa_cli/commands/.
+    Add new commands by dropping a .py file in nooa_cli/commands/, or from
+    another package via the "nooa_cli.commands" entry-point group.
     """
     if ctx.invoked_subcommand in _SKIP_SECRETS_PRELOAD:
         return
@@ -57,11 +61,14 @@ def oo(ctx):
         )
 
 
-# -- Auto-discover and register all commands from commands/ -----------------
+# -- Auto-discover and register all commands (built-ins + entry-point plugins) --
 for _name, _cmd in discover_commands():
     oo.add_command(_cmd, name=_name)
 
 # -- Built-in infrastructure commands (not in commands/ because they're meta) -
+# Registered *after* discovery on purpose: `completion` is not part of
+# discover_commands(), so this ordering is what stops a third-party plugin
+# named "completion" from taking the name.
 oo.add_command(completion)
 
 

nooa_cli-0.0.10/src/nooa_cli/coding/__init__.py

@@ -0,0 +1,32 @@
+# SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+"""Shared coding-agent components used by terminal and protocol hosts."""
+
+from nooa_cli.coding.activity import (
+    ActivityShellTools,
+    FileEdit,
+    TerminalCommandFinished,
+    TerminalCommandOutput,
+    TerminalCommandStarted,
+)
+from nooa_cli.coding.agent import CodingAgent
+from nooa_cli.coding.instructions import (
+    discover_agent_instruction_files,
+    render_agent_instructions,
+)
+from nooa_cli.coding.settings import load_coding_skills_dirs
+from nooa_cli.coding.slash_commands import CodingSlashCommand, CodingSlashCommandRegistry
+
+__all__ = [
+    "ActivityShellTools",
+    "CodingAgent",
+    "CodingSlashCommand",
+    "CodingSlashCommandRegistry",
+    "FileEdit",
+    "TerminalCommandFinished",
+    "TerminalCommandOutput",
+    "TerminalCommandStarted",
+    "discover_agent_instruction_files",
+    "load_coding_skills_dirs",
+    "render_agent_instructions",
+]