Nexus Weekly Update: Observability, Smarter Tooling, and Model Auth Fixes (Apr 6–12)
This week was about making Nexus more trustworthy under the hood — fewer silent failures, smarter model routing, and the foundation for the blog you're reading right now.
✨ What's New
Error Handling Overhaul
We audited the entire codebase and fixed 23 instances of silent failures — bugs that fail quietly and leave you guessing what went wrong. We introduced a parseJsonResponseSafe utility (a helper that safely reads AI responses without crashing), enforced structured error logging across all critical paths, and added automated rules to block empty error handlers at commit time. You'll see fewer mystery errors and much faster diagnosis when something does go wrong.
Pre-Commit Hooks via Husky + lint-staged
We wired up pre-commit hooks — automated checks that run before any code can land in the codebase. ESLint (our code quality enforcer) now runs at the source, blocking bad patterns before they ever reach the repo. No more accidentally shipping empty error handlers or skipping code review. Quality is now enforced, not hoped for.
nexus_delete_automation Tool
Automations can now be deleted directly from the Nexus chat interface or backend API. This closes the last gap in the automation lifecycle — you can now create, update, pause, and delete, completing the full management loop.
list_commits Action for GitHub Tool
The GitHub integration now supports pulling commit history with optional filters by author, date range, and repo. This is the exact capability powering the weekly blog automation you're reading right now — idea → commits → article, fully automated.
Business Snapshot View + SQL Migration
We added a new database view called nexus_business_snapshots — think of it as a clean, always-updated summary of your business data that the AI can read quickly and reliably, replacing slower one-off queries. Paired with new unit tests to lock in the behavior going forward.
robots.txt for SEO + LLM Guidance
Added a robots.txt file to the landing app — a standard web file that tells search engines and AI agents how to crawl the site. A small but meaningful step toward discoverability as Nexus grows its web presence.
Enhanced Landing Page
The landing page got a content pass to better communicate Nexus's value proposition, alongside a new end-to-end test script for the GitHub API integration.
🔧 What We Fixed
OpenRouter OAuth Callback
Consolidated the API key exchange logic in the OpenRouter OAuth callback. OpenRouter is the service that routes AI model requests — previously the handoff logic was spread across multiple code paths, now it's clean and predictable.
OpenClaw Model Auth + JIT Sync
Two targeted fixes to how Nexus selects and authenticates AI models. Auth checks now correctly account for just-in-time token sync (credentials fetched on-demand rather than cached ahead of time), and model settings properly propagate even when the key sync is cached. This resolves edge cases where the wrong model was silently selected.
Auto-Skip Models Over 128-Tool Limit
Nexus now has 137 registered tools. Some AI models cap at 128 tools per session — meaning they can't handle Nexus's full catalog. The router now automatically skips incompatible models rather than erroring out, keeping your sessions uninterrupted as the tool catalog grows.
♻️ Under the Hood
A few improvements that make the platform easier to maintain and extend:
The ConnectionsAPISection tab logic was simplified — fewer moving parts, same behavior, easier to maintain going forward. The Automation Scheduler now surfaces clearer error logs during idle periods, so slow or stuck runs are easier to diagnose. Module resolution was cleaned up and unused props removed, improving attachment preview accessibility. The client tsconfig (TypeScript configuration file) was updated to align with current module conventions, preventing subtle build inconsistencies down the line.
What This Means for You
This week's work is foundational. Better error visibility means fewer mystery failures and faster fixes when something goes wrong. Pre-commit hooks mean the codebase stays clean as we grow. The model compatibility fixes mean Nexus stays reliable as we keep expanding what it can do. And the list_commits tool? That's what made this article possible — a direct line from code to published content, automated end-to-end.
The platform is getting sharper — and it's showing.
Want early access or have a feature request? Reach out to the Marcoby team — we build with our customers.
At Marcoby, You're Technically Family.