Community Hub

Nestor is a small, friendly open-source project. Whether you're filing your first issue, sending a PR, or just lurking — you're welcome here. Here's how to get involved.

💬

GitHub Discussions

Questions, ideas, show-and-tell, and longer-form conversations. Best for "how do I…?" and "should we add…?".

Join the discussion → 🐛

Issue Tracker

Bug reports and feature requests. Please run npx nestor-sh doctor first and paste the output.

Browse issues → 🔀

Pull Requests

Code contributions, doc fixes, examples. Small PRs are easier to review and ship — split big work into stages.

Open PRs → 📘

Contributing Guide

How to set up the dev environment, run tests, write commits, and ship your first patch.

Read the guide → 🛡️

Security Disclosures

Please report vulnerabilities privately via GitHub Security Advisories — not in public issues. PGP key on request.

Disclosure policy → 📜

MIT License

Free to use, modify, redistribute. Commercial-friendly. No CLA required for contributions.

View license → 🚀

Releases

Every release with detailed change notes. Subscribe via the RSS feed or the changelog page.

Browse releases → 🤝

Code of Conduct

Be kind, assume good faith, focus on the work. We follow the Contributor Covenant 2.1.

Read the code →

Your first contribution

The most useful first contributions are usually small and obvious: typo fixes, doc clarifications, missing examples. Here's the workflow we recommend.

1. Fork & clone

git clone https://github.com/<your-handle>/nestor.git
cd nestor
corepack enable
corepack pnpm install

2. Build & test the workspace you'll touch

corepack pnpm --filter @nestor/db build
corepack pnpm --filter @nestor/db test

3. Make your change on a branch

git checkout -b fix/typo-in-quickstart
# edit files
corepack pnpm -r build      # verify nothing else breaks
corepack pnpm -r test

4. Commit & open a PR

git commit -m "docs: fix typo in quickstart wizard step"
git push origin fix/typo-in-quickstart

Open the PR against main. Describe why the change matters — the diff already shows what.

That's it. There's no CLA, no Slack-only review channel, no waiting on a single maintainer. Issues and PRs are triaged within a week.

Where to start if you want to write code

Good first-contribution areas, ranked by independence (you can ship without coordinating with others):

  1. Documentation — fix typos, add missing examples, expand the troubleshooting page. website/docs/ is plain HTML.
  2. Skill translators — translate a popular LangChain or CrewAI tool into a Nestor skill. packages/skill-translator/
  3. New LLM adapters — add support for a provider Nestor doesn't yet ship (e.g. Cohere, Together, Replicate). packages/agent/src/llm/
  4. Built-in tools — extend packages/agent/src/tools/builtin.ts with a tool you want Nestor to have.
  5. Studio UI — React components in packages/ui/src/. Vite + Tailwind, no exotic stack.
  6. Hard infrastructure — schema migrations, runtime refactors, security core in Rust. Coordinate first via Discussions.

Reporting a bug well

We can fix bugs much faster when reports include:

If you can isolate a reproduction in a fresh NESTOR_HOME=~/.nestor-debug, even better.

🌟 Contributor recognition

Every merged PR appears in the next CHANGELOG entry. Major contributors get a permanent shout-out on the README and (when the hosted tiers launch) a free Solo Pro account. We don't have stickers yet — but we will.

Stay in the loop