Skip to content

Contribution

Thank you very much for your interest in Nexa, the Agent-Native programming language. Open source and community co-creation are the core driving forces for Nexa's continuous evolution and breaking the current AI "glue code" chaos!

✨ Core Contributors

The birth and evolution of Nexa would not be possible without the passionate developers and architects behind it. The current core research and development members of the language compiler and native execution engine:

  • Ouyang Yipeng —— Nexa core architect, compiler underlying research and development design, and main creator of the native coroutine execution engine (Runtime).

As the framework boundaries continue to expand, whether you're a底层 geek or an upper-level application hacker, we eagerly look forward to seeing more names appear on this glittering list of contributors in the future!

🤝 How to Contribute?

Whether you want to optimize the underlying regex inference of the parser, provide hardcore concurrent performance stress test reports, connect a groundbreaking general tool wrapper, or just fix a typo in the official documentation, all your contributions are as precious as gold at this early stage.

1. Submit Issues for Discussion and Feedback

If you discover a bug with engine deadlock errors, or have a brilliant feature idea for refactoring syntax (such as a more elegant concurrent pipeline blocking design), please don't hesitate to open an Issue on the project GitHub homepage immediately.

If it involves core keyword modifications to protocol or match intent, we will initiate public GitHub Discussions for discussion and voting.

2. Fork & Pull Request to Participate in Core Building

If you're ready to get your hands dirty and dive into the engine compartment:

  1. Fork the official repository and Clone to your local experimental area.
  2. Check out a semantically clear branch (e.g., feature/lsp-support, bugfix/dag-traverse).
  3. Implement code, insist on and pass (Test Driven Development) unit test cases.
  4. Provide solid and detailed Commit Messages and initiate an upstream Pull Request (PR) from your personal branch.

We will conduct rigorous, pure, and geeky-fun code review discussions!

3. Expand the Standard Library stdlib and Ecosystem Wrappers nxm

If you're not interested in the compiler's underlying Abstract Syntax Tree (AST), you can still make great contributions by writing good external tool wrappers! Standardize and encapsulate high-quality scenario tools you've debugged in Python daily (such as crawler aggregation, knowledge base vector connections, etc.) and merge them into Nexa runtime's underlying runtime/stdlib.py, and you'll directly benefit millions of users.

4. Leave Your Footprints

No need to create new web pages; every page footer of this documentation seamlessly connects to our Discussions on GitHub. If you have any complaints or questions, feel free to scroll to the bottom of the page and leave a comment as easily as sending a bullet screen message.


Let's reinvent the execution layer natively, together! *Come join us and build this modern software engineering revolution belonging to Agent-Native!

快来问问agent吧!

Nexa Agent

Nexa 文档助手

我是Nexa文档AI助手,可以问我有关文档的一切!

由AI Hub提供支持