# Getting help

## Found a bug or missing behavior?

Open an issue on the repository:
[github.com/agustinusnathaniel/klyro/issues](https://github.com/agustinusnathaniel/klyro/issues).

To make an issue actionable, include:

- the command you ran and its exit code (see the
  [exit-code table](/cli/commands/#exit-codes));
- your `klyro.yaml`, with every secret value removed: names only;
- for unexpected defects, a run with `KLYRO_VERBOSE=1` to capture details;
- the Klyro version (`klyro --version`) and Node version.

## Questions while building

- The [quickstart](/getting-started/quickstart/) covers the full first-stack
  walkthrough.
- The [klyro.yaml reference](/configuration/klyro-yaml/) lists every supported
  field and value.
- [Limitations](/reference/limitations/) states plainly what v0.1 does not do,
  before you file a "missing feature" report.

## Contributing changes

- [Architecture overview](/contributing/architecture-overview/): package
  ownership and Effect boundaries.
- [Providers](/integrations/providers/#adding-a-provider): how new runtime and
  integration support is added.
- [Upgrading](/reference/upgrading/): the controlled procedure for toolchain
  bumps.

Security-sensitive reports are best raised through a private channel with the
maintainers rather than a public issue; when in doubt, omit secrets and
describe the impact instead.