Choose the marketplace for your desktop browser, then use the documentation to save your first source.
Redline support
Bring the context. Protect the evidence.
Find a quick answer in the docs, report a reproducible problem, or suggest an improvement without exposing private research.
Start here
Match the channel to the problem.
Documentation is fastest for known behavior. GitHub issues are best for reproducible public examples and concrete suggestions.
Check common causes for capture, Source Witness comparison, highlights, Evidence Compiler, search, import, and export problems.
Troubleshoot firstUse a non-sensitive public page and include browser, version, steps, expected result, and actual result.
Report a bugDescribe the research problem, the outcome you want, and any workaround you use today.
Request a featureReport a broken link, unclear instruction, inaccurate statement, or accessibility problem.
Report a docs issueSearch open and closed issues before filing. A workaround or status update may already exist.
Browse issuesLocal report builder
Format the environment. Keep the research out.
Enter only non-sensitive environment details. This tool runs entirely in your browser; it does not submit, save, or transmit the values.
Do not put URLs, selected text, notes, dossier names, credentials, tokens, or other research content in these fields.
Environment summary
Review the summary before pasting it into a public issue.
Continue to the bug report →Before you post
Redact first. Then redact again.
A useful public bug report does not need your private vault.
Never attach or paste:
- A full or partial Redline JSON export
- Private URLs, selected passages, notes, tags, dossier names, claim text, conclusions, or relation rationales
- Your browser profile, credentials, tokens, or cookies
- Unredacted screenshots containing personal or confidential material
What makes a useful bug report?
- Redline version
- Browser name and exact version
- Operating system and version
- Clear steps from a fresh page to the problem
- Expected result and actual result
- Whether the issue reproduces on a non-sensitive public page
- Whether it started after a Redline, browser, extension, or operating-system update
- A carefully redacted screenshot only when it materially helps
One reproducible behavior per issue is easier to diagnose and track.
If data appears missing
Confirm that you are in the same browser profile and operating-system account where the records were created. If the Library still opens, create an All data JSON export immediately.
Because Redline has no hosted copy of the local vault, support cannot recover data after the local storage is removed when no JSON backup exists.
Security, privacy, or sensitive-data reports
Do not use a public issue for a suspected vulnerability, private URL, credential, token, or report that cannot be meaningfully redacted.
Use GitHub’s private vulnerability reporting for the support repository. This creates a private security advisory visible to repository maintainers rather than a public issue.
Open a private reportIf GitHub reports that private vulnerability reporting is unavailable, open a public issue containing no sensitive details and ask the maintainer for a private contact route.
Support scope and expectations
Public support is best-effort and focuses on current Redline releases on supported desktop browsers. Support can explain documented behavior, investigate reproducible product defects, and consider feature or documentation requests.
Support cannot restore a deleted vault without a Redline JSON backup, repair third-party websites, guarantee citation style compliance, or diagnose a report that requires publishing confidential research.