RELEASE·NEXUS
Nexus 0.2.3: A Proper Architecture, Full Observability, and SDKs for Every Agent Runtime
Nexus 0.2.3 is the most substantive release since launch. A formal service layer replaces the monolithic handler, five new Prometheus metrics cover every credential operation, critical Broker bugs are fixed, and three first-class SDKs with native MCP support ship for Go, Python, and TypeScript.
May 14, 202613 min read
RELEASE·JARVISCORE
JarvisCore 1.1.0: Agents That Know What They Are Doing
From P2P keepalive spam to hallucinated imports, building production agents on JarvisCore 1.0.x meant working around problems you shouldn't have had. 1.1.0 changes that. Here is the full story.
May 12, 202611 min read
BLOG·NEXUS
Security-as-Code: Why We Treat Provider Configuration Like Infrastructure Code
The Nexus Broker holds refresh tokens and API keys for every provider in your workspace. Before nexus-cli, the only way to change that state was an ad-hoc API call with no review, no diff, and no record. Here is why that mattered and what we built instead.
May 5, 20269 min read
RELEASE·NEXUS
Nexus 0.1.5: Bridge and Broker Stability Fixes
Nexus 0.1.5 replaces goto-based retry logic in the Bridge, fixes a partial-write race in the Broker's streaming encoder, and resolves NULL panics for non-OAuth2 provider profiles.
Apr 13, 20267 min read
BLOG·NEXUS
Connecting Salesforce: skip_scope_on_auth and What We Learned
Nexus 0.1.4 adds skip_scope_on_auth for providers like Salesforce that reject scope parameters on the OAuth authorization URL. Here is why the fix was needed and how to use it.
Apr 1, 20266 min read
RELEASE·JARVISCORE
JarvisCore 1.0.2: P2P Keepalive Backoff and Remote Agent Discovery
JarvisCore 1.0.2 fixes two P2P reliability issues: continuous keepalive spam when peers are unreachable, and list_roles() missing agents discovered via SWIM.
Mar 4, 20269 min read
RELEASE·JARVISCORE
JarvisCore 1.0.0: An Open Source Multi-Agent Framework Built for What Agents Actually Do
JarvisCore is now open source under Apache 2.0. This is the story of why we built it, what we believe about multi-agent systems, and five things we did differently.
Feb 25, 202612 min read
COMMUNITY·JARVISCORE
Community Spotlight: A Financial Intelligence Pipeline in 344 Lines
How a team built a three-agent market data pipeline on JarvisCore — fetch, analyse, report — with crash recovery, episodic memory, and a Markdown briefing saved to blob storage on every run.
Feb 18, 20267 min read