Chat2DB Community: Start here

[openai0229]

Chat2DB Community uses this pinned issue as the single starting point for reporting problems, contributing changes, and joining active design work. Detailed rules live in the version-controlled repository documentation linked below.

Report a problem or request a change

What you need	Where to go
A reproducible Chat2DB problem	Bug report
A database-specific connection, metadata, SQL, or editor problem	Database compatibility bug
A concrete product improvement	Feature request
A documentation correction or addition	Documentation task
Installation, configuration, or usage help	Q&A Discussions
An early idea or workflow to explore	Ideas Discussions
A security vulnerability	Follow SECURITY.md and do not post details publicly

You can also start from the Issue chooser. Before submitting, search existing Issues and Discussions, use the latest applicable version or provide a source commit, keep one actionable problem per Issue, and remove secrets or private data. See the Issue triage guide for the evidence maintainers need.

Contribute

• Read CONTRIBUTING.md.
• Browse Good First Issues and Help Wanted.
• Claim a published contribution task with /claim and follow the finding and claiming work contract.
• Share verified workflows and integration results in Show and tell.

Open a dedicated Issue or Discussion for concrete work instead of using comments on this navigation Issue.

Active community feature initiatives

Parent Issues organize related Community feature work while keeping each deliverable available as an independently claimable leaf Feature Issue. Open the parent for the complete feature registry, then claim only a linked leaf Issue that is in Project status Ready and has a contribution/* label.

Initiative	Parent Issue	Focus
MySQL Community feature support	#2567 - MySQL Community feature support and contribution plan	Complete MySQL product capabilities organized as native, individually claimable Feature sub-issues.

Active design discussions

Each active design Discussion has one open Tracking Issue:

• The Tracking Issue owns the user problem, scope, priority, acceptance criteria, and implementation tracking.
• The Discussion owns unresolved design questions, alternatives, and decision records.

Discussion	Tracking Issue	Focus
#2565 - Evolve built-in AI from chat into a task-oriented Agent Runtime	#2566 - Evolve built-in AI from chat into a task-oriented Agent Runtime	Task-first execution, pluggable runtimes, lifecycle state, approvals, resumable event streams, artifacts, scheduling, and auditable database operations.
#2412 - How should Chat2DB integrate Codex and ChatGPT subscription access?	#2413 - Use ChatGPT/Codex subscription access in Chat2DB Community	Product, runtime, authentication, model, delivery, database-tool, state-ownership, and release boundaries for a Codex provider.
#2256 - Redesign SQL editor AI interaction and result workflow	#2255 - Redesign the SQL editor AI interaction and result workflow	The interaction model between the SQL editor, AI assistance, execution, and result presentation.
#1944 - Move result-grid query composition into database plugins	#1911 - Move result-grid query composition into database plugins	Database-specific ownership of result-grid query composition.
#1941 - Deliver large AI tool results through previews and retrievable local artifacts	#1942 - Deliver large AI tool results through previews and controlled retrieval	Preview, completeness, retention, and controlled retrieval contracts for large AI tool outputs.

This list is a navigation index, not a roadmap or delivery commitment. Keep an entry only while its Discussion and Tracking Issue remain active.

[openai0229]

The maintained contributor entry point now lives in CONTRIBUTING.md, the Community Project, contributor-ready label queries, and .github/COMMUNITY_OPERATIONS.md from #1939. Closing this standalone guide so contribution rules stay in version-controlled repository documentation.

[Shubh2-0]

i'm a backend dev looking to help out with postgres integration and performance. i'd love to take on optimizing schema metadata fetching using a redis caching layer and tuning spring boot connection pool timeouts.

[openai0229]

@Shubh2-0 Thanks for offering to help. Please open a separate issue using the appropriate issue template and clearly describe the current problem, including the existing behavior and impact, reproducible steps and environment, and any baseline or profiling data that shows the bottleneck.

Please also explain the proposed scope and why Redis caching or HikariCP tuning is appropriate for the reported problem. Once the task is clearly defined, you can create a focused pull request and link it to the new issue with Closes #<issue-number>.

Please use the new issue, rather than this contributor guide, to track the implementation.