Repository navigation
Releases
Releases · sepehrtaji-dev/Nova-agent
Nova 2.3 — Agentic Tool Loop, NoviqX GitHub App (MCP) & Setup Wizard
Nova 2.3 — Agentic Tool Loop, NoviqX GitHub App (MCP) & Setup Wizard 🚀
The biggest release yet: Nova can now act autonomously with tools, connect to GitHub through your own NoviqX GitHub App (MCP server included), and remembers your conversation properly.
✨ Highlights
- 🔁 Agentic tool loop — Nova drives tools through a native tool-calling loop in the main UI, chaining multiple calls autonomously until the task is done.
- 🔌 NoviqX GitHub App (MCP) — bring-your-own-App: MCP server, registry tools, RS256 JWT → installation-token auth chain (cached, auto-refreshed on 401), and SHA-locked writes with optimistic locking. Your
.pemprivate key never leaves your disk — settings store only IDs and its path. - 🧙 First-run setup wizard — on launch, if NoviqX isn't configured, a 4-step wizard walks you through: intro → create your own GitHub App → credentials with live validation → a real connection test. Includes a "Never show this again" button (also in Settings → NoviqX GitHub App…).
- 👀 Live activity indicator — a tiny chip above the message composer now shows what Nova is doing in human words: Thinking → Searching the web / Reading the file / Writing the file / Running the command / Asking GitHub → Writing, with a pulsing dot and animated ellipsis, instead of an opaque wait (PR #53)
- 🧠 Conversation memory fix — short-term history is now sent as real alternating user/assistant turns (12-message / 6,000-character budget), so follow-ups like "does this have applications in AI?" correctly resolve "this" to the previous topic.
🛠 Fixes
- Build refresh — NO_PROXY now applied before the Ollama client is built (PR #56) — the previous fix patched
NO_PROXYafterimport ollama, but the ollama package constructs its default httpx client eagerly at import time, baking the proxy mounts from the environment — so the loopback exemption never reached real requests. That is why the VPN stayed fatal in both states: VPN on → the live proxy answered the loopback request with the empty-body 503; VPN off → staleHTTP_PROXYvariables (e.g. viasetx) sent the request to the dead proxy port asConnectError: [WinError 10061]. The patch now runs before the import and any pre-built client is rebuilt under the patched environment — proven by an end-to-end subprocess test (fresh interpreter, dead proxy, fake loopback Ollama; plain and streaming chat succeed) plus a negative control reproducing the old failure. Connection-refused failures now also get a targeted message (check Ollama is running; clear leftoverHTTP_PROXY/HTTPS_PROXYvariables). - Local model 503 — root cause fixed: system proxy intercepting localhost (PR #55) — the surviving 503s had an empty error body, which Ollama never produces; they came from a middlebox. The Ollama Python client (httpx) routes even
http://localhost:11434throughHTTP_PROXY/HTTPS_PROXYwith no loopback exception — unlike the Go client the Ollama CLI uses — so VPN/proxy tools answered Nova with a bare 503 whileollama runworked in the same terminal. Nova now addslocalhost,127.0.0.1,::1toNO_PROXYat startup (your own entries are preserved; remote providers keep using the proxy), retries transient 5xx up to 6 times (~31s, enough for cold model loads), and the failure message points at the proxy whenever the 503 body is empty. - Local model 503 fix (PR #54) — with a local Ollama model, conversations could abort with “the tool interaction failed: ResponseError (status code: 503)” whenever the model was still loading or every runner was busy. Ollama chat calls now retry transient 5xx errors with backoff (1s → 2s → 4s, tunable via
NOVA_OLLAMA_RETRIES, default 4 attempts) across all four brain paths; streaming turns retry only before the first token so nothing on screen is duplicated. If the server still does not recover, Nova explains the cause and suggestsollama psinstead of dumping the raw error. - Empty tool registries no longer mute the assistant — greetings and ordinary chat answer normally even when tools are unavailable, and tool-dependent requests get the cause and remedy instead of a canned line (PR #52)
- Wizard layout breaking from step 3 onward (widgets now cleared immediately on step change)
- Streaming-protocol floods in the UI + hardened entry points (PR #50)
- Security hardening of tool execution (PR #48)
- Major logic fixes across agent core, model providers and memory (PR #49)
- Math parser: superscript minus (
e⁻ˣ), inline-code spacing - Anthropic Messages API as a first-class remote backend (
NOVA_API_PROVIDER=anthropic) — now documented in README and docs/remote-providers.md
✅ Quality
- 468 tests passing, 5 skipped — incl. 12 NoviqX settings/security tests, 5 conversation-history regression tests, 9 tool-activity status tests and 21 Ollama transient-503/proxy-bypass tests (with an end-to-end dead-proxy probe)
- Real-integration smoke test:
scripts/noviqx_smoke_test.py(JWT → token → repo metadata → SHA-locked write round-trip)
📦 Getting started
git clone https://github.com/sepehrtaji-dev/Nova-agent.git
cd Nova-agent
pip install -r requirements.txt
python App.pyIf NoviqX isn't configured yet, the setup wizard appears on launch — or skip it with "Never show this again".
See the README for the full NoviqX walkthrough.
Full changelog: CHANGELOG.md
