Start here
For setup and usage questions, start with the generated docs. They cover installation, CLI commands, MCP setup, agent references, and the current tool catalog from the npm package.
Use the README for source-level context, release notes, contribution details, and broader examples of questions Clovis can answer.
Use GitHub issues for reproducible bugs, documentation gaps, feature requests, and public technical questions. Use email for sensitive security reports, private business inquiries, or anything that should not be indexed publicly.
What to include
Include the topic, package version, Node version, operating system, command you ran, expected result, actual result, and whether you are using the CLI, package APIs, or MCP server.
For import issues, include the file type, bank export format, account type, and redacted sample rows when possible. Do not include bank credentials, API keys, full statement files, account numbers, or private financial records in public GitHub issues.
- Good: a minimal command, package version, redacted sample row, and exact error message.
- Bad: an unredacted bank statement, private ledger file, access token, or screenshot with account numbers.
Security and private reports
Send sensitive issues to support@cloviscomputing.com instead of posting them publicly. Include a clear description, reproduction steps, affected version, impact, and a safe proof of concept if you have one.
Do not access data that is not yours, degrade services, publish exploit details before coordination, or test against third-party systems without permission. Security reports do not create an employment, consulting, bounty, reward, or payment relationship unless agreed in writing.
Support scope
Support can help with package usage, documentation gaps, bug reports, local setup, and public project questions. Clovis support cannot provide financial, tax, legal, investment, accounting, banking, or emergency advice, and cannot recover local ledger files that were not backed up.
Support is provided as available. The public package does not include guaranteed response times, uptime commitments, compatibility guarantees, migration guarantees, professional review, or dedicated support unless a separate written agreement says otherwise.
Before sharing data
Redact names, account numbers, balances, transaction IDs, addresses, phone numbers, emails, tax identifiers, payroll information, client records, and anything else that is not needed to reproduce the issue. Prefer synthetic examples when possible.