The real Textual interface, captured from a deterministic Noah Code session.
Noah keeps the conversation central while the context rail tracks live work, Git changes, session, model usage, and the current plan. Tool execution stays visible, completed work compacts into readable records, and every session remains scoped to its repository.
Built on the NVIDIA OO Agents (NOOA) runtime.
Install
Install Noah Code and its managed Python runtime with one command:
curl -LsSf https://raw.githubusercontent.com/skundu42/noah-code/main/install.sh | sh
Open a new terminal, move into a repository, and start Noah:
cd your-project
noah .
Noah is compatible with macOS on Apple Silicon and Intel, plus Linux on arm64 and x86_64.
On the first launch, the TUI walks through provider, API key, model, and reasoning setup. Keys are stored in Noah's private auth file with owner-only permissions; they are never written to project configuration or session history.
Why Noah
- Repository-aware exploration. Search with ripgrep, inspect Git history and diffs, navigate symbols through language servers, and use an mtime-cached repository map.
- Controlled edits. Apply anchored replacements or atomic multi-file patches with exact preimages, concurrent-change detection, immediate diagnostics, and rollback.
- Visible execution. Stream bounded shell output while commands run, keep servers and watchers
as managed background jobs, and revisit activity details with
F2. - Recoverable work. Review staged and unstaged changes in
/diff, then undo or redo journaled file edits even after restarting Noah. - Persistent sessions. Resume repository-scoped conversations, todos, model choices, and automatically compacted context without losing the full underlying tool results.
- Token-efficient by construction. Lean tool-output bounds with disk-backed recall, condensed
subagent results, cache-stable request prefixes (volatile status arrives as appended events),
and pointer-eviction compaction — measured live with
/tokens. - Explicit control. Switch between implementation-focused build mode and read-only
plan mode, with ordered
allow,ask, anddenypermission rules. - Extensible workflows. Add slash commands, opt-in skills, MCP servers, or markdown subagents;
attach
@filesand images when the task needs more context.
Noah follows repository instructions from AGENTS.md, CLAUDE.md, and
.noah-code/instructions.md.
Quick start
Describe the outcome you want rather than prescribing every edit:
Find the cause of the failing parser tests, implement the smallest safe fix, and run the
focused test file.
Useful launch modes:
# Open another workspace
noah /path/to/repository
# Inspect and plan without editing
noah --mode plan .
# Run one task and exit
noah run "Explain how authentication is wired" .
# Allow actions that would normally ask; explicit deny rules still apply
noah run --auto "Fix the failing unit test" .
# Resume previous work
noah --continue .
noah --session SESSION_ID .
# Use the line-oriented interface
noah --console .
Check the installation and resolved configuration with:
noah --version
noah doctor .
noah config show .
noah update --check
The package also installs noah-code and nc as equivalent entry points. Because nc commonly
means netcat, noah or noah-code is recommended.
Inside the TUI
Type / to search the full command and configuration reference. The most common controls are:
| Control | Action |
|---|---|
Enter |
Send the current prompt or accept a selected suggestion |
Shift+Enter |
Insert a newline |
Tab |
Switch between build and plan mode |
F2 |
Open execution activity |
F3 |
Open paginated conversation history |
/model |
Configure a provider or switch the session model |
/theme |
Choose Atom One Dark, Noah Ocean, Graphite, or High Contrast |
/diff |
Review staged and unstaged changes |
/undo / /redo |
Traverse the persistent edit journal |
/tokens |
Inspect tokens, cache usage, prefix stability, model wait, and tool output |
/efficiency |
Switch between fast, balanced, and deep budgets |
On wide terminals, the side rail prioritizes the active operation, Git branch and change counts, session, model usage, update state, and plan. Git status is refreshed in the background at turn boundaries, so the animated working state stays responsive. The main pane remains centered on the Noah mark until the first prompt, then becomes the conversation and execution timeline.
Models and providers
Noah supports OpenAI, Anthropic, OpenRouter, NVIDIA, and custom OpenAI-compatible providers. It also works with vLLM, LM Studio, Ollama, Azure OpenAI, Bedrock, Gemini, Groq, Mistral, xAI, DeepSeek, Together AI, and Perplexity.
The guided /model flow is the easiest way to configure a provider. Environment variables and
the CLI remain available for scripts and headless environments:
export OPENAI_API_KEY="..." # or ANTHROPIC_API_KEY / OPENROUTER_API_KEY
noah providers list
noah providers add openai --model MODEL_NAME
noah .
/model MODEL changes only the current session and remembers that choice when resumed. Use
/model --global MODEL to set the default for future sessions in every repository.
For compatible reasoning models, choose default, none, minimal, low, medium, high, or
xhigh. default omits the provider parameter:
noah --model openai/MODEL --reasoning-effort high .
See the provider configuration guide for gateway-specific setup.
Updates
Noah checks PyPI for new versions at most once every 24 hours. New TUI sessions show a temporary banner when an update is available and keep the version visible in the context rail. Installation remains explicit by default:
noah update --check
noah update
Documentation
- Interactive interface and sessions
- Configuration, modes, permissions, and updates
- Generated-code security
- Custom commands, skills, MCP, and tracing
- Development, CI, and releases
- Release notes
Development
uv sync --extra dev --extra mcp --extra tracing
uv run ruff check src tests
uv run pytest tests
uv build
See the development guide for platform checks and the release process.
License
Apache-2.0. NOOA remains separately licensed by its upstream project.
Credits
Built on NVIDIA OO Agents (NOOA). Thanks to the NVIDIA NeMo team and NOOA contributors for the agent runtime that powers Noah Code.
Release files for noah-code 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| noah_code-0.2.3.tar.gz | 357.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| noah_code-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 553.0 kB
Release files / noah_code-0.2.3.tar.gz
| Download URL | noah_code-0.2.3.tar.gz |
|---|---|
| Size | 357.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fc38445f4ea52ac10282d09b47709fc3466ef0a583fd73d83e3bce4f8a4cf8f
|
|
BLAKE2b-256 checksum How to use checksums |
32dd37a76e452d721386d3204d1c7227c63b5f7fb52559f25473a939b4df5acd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / noah_code-0.2.3-py3-none-any.whl
| Download URL | noah_code-0.2.3-py3-none-any.whl |
|---|---|
| Size | 195.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26878fe2b7adb0ec0e90509f5138f30ed94735e1b42e12dec56d63e13555021e
|
|
BLAKE2b-256 checksum How to use checksums |
1e71ca4242d8712a31130bd984446bbe15b5bb704933185f672eaad89dcfb9eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency log