---
title: "Get help and contribute"
description: "Report a reproducible problem or contribute a focused fix."
---

# Get help and contribute

For a reproducible bug, use the [issue templates](https://github.com/vstorm-co/agenticos/issues/new/choose). Search existing issues first. Include the release or commit, deployment type, relevant model and tool configuration, expected result, actual result and a minimal synthetic input.

Do not include credentials or private documents. For a suspected vulnerability, follow the private reporting instructions in [SECURITY.md](https://github.com/vstorm-co/agenticos/blob/main/SECURITY.md), rather than opening a public reproduction.

## Before reporting an installation problem

Check [installation](install.md) and the selected [deployment configuration](deployment.md). Record the command that failed and a redacted error. For a document answer, check source processing, collection binding and permissions. For a tool failure, preserve the tool error and run status. A connection probe is not proof that the task completed.

## Contribute or scope implementation help

Read [CONTRIBUTING.md](https://github.com/vstorm-co/agenticos/blob/main/CONTRIBUTING.md), [architecture](architecture.md) and the relevant how-to before changing behavior. A focused documentation fix or a reproducible issue is a useful contribution. Coordinate larger changes with maintainers through the repository.

For deployment in your infrastructure, documentation, process creation or custom development, contact [Vstorm](https://vstorm.co/) or Kacper. Support commitments are scoped separately. Community issue reporting is not a contracted response SLA.