Skip to content
Bedrova bedrova
FeaturesCompatibilityDevelopersCompareDocs Coming soon

Docs

Community & support

Where to get help, follow development, and file a bug report that gets fixed.

Bedrova is built by ideius in the open about what works and what doesn’t. Here’s where to reach people and how to get a problem looked at quickly.

Where to ask

  • Discord — the fastest place for questions, help, and show-and-tell.
  • Blog & changelog — follow what’s shipping on the blog and changelog.

Before you ask

Most issues have a known answer:

  • Check Troubleshooting for first-launch, memory, speed, and external-drive problems.
  • Skim the FAQ for scope and requirements questions.

Filing a good bug report

A report that includes the following gets diagnosed far faster than one that doesn’t:

  1. What you did and what happened — the steps, the model and quant, and the actual result versus what you expected.
  2. Your Mac — chip and unified memory (Settings → Hardware shows both).
  3. A diagnostics bundle — Settings → Diagnostics builds a redacted bundle with logs, versions, and config. It strips prompts, file contents, and secrets. See Diagnostics & support bundles for what’s inside and what’s removed.

Attach the bundle in Discord and describe the steps. The bundle tells us your runtime-pack version and recent errors without exposing anything you typed.

Privacy note

Sharing a diagnostics bundle is your choice and a deliberate, inspectable action — Bedrova never uploads one on its own. Everything else about what stays local is in Privacy & security.