1. Choose a support channel
Discord community
Best for usage questions, workflow discussion, and help from the community.
Open DiscordThese are public or third-party channels. Anything you post may be visible to others and is also governed by Discord's or GitHub's terms and privacy policy.
2. Before reporting a problem
- Confirm that you are using the latest Lévin™ Harness preview available to you.
- Retry the action in a non-critical test project when it is safe to do so.
- Record the exact steps, expected result, actual result, and whether the problem is repeatable.
- Note your macOS version, Mac model or chip, Lévin™ Harness version, model provider, and relevant plugin or remote-host setup.
- Remove secrets and unrelated private data from screenshots, logs, prompts, and sample files.
3. Report a bug
A short, reproducible report is more useful than a large raw log. Include only the context needed to reproduce the problem.
Summary:
Lévin™ Harness version:
macOS and Mac model:
Steps to reproduce:
1.
2.
3.
Expected result:
Actual result:
Does it reproduce consistently:
Relevant provider / plugin / remote host:
Sanitized screenshot or log:For public projects and updates, visit the Levinthal GitHub profile. For product usage questions, start in the Discord community.
4. Suggest a feature or improvement
Describe the research or engineering task you are trying to complete, the current obstacle, and the result you need. A concrete workflow and sample input are usually more helpful than prescribing a specific interface.
- Explain who the workflow is for and how often it occurs.
- Describe the current steps and where time or reliability is lost.
- State what a successful result would look like.
- Share a sanitized example that the team can use to test the behavior.
5. Protect sensitive data
Before sharing any diagnostic material, remove API keys, passwords, SSH keys, access tokens, private repository URLs, patient or participant information, proprietary molecules, confidential sequences, unpublished results, and unrelated file paths or content.
If a report cannot be explained without sensitive material, wait for an approved private channel. Public community channels are not suitable for confidential, regulated, or identifying data. See the Privacy Policy for how connected services handle information.
6. Security issues
Do not publicly post an unpatched vulnerability, exploit, leaked credential, or sensitive proof of concept. Avoid accessing data that is not yours, stop testing once a vulnerability is confirmed, and preserve only the minimum evidence needed for a report.
A dedicated private address or form for security reports has not yet been confirmed. It must be published here before the product's public launch. Until then, do not send confidential vulnerability details through Discord or a public GitHub issue.
7. Preview support scope
Lévin™ Harness is preview software, and community support does not include a guaranteed response time or service level. Reports are prioritized based on severity, reproducibility, user impact, and available capacity.
Model provider billing, account access, outages, training settings, and data-retention requests must be handled by the relevant provider. Problems with your remote host, Apple iCloud account, GitHub, Discord, or a third-party plugin may also require support from that service.