--- headline: Contribution Overview | Opik Documentation og:description: Contribute to Opik by submitting bug reports, suggesting features, or improving documentation to enhance the project for everyone. og:site_name: Opik Documentation og:title: Contributing to Opik - Join Our Open Source Community title: Contribution Overview canonical-url: https://www.comet.com/docs/opik/contributing/overview --- # Contributing to Opik We're excited that you're interested in contributing to Opik! There are many ways to contribute, from writing code to improving the documentation, or even helping us with developer tooling. ## How You Can Help Help us improve by submitting bug reports and suggesting new features. Improve our guides, tutorials, and reference materials. Set up your local Opik development environment with Docker, local processes, or manual setup. Enhance our Python library for Opik. Help improve our TypeScript library for Opik. Work on our agent optimization tools. Develop new features and UI improvements for the Opik web application. Work on the core Java services powering Opik. The bounty program is currently paused. Check status updates here. Speak or write about Opik and share your experiences. Let us know on [Comet Chat](https://chat.comet.com)! Also, consider reviewing our [Contributor License Agreement (CLA)](https://github.com/comet-ml/opik/blob/main/CLA.md). ## Submitting a new issue or feature request This is a vital way to help us improve Opik! Before submitting a new issue, please check the [existing issues](https://github.com/comet-ml/opik/issues) to avoid duplicates. To help us understand the issue you're experiencing, please provide: 1. Clear steps to reproduce the issue. 2. A minimal code snippet that reproduces the issue, if applicable. This helps us diagnose the issue and fix it more quickly. Feature requests are welcome! To help us understand the feature you'd like to see, please provide: 1. A short description of the motivation behind this request. 2. A detailed description of the feature you'd like to see, including any code snippets if applicable. If you are in a position to submit a PR for the feature, feel free to open a PR! ## Project Setup and Architecture Opik is a monorepo with multiple services and SDKs. Common contributor entry points are: - `apps/opik-backend`: Core Java backend API/services - `apps/opik-frontend`: React frontend application - `apps/opik-documentation`: Documentation website and docs source - `apps/opik-guardrails-backend`, `apps/opik-python-backend`, `apps/opik-sandbox-executor-python`: supporting backends and runtime services - `sdks/python`, `sdks/typescript`, `sdks/opik_optimizer`: SDKs and optimizer tooling - `tests_end_to_end`: E2E suites and helper services Opik relies on: ClickHouse (traces, spans, feedback), MySQL (metadata), and Redis (caching). The local development environment uses convenient scripts (`./opik.sh` for Linux/Mac, `.\opik.ps1` for Windows) that manage Docker Compose automatically. Please see instructions in the [deployment/docker-compose/README.md](https://github.com/comet-ml/opik/blob/main/deployment/docker-compose/README.md) on GitHub for advanced usage. ## Developer Tooling & AI Assistance To help AI assistants (like Cursor) better understand our codebase, we provide context files: - **General Context**: [`https://www.comet.com/docs/opik/llms.txt`](https://www.comet.com/docs/opik/llms.txt) - Provides a general overview suitable for most queries. - **Full Context**: [`https://www.comet.com/docs/opik/llms-full.txt`](https://www.comet.com/docs/opik/llms-full.txt) - Offers a more comprehensive context for in-depth assistance. You can point your AI tools to these URLs to provide them with relevant information about Opik. ## AI-Assisted Contributions (Required Disclosure) AI assistance and authorship is allowed. Human authors remain fully accountable for correctness, licensing, and security. Rules: - Always run relevant tests/linters for touched code. - Always be explicit about human/users interaction with produced output. - Always review prior issue, pull-requests and code-base for existing solutions. - Always address any system generated reviews (Baz, Greptile). - Never submit unreviewed AI output. - Never include secrets, tokens, private prompts, internal system instructions, or customer-sensitive data in generated/public content. - Never disclose vulnerabilities, exploit steps, or incident details in public issues/PRs. Use private maintainer/security channels. - You must ensure every PR include an AI disclosure watermark block in the PR description: If AI is used, include a brief `## AI Assistance` note in the PR description with tool/model, scope, and confirmed human verification (if any); if no AI is used, omit that section entirely. _Review our [Contributor License Agreement (CLA)](https://github.com/comet-ml/opik/blob/main/CLA.md) if you haven't already._ _Comment on [popular feature requests](https://github.com/comet-ml/opik/issues?q=is%3Aissue+is%3Aopen+label%3A%22feature+request%22) to show your support._