Open Source · MIT Licensed

Build Astra with us.

Astra is written and maintained in the open. Whether you fix a typo in the docs or add a feature to the C++ core, every contribution moves the language forward.

↗ View on GitHub Browse Open Issues

Ways to Help

Pick where you fit in.

You don't need to touch the C++ core to contribute — docs, tests, and bug reports matter just as much.

🔧

Core Engine (C++)

Astra's interpreter is written in C++. Fix bugs, improve performance, or implement new language features in the core VM.

C++

📖

Documentation

Improve the docs you're reading right now — fix typos, clarify explanations, or write new guides and examples.

Next.js

🐛

Bug Reports

Found something that doesn't work as expected? File a detailed issue with a minimal .astra file that reproduces it.

No code needed

⚡

Power Modules

Write a .power module in C++ to extend Astra — new math functions, string utilities, or entirely new capabilities.

C++

💡

Language Ideas

Propose new syntax or features by opening a discussion. Explain the problem it solves with a concrete example.

Discussion

🧪

Testing

Write test cases for the interpreter, or stress-test edge cases in chains, modifiers, and error handling.

C++ / Astra

Getting Started

From fork to pull request.

Five steps to get your first change merged into Astra.

Fork & Clone

Fork the repository on GitHub, then clone your fork locally.

git clone https://github.com/YOUR-USERNAME/astra.git
cd astra

Build from Source

Astra is built with CMake. Compile the interpreter locally before making changes.

mkdir build && cd build
cmake ..
make

Create a Branch

Name your branch after what it does — keep main clean for your fork.

git checkout -b fix/division-by-zero-message

Make Your Change

Keep commits focused. One fix or feature per pull request is easier to review and merge.

# edit source files
git add .
git commit -m "Fix: clarify DIVISION_BY_ZERO error message"

Open a Pull Request

Push your branch and open a PR against the main repo. Describe what changed and why.

git push origin fix/division-by-zero-message

Before You Submit

Pull request guidelines.

A few conventions that make review faster for everyone.

Keep pull requests focused — one logical change per PR.
Match the existing code style in the file you're editing.
Add a .astra test file for new language features when possible.
Update relevant docs pages if your change affects behavior.
Write clear commit messages that explain the "why," not just the "what."

New to Astra's codebase?

Look for issues labeled good-first-issue — they're scoped for first-time contributors.

Find an Issue →