# Feature requests and enhancements

We love to hear your ideas.

Here are some guidelines for suggesting enhancements. They are designed to make it easier for the maintainers and the community to understand your proposal, which will make it more likely to be adopted.

## Requesting new features

Have an idea for improving Weaviate? We'd love to hear it! You can submit feature requests through either channel:

- **[GitHub Issues](https://github.com/weaviate/weaviate/labels/feature%20request)** - Create a feature request issue
- **[Community Forum](https://forum.weaviate.io/tag/feature-request)** - Start a discussion with the `feature-request` tag

When submitting a feature request, you should:

- **Check for duplicates** - Search existing requests to avoid duplicates
- **Be clear and specific** - Use a descriptive title and explain what the feature should do
- **Explain the value** - Why would this be useful to Weaviate users?
- **Provide examples** - Include code snippets, use cases, or mockups if helpful

## How to suggest enhancements

Suggestions are tracked as issues in GitHub repositories, such as the [Weaviate repository](https://github.com/weaviate/weaviate/issues). Check first for a duplicate WIP (work in progress) issue. If not, create an issue in the relevant GitHub repository with the following:

- **Use a clear and descriptive title**.
- **A specific and accurate description** of the suggested enhancement; include steps if necessary.
- **Specific examples(s)**. If possible, include code snippets in Markdown format.
- (If relevant) **Describe the current behavior** and then **explain how it would be altered**.
- (If relevant) **Include images, animated GIFs, or video links** in support.
- **Explain why this change would be useful** to Weaviate users.
- Specify which **version of Weaviate** you're using.

## Working on your own ideas

You are welcome to implement your own ideas and contribute code to Weaviate! We love to hear your ideas. Feel free to reach out to us and the wider community on the [forum](https://forum.weaviate.io) to discuss them before you get started.

If you want to implement your ideas, or do some work on the Weaviate code base, follow these [instructions](../weaviate-database/setup.md) to create a local development environment.

## Questions and feedback

Have a question or feedback? Here's how to reach us.

::::card-grid
:::card{title="Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions and connect with other developers on our **Community forum**.
:::

:::card{title="Support" href="/guides/support-overview" icon="life-buoy"}
Weaviate Cloud user or customer? Find the right channel on the **Support page**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.