Welcome to the Nexus Framework! (Here is how we start)

[sangalo20]

Welcome, everyone!

For a while, the vision of a zero-trust, provider-agnostic integration layer for autonomous agents has been living in the foundational white paper on Zenodo. The core engine—the Go Broker, Gateway, and Bridge—is now built, stable, and live.

Now, it’s time to expand the ecosystem.

Our immediate goal is to make Nexus plug-and-play for the broader agentic AI space. We want developers building custom agents, or working with memory OS systems like Athena and autonomous architectures like OpenClaw, to be able to hook into our identity orchestration instantly, without rewriting integration logic.

Where We Need Your Help Right Now:
The core Go stack is solid, but to achieve mass adoption, we need to meet developers where they are. I have just opened up three major initiatives on the Issue Board, and they are up for grabs:

1. The MCP Server Adapter: This is the killer app. We need an adapter that translates Nexus connections into standardized Model Context Protocol (MCP) Tools, allowing any MCP-compliant agent to securely access external APIs through Nexus.
2. The nexus-sidecar Proxy: This is our zero-trust security mesh. Instead of chasing the endless treadmill of building SDKs for Python, Node, and Rust, we are building a standalone Go proxy. Agents in any language can just make standard, unauthenticated HTTP requests to this local sidecar. The sidecar intercepts the request, securely fetches the right token from the Nexus Gateway, signs it, and forwards it to the provider. Most importantly, this creates a Zero-Knowledge architecture: the AI agent itself never holds raw API tokens in its memory, completely neutralizing token exfiltration risks if an agent is compromised via prompt injection.

How to Get Started Today:

• Pull down the nexus-framework repo.

• Follow the Quickstart in the README.md (run docker-compose up -d).

• Head over to the Issues tab and look for the good first issue or help wanted tags.

• Claim an issue: Just drop a comment on the issue saying "I'll take this!" so we don't duplicate work.

Communication:
We will use this Discussions tab as our async headquarters. If you hit a wall getting the Docker stack running, or if you want to propose an architecture change for the SDKs, open a thread here in Discussions. If you find a reproducible bug, open an Issue.

Let’s build the standard for agent identity. Grab an issue, and let me know where you get stuck!

[sangalo20]

@ashioyajotham Is there any issue you are particularly interested in?

[ashioyajotham]

@sangalo20 I have a bunch like issue 26 (I was working on it for a while just submitted a PR). I think I will go to 29 next!

[sangalo20]

Cool! let review the PR in a few