Start with the docs
The docs cover setup and every feature, starting with the quickstart. Troubleshooting has fixes for the problems people run into most, and known issues lists the limitations and bugs in the current version.
Ask on GitHub
Questions, bug reports, and feature requests go to the issues in the OpenOrc GitHub repository. Open a new issue and choose Question, Bug report, or Feature request. Search the existing issues first, since yours may already have an answer.
Say which OpenOrc version and operating system you use, and which agent command-line tool and version is involved. For the iPhone app, add your iOS version and the app’s version, which the App Store or TestFlight shows. A small example that shows the problem helps most.
Issues are public. Before you post a screenshot or a log, remove credentials, private conversations, project names, and local paths. Do not attach OpenOrc’s database or a full profile.
For something you would rather not post in public, email eliasdavidceriola@gmail.com.
Security problems
Report a suspected vulnerability privately, not in an issue: on the repository’s Security and quality tab, choose Report a vulnerability. GitHub shares the report only with the maintainers.
Agents and accounts
OpenOrc runs the agent command-line tools you install, signed in to your own accounts. Billing, account access, and outages for those services belong with each provider’s support.
What to expect
OpenOrc is free and open source. Help comes from its maintainer and the people who use it, as time allows, with no promised response time. The privacy policy describes how OpenOrc handles information.